[ http://issues.apache.org/jira/browse/GERONIMO-1693?page=comments#action_12369562 ]
David Jencks commented on GERONIMO-1693: ---------------------------------------- The problems seem to be caused by xmlbeans downloading a copy of the webservices client schema from the web rather than using the local copy. This brings up the point that it is essential that download=false for all our use of xmlbeans. We must supply every schema that we compile. In the m1 plugin I had to supply an entity resolver and a catalog manager in order to help xmlbeans find the correct local schemas. Something similar may be needed here also. Also, in the m1 plugin you can specify modules to add to the xmlbeans compiler classpath, where these modules include stuff already generated by xmlbeans. In this way xmlbeans won't generate duplicate copies of the already generated classes, and you won't have big problems with xmlbeans not able to find the missing schemas. This will be more of a problem compiling the *-builder modules which tend to depend on each other. I also strongly recommend setting noJavac true, but it is possible that the m2 plugin won't let you do this. I think maven should be in control of compiling the generated code, not xmlbeans/ant. I consider exposing this property and the others that let xmlbeans compile the results in the m2 plugin an error. > j2ee-schema module migration to Maven2 > -------------------------------------- > > Key: GERONIMO-1693 > URL: http://issues.apache.org/jira/browse/GERONIMO-1693 > Project: Geronimo > Type: Sub-task > Reporter: Anita Kulshreshtha > Priority: Blocker > Attachments: pom.patch > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
