Arnoud, I read yet another set of questions on this subject on the list so I am going public again.
> -----Original Message----- > From: Arnaud Blandin [mailto:[EMAIL PROTECTED]] > Sent: Monday, July 08, 2002 4:47 PM ... > I understand you are interested for the moment in the namespace issue > and I will sum up quickly the work on the binding file: regarding the > namespace handling, there are no major changes. The only code in place > as far as I can remember is to allow the user to define the mapping > namespace-package by hand in the binding file instead of the property > file. Does this mean that calling schema will know where to find the referenced classes? That would reduce the maintainence job considerably. It might even be a full solution to the problem (expect for not being automated) Say a schema contains namspaces a and b and element <a:thing><b:part /></a:thing> Can this then be generated as -*-file a/thing.java-*- package a; import b.part; public class thing{ part p; }; -*-end of file a/thing.java-*- and -*-file b.part.java-*- package b; public class part{}; -*-end of file b.part.java-*- using a namespace properties construction like org.exolab.castor.builder.nspackages=\ a.xsd=a,\ b.xsd=b or do i misunderstand? Then maybe stylesheets are an option? > There was no decision taken for a high level handling of namespaces as > you proposed. I have currently no time to work on it unfortunately but > you can still send me your thoughts and code, I will take a > closer look > at it later in the week. ... <more discussion cut> ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
