Hi,
I do have set of XSDs which are interlinked. Let's say I have 4 xsds
a.xsd, b.xsd,c.xsd and d.xsd. b.xsd include a.xsd and c.xsd and d.xsd
include b.xsd. When I try to generate classes using XJC for c.xsd, it
generates classes for b.xsd and a.xsd. Same of d.xsd. Hence, it is
generating duplicate classes in package of c.xsd and d.xsd. How can I
avoid this?
Regards,
Tamanna Shah
Sr. Software Engineer
-----Original Message-----
From: aleksei.valikov_at_gmail.com [mailto:aleksei.valikov_at_gmail.com] On
Behalf Of Aleksei Valikov
Sent: Wednesday, June 17, 2009 11:59 PM
To: users_at_jaxb.dev.java.net
Subject: Re: FW: JAXB memory leak issue
Hi,
> I am facing memory leak issue while loading the JAXB classes using
JAXBContext.newInstance(factoryClass); method.
What exactly leaks memory? How did you find it out?
> I am using JDK 1.6.0.14 and my application is deployed on tomcat
6.0.18.
>
> How do I resolve it? also, when I generate classes using XJC tool it
is generating too many classes basically, I wanted to avoid generation
of repeated classes. How do I do that?
I'm not sure what you mean with "repeated classes" but maybe episodes
are something you're looking for.
http://weblogs.java.net/blog/kohsuke/archive/2006/09/separate_compil.htm
l
Bye.
/lexi
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net
"Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment."
www.cybage.com