import org.apache.fop.layout.*;
import org.apache.fop.datatypes.*;
import org.apache.fop.apps.FOPException;
+import org.apache.fop.layoutmgr.LayoutManager;
+//import org.apache.fop.layoutmgr.BlockLayoutManager;
import org.xml.sax.Attributes;
return this.span;
}
+ public LayoutManager getLayoutManager() {
+ //return new BlockLayoutManager(this);
+ return null;
+ }
+
}
import org.apache.fop.layout.Area;
import org.apache.fop.layout.BodyAreaContainer;
import org.apache.fop.apps.FOPException;
+import org.apache.fop.layoutmgr.LayoutManager;
+import org.apache.fop.layoutmgr.FlowLayoutManager;
// Java
import java.util.Hashtable;
// 001228, Number 406), confusion in spec section 6.4.5 about
// multiplicity of fo:flow in XSL 1.0 is cleared up - one (1)
// fo:flow per fo:page-sequence only.
+
/* if (pageSequence.isFlowSet()) {
if (this.name.equals("fo:flow")) {
throw new FOPException("Only a single fo:flow permitted"
}
*/
setFlowName(getProperty("flow-name").getString());
- pageSequence.addFlow(this);
+ // Now done in addChild of page-sequence
+ //pageSequence.addFlow(this);
}
protected void setFlowName(String name) throws FOPException {
return true;
}
+ public LayoutManager getLayoutManager() {
+ return new FlowLayoutManager(this);
+ }
+
}