See in-line.

Werner

Pascal Maugeri wrote:
>> having no XML name at this 'time of processing' isn't a problem...
>> it can have multiple reasons, in your special case it is because
>> 1) Castor has no mapping information at hand,
> 
> Can I assume that a mapping file could be a good workaround for this problem ?
Not sure, to be honest. The Java classes as generated for/from
enumerations are far better than any mapping can be, imho.
> 
>> 2) then Castor creates adhoc descriptors by introspection (reflection)
>> and those descriptors have no XML name set
> 
> But I verified that there is a .castor.cdr that binds the class
> AllowInviteType to its descriptor class. I thought it was enough ...
It should be enough. But I guess that the descriptor that is found
somehow represents the wrong entity, i.e. one without an name set. Not
100% sure, though.

> 
>> To come back to issue 2031: we're still working to solve the problem,
>> but there are at least two different problems that overlap and we have
>> to solve each of them.
> 
> It looks a quite complex problem. Please let me know if I can help a
> bit.... I would also appreciate if you could recommend me a workaround
> as this bug prevents us to process several parts of documents in our
> projects.
Will try to come up with work-around(s) over the weekend.
> 
> Regards,
> Pascal
> 
>> Regards
>>
>> Joachim
>>
>> On 02/08/07, Pascal Maugeri <[EMAIL PROTECTED]> wrote:
>>> Hi
>>>
>>> I'm working on the issue CASTOR-2031. I'm debugging the Marshaller
>>> class and I have a quick question regarding the code of this class.
>>>
>>> It happens that on line 953 (trunk version) the
>>> 'descriptor.getXMLName()' returns null.
>>>
>>> What could be the possible reasons ? Is it a normal behavior ? I
>>> observe that for other nodes of the document being marshalled
>>> getXMLName() always returns the correct name.
>>>
>>> The related node of the schema being processed (in attachment) is
>>> 'allow-invite'.
>>>
>>> Regards
>>> Pascal
>>>
>>> ---------------------------------------------------------------------
>>> 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

Reply via email to