Travis,

can you please create a new Jira issue at

http://jira.codehaus.org/browse/CASTOR

and attach all relevant files. If you tried to comply with the
guidelines available in the XML HOW-TO section, that would be appreciated.

travis fritts wrote:
> Thanks for your help Josh.  I also had this work correctly with a small
> test which made me look harder at the specific element names and
> values.  I found the issue and I hope someone has a work around for
> this.  The problem is with the element Named 'Number'.  Castor has
> problems creating a wrapper-element for an element named 'Number'.  I
> can change the name of the element and the mapping works fine.  I am
> using elements named 'Number' elsewhere but not as a wrapper and they
> all work fine.  Is this a known bug/issue?  Has anyone experienced this
> and what was your solution.  Thanks in advance for your assistance.
> 
> Travis
> 
> 
>> From: Josh Foure <[EMAIL PROTECTED]>
>> Reply-To: [email protected]
>> To: [email protected]
>> Subject: Re: [castor-user] Castor XML: Strange behavior while mapping
>> xml elements
>> Date: Wed, 13 Jun 2007 19:23:25 -0700 (PDT)
>>
>> Hi Travis,
>>
>> I tried a mapping file with a snippet similar to what you sent out and
>> it worked fine with Castor 1.1.  You can post your complete XML and
>> mapping file if you want.
>>
>> Josh
>>
>> ----- Original Message ----
>> From: travis fritts <[EMAIL PROTECTED]>
>> To: [email protected]
>> Sent: Wednesday, June 13, 2007 6:05:24 PM
>> Subject: Re: [castor-user] Castor XML: Strange behavior while mapping
>> xml elements
>>
>> Thanks for the response.  You are right, I had posted the wrong code
>> for the
>> mapping.  It should be Number.  However, this is not really the root
>> element.  I just posted a snippet.  I dont understand how the more
>> complex
>> element will map correctly and not the simpler one.  Any thoughts?
>>
>>
>> >From: Josh Foure <[EMAIL PROTECTED]>
>> >Reply-To: [email protected]
>> >To: [email protected]
>> >Subject: Re: [castor-user] Castor XML: Strange behavior while mapping
>> xml
>> >elements
>> >Date: Wed, 13 Jun 2007 14:20:20 -0700 (PDT)
>> >
>> >Hi Travis,
>> >
>> >Shouldn't the "location" attribute for policyPrefix bind-xml be "Number"
>> >instead "Name"?  I see that you use "location" for each field
>> starting with
>> >the root but in my experience you only need it for places like
>> >Policy-Prefix where you want to ignore the Number element.
>> >
>> >Hope that helps,
>> >Josh
>> >
>> >
>> >----- Original Message ----
>> >From: travis fritts <[EMAIL PROTECTED]>
>> >To: [email protected]
>> >Sent: Wednesday, June 13, 2007 4:52:40 PM
>> >Subject: [castor-user] Castor XML: Strange behavior while mapping xml
>> >elements
>> >
>> >I am getting the following error while trying to map just one
>> specific xml
>> >element.  Other more complex elements map correctly.  Here is the
>> example:
>> >
>> ><Policy>
>> >         <LOB-Code>1</LOB-Code>
>> >         <Number>
>> >             <Policy-Prefix>12345</Policy-Prefix>
>> >         </Number>
>> >         <State>AR</State>
>> >         <Insured-Name>
>> >             <Client-Id>234543</Client-Id>
>> >             <First-Name>John</First-Name>
>> >             <Middle-Name/>
>> >             <Last-Name>Doe</Last-Name>
>> >         </Insured-Name>
>> >         <Agency>
>> >             <Number>12345</Number>
>> >             <Name>
>> >                 <Client-Id>12345</Client-Id>
>> >                 <Business-Name>Some cool place</Business-Name>
>> >             </Name>
>> >         </Agency>
>> ></Policy>
>> >
>> >I am getting unable to find FieldDescriptor for 'Number' in
>> ClassDescriptor
>> >of Policy while using the following mapping (just a snippet of the
>> >mapping):
>> >
>> ><field name="LOBCode" type="string">
>> >     <bind-xml name="LOB-Code" location="Policy"/>
>> ></field>
>> ><field name="declarationNumber" type="string">
>> >     <bind-xml name="Declaration-Number" location="Policy"/>
>> ></field>
>> ><field name="policyPrefix" type="string">
>> >     <bind-xml name="Policy-Prefix" location="Name" />
>> ></field>
>> ><field name="state" type="string">
>> >     <bind-xml name="State" location="Policy"/>
>> ></field>
>> ><field name="insuredNameClientId" type="string"
>> >handler="com.basic.castor.utility.DefaultNumberHandler">
>> >     <bind-xml name="Client-Id" location="Policy/Insured-Name"/>
>> ></field>
>> ><field name="businessName" type="string">
>> >     <bind-xml name="Business-Name" location="Policy/Insured-Name"/>
>> ></field>
>> >
>> >Why can I map the more complex Business-Name element and not the
>> >Policy-Prefix?
>> >
>> >Here is the castor debug info for this mapping:
>> >
>> >#startElement: Policy
>> >wrapper-element: Policy
>> >#characters:
>> >
>> >#startElement: LOB-Code
>> >#characters: 10
>> >#endElement: LOB-Code
>> >#characters:
>> >
>> >#startElement: Number
>> >unable to find FieldDescriptor for 'Number' in ClassDescriptor of
>> Policy -
>> >ignoring extra element.
>> >#characters:
>> >
>> >#startElement: Policy-Prefix
>> >#characters: 12345
>> >#endElement: Policy-Prefix
>> >#characters:
>> >
>> >#endElement: Number
>> >#characters:
>> >
>> >#startElement: State
>> >#characters: AR
>> >#endElement: State
>> >#characters:
>> >
>> >#startElement: Insured-Name
>> >wrapper-element: Insured-Name
>> >#characters:
>> >
>> >#startElement: Client-Id
>> >#characters: 234543
>> >#endElement: Client-Id
>> >#characters:
>> >
>> >#startElement: First-Name
>> >#characters: John
>> >#endElement: First-Name
>> >#characters:
>> >
>> >#startElement: Middle-Name
>> >#endElement: Middle-Name
>> >#characters:
>> >
>> >#startElement: Last-Name
>> >#characters: Doe
>> >#endElement: Last-Name
>> >#characters:
>> >
>> >#endElement: Insured-Name
>> >#characters:
>> >
>> >#startElement: Agency
>> >wrapper-element: Agency
>> >#characters:
>> >
>> >#startElement: Number
>> >#characters: 12345
>> >#endElement: Number
>> >#characters:
>> >
>> >#startElement: Name
>> >wrapper-element: Name
>> >#characters:
>> >
>> >#startElement: Client-Id
>> >#characters: 12345
>> >#endElement: Client-Id
>> >#characters:
>> >
>> >#startElement: Business-Name
>> >#characters: Some cool place
>> >#endElement: Business-Name
>> >#characters:
>> >
>> >#endElement: Name
>> >#characters:
>> >
>> >
>> >Thanks for your help with this issue.
>> >
>> >_________________________________________________________________
>> >Picture this – share your photos and you could win big!
>> >http://www.GETREALPhotoContest.com?ocid=TXT_TAGHM&loc=us
>> >
>> >
>> >---------------------------------------------------------------------
>> >To unsubscribe from this list please visit:
>> >
>> >     http://xircles.codehaus.org/manage_email
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >____________________________________________________________________________________
>>
>> >Fussy? Opinionated? Impossible to please? Perfect.  Join Yahoo!'s user
>> >panel and lay it on us.
>> >http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
>> >
>>
>> _________________________________________________________________
>> Play games, earn tickets, get cool prizes. Play now–it's FREE!
>> http://club.live.com/home.aspx?icid=CLUB_hotmailtextlink1
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ____________________________________________________________________________________
>>
>> The fish are biting.
>> Get more visitors on your site using Yahoo! Search Marketing.
>> http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
> 
> _________________________________________________________________
> Picture this – share your photos and you could win big! 
> http://www.GETREALPhotoContest.com?ocid=TXT_TAGHM&loc=us
> 
> 
> ---------------------------------------------------------------------
> 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

Reply via email to