Hi Jose, Personally, I keep all my projects outside the workspace, so for me the binding and schema would be inside the project but outside the workspace. I'm not sure how that fits in with what you're suggesting.
I'd say your approach of a separate source directory for the code generation is the right way to go. - Dennis Dennis M. Sosnoski SOA, Web Services, and XML Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117 [EMAIL PROTECTED] wrote: > I will make the following changes to v0.1.0 of the org.jibx.eclipse > plug-in: > > * Multiple binding locations (file & dir). Each location can be > disabled via a checkbox. > > * Multiple schema locations (file 6 dir). Each location can be > disabled via a checkbox. > > * Does anyone see the need for allowing schema & binding locations to > reside outside of the workspace? > > * A separate source directory must be defined for JiBX if generating > java and bindings from XSDs. This is to allow for proper cleaning of > old java classes and packages {currently I can remove the Java classes > but not the packages. I think a separate source directory is cleaner > then mucking about with the JDTModel? > > * shorter refresh times, currently the generation and binding is fast > but eclipse takes a while to refresh which means you don't see the > changes immediately. > > Jose Badeau _______________________________________________ jibx-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jibx-devs
