Hi Ranjan,
it sound like you might be spot on. Most likely, in terms of your web
app class loader, it looks like the 1.0.5 release of Castor takes
precedence (which is not what you want).
Kind Regards
Werner
On 01.06.2011 11:15, ranbaab wrote:
>
> Hi werner,
>
> You are right, in geronimo the castor-1.0.5 is loaded in the module
> org\apache\geronimo\configs\webservices-common. Though I have configure to
> used castor-1.1 for my application in geronimo, may be the configuration is
> not proper. I will investigate further and update the outcome.
>
> Thanks,
> Ranjan
>
>
>
> ranbaab wrote:
>>
>> Hi all,
>>
>> I am working on a web based application deployed on tomcat and planning to
>> move to geronimo.
>>
>> The application was deploy to geronimo tomcat and run
>> successfully(partially). Some of the page are having issue due to null
>> pointer exception because the string without the default value return null
>> after unmarshalling.
>>
>> In the schema, there is a string which does not have a default value.
>> <xs:attribute name="n-columns" type="xs:string" minOccurs="1"
>> maxOccurs="1"/>
>>
>> org.exolab.castor.builder.SourceGeneratorMain is used to generate the
>> class, while the xml has the value n-columns=""
>>
>> The generated default constructor does not set the string to it default
>> value.
>>
>> public class SubGroup
>> implements Serializable
>> {
>> private String _nColumns;
>>
>> public SubGroup()
>> {
>>
>> }
>>
>> After the Unmarshaller.unmarshal(Configuration, reader)
>> The string value is return null.
>>
>> But when the application is deployed with tomcat, the string value is
>> return as "" string.
>> I am wondering whether there is any jar conflict?
>>
>> Thanks,
>> Ranjan
>>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
