I did have a dependency issue when i deployed it to the osgi container. castor-xml uses com.sun.org.apache.xml.internal.serialize in jdk5+, which is not exported by the osgi system bundle (it is not part of the standard java library but rather an implementation detail). To resolve this, I created a fragment bundle and exported the package.
Thought to mention this in case it has any bearing on the problem. Thanks, Mohnish mohn3310 wrote: > > Hello, > > I'm using castor-xml in introspection mode to write out simple POJOs to > files (one POJO per file). I've written unit tests and verified that this > works. I've also inspected the files and made sure they have appropriate > xml. > > I then packaged this up into an osgi bundle and deployed it to a container > (felix). For some reason when I run it, it ends up creating the file but > it is empty... i.e. no xml in the file. Yet another strange thing is that > I use Unmarshaller.unmarshall() to convert the xml files back to their > associated POJOs. As a test I generated the xml by hand and it was able to > load it. So Marshaller.marshall() doesn't work, but > Unmarshaller.unmarshall() does! > > Any idea why it is behaving this way? Same code... works great "normally", > but doesn't work inside an osgi container. > > Thanks, > Mohnish > -- View this message in context: http://www.nabble.com/castor-xml-writing-empty-file-tp24175804p24175870.html Sent from the Castor - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
