I am asking more from the point of view, to see if there are any name conflicts while the Code generator framework generates the java classes from XML Schema. There is a setting in the castorbuilder.properties,, which I tried, to send the name conflicts to the log file, but I am unable to get it to work successfully. If someone has used this feature, pls help Thanks Kannan
# Configures how to handle name conflicts within a Schema (such as a complex # type and a global element with the same name). When name conflicts occur, # Castor will use the first listed conflict resolution strategy to decide what # to do. Current choices are warn-and-ask-user-what-to-do and log-and-ignore. # More choices may be offered in the future. # Default is as configured below. # org.exolab.castor.builder.nameConflictStrategies=\ org.exolab.castor.builder.conflictresolution.WarningViaDialogClassNameCR Strategy,\ org.exolab.castor.builder.conflictresolution.InformViaLogClassNameCRStra tegy -----Original Message----- From: Werner Guttmann [mailto:[EMAIL PROTECTED] Sent: Monday, November 05, 2007 1:10 PM To: [email protected] Subject: Re: [castor-user] Castor Logging and XML validation No document, as it's standard logging and depends on what tool you are using for logging. Are you by chance using log4j ? Werner Jayaraman, Kannan wrote: > Thanks for the response. Can you pls, point me a URL/Doc link in > Castor, where I could refer about how to turn on the logging for > Castor XML/Java binding code generator. > > Thanks > Kannan > > -----Original Message----- > From: Werner Guttmann [mailto:[EMAIL PROTECTED] > Sent: Sunday, November 04, 2007 11:07 AM > To: [email protected] > Subject: Re: [castor-user] Castor Logging and XML validation > > Hi, > > please see inline. > > Werner > > Jayaraman, Kannan wrote: >> How do I enable logging while using castor binding files (to log the >> output, while I generate the castor binding classes). > I assume you are referring to the Castor XML code generator, which is > used to generate Java classes from an XML schema ? If so, this code > (as well as other parts of Castor) use Jakarta's commons-logging > package for logging. As such, you can plug in any logging provider of > your choice, such as Log4J or simply Java logging. > >> Also, is the XSD validation while unmarshalling/marshalling of >> XML-to-Java using Castor binding frameworks, is automatically enabled. > No, it is not. > >> Or is there a place to turn on/off ? > Please have a look at the documentation of the Castor properties file. > >> Pls help >> Thanks >> Kannan >> >> -----Original Message----- >> From: kirran [mailto:[EMAIL PROTECTED] >> Sent: Thursday, November 01, 2007 4:30 PM >> To: [email protected] >> Subject: [castor-user] castor user issue >> >> >> Hi All, >> >> Any help is sincerely appreciated. >> >> sample xml >> --- >> <person name="tom"/> >> <person name="brady"/> >> >> >> class Person{ >> private name; >> public void setName(String name){ >> this.name=name; >> } >> } >> >> When i use castor, it gives me a collection of person objects. What i >> need is a callback in my client code after each person >> >> element is parsed into an object sequentially so that i can invoke >> operations on each object. This is also inline with my req. >> >> of not storing an entire collection of persons in memory at once. >> >> Thanks in advance. >> >> >> >> >> >> >> -- >> View this message in context: >> http://www.nabble.com/castor-user-issue-tf4734226.html#a13537918 >> Sent from the Castor - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
