Sam, A similar thread came up a little while back. Have a look at this and see if it helps you out. http://apache-pivot-users.399431.n3.nabble.com/bxml-id-scoping-td2838043.html
Note that Joe followed up with a post at the end regarding the effects of reusing a BXMLSerializer instance and clearing the namespace verses using a new BXMLSerializer instance for each 'included' BXML fragment. Chris On 1 May 2011 13:30, sam <[email protected]> wrote: > I think I may resolved the issue. The original way of using include made me > think the difference would be the Id I gave to them. Also the error indicate > it was in > org.apache.pivot.beans.BXMLSerializer.processAttributes(BXMLSerializer.java:934). > Looked like the id was not registered so they some how got recognized as the > same thing. Then I tried to assign a name or some sort like in the include > tag does for the bxml:id attribute and not having a success. Finally I > created another BXMLSeralizer instance and loaded the second bxml and worked > fine. Is this the right way of doing it? I am guessing by adding another > BXMLSerializer instance, the name space was different. It sort of sense of > having another class loader to load the same class again. But I guess this > might not be the best way to resolve this issue > ------------------------------ > View this message in context: Re: Dynamically adding components to a > boxpane and ID already used > error<http://apache-pivot-users.399431.n3.nabble.com/Dynamically-adding-components-to-a-boxpane-and-ID-already-used-error-tp2885412p2885463.html> > > Sent from the Apache Pivot - Users mailing list > archive<http://apache-pivot-users.399431.n3.nabble.com/>at Nabble.com. >
