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 

Reply via email to