Hi,

you could, but I suggest you change to adopt the following pattern for
instantiating e.g. an Unmarshaller.

XMLContext context = new XMLContext();
context.setMapping(....);

Unmarshaller unmarshaller = context.createUnmarshaller();

This way, creation of the InternalContext happens once only (with the
creation of the XMLContext instance).

Kind Regards
Werner

On 17.06.2011 16:06, Thinian wrote:
> 
> Hi Werner,
> 
> I noticed there are more than one constructor use for the Marshaller, and in
> one you can pass in the context, I ssume if we don't want it to initialize
> it every time, we should use the other constructor.
> 
> Thanks for the quick responses.
> 
> Mark
> 
> 
> Werner Guttmann-6 wrote:
>>
>> Hi,
>>
>> the question still remans whether Axis internally is making use of the
>> XMLContext class to instantiate Marshaller and Unmarshaller instances.
>> If not, that means, if you (aka Axis is) are creating Unmarshaller and
>> Marshaller instances directly, then you'll see the 'parsing' of those
>> (refactored) property files again and again.
>>
>> But given that this is logging (output) only, and a possible performance
>> impact should be negligible, you should be fine.
>>
>> Kind regards
>> Werner Guttmann
>>
>> On 17.06.2011 11:47, Thinian wrote:
>>>
>>> Hi Werner,
>>>
>>> We seem to use these two classes:
>>>
>>> import org.exolab.castor.xml.Marshaller;
>>> import org.exolab.castor.xml.Unmarshaller;
>>>
>>> It is used with axis in a webservice.
>>>
>>> Has logging changed? The upgrade had almost no impact on our code base.
>>>
>>> Mark 
>>>
>>>
>>> Werner Guttmann-6 wrote:
>>>>
>>>> Hi,
>>>>
>>>> how are you using Castor XML ? Are you using the XMLContext to create
>>>> (Un-)Marshaller instances to be used for business using the
>>>> create(Un-)Marshaller() methods ?
>>>>
>>>> Thanks
>>>> Werner
>>>>
>>>> On 17.06.2011 10:41, Thinian wrote:
>>>>>
>>>>> Hi All,
>>>>>
>>>>> We have recently upgraded to castor 1.3 and we are seeing the following
>>>>> lines in our log file:
>>>>>
>>>>>
>>>>>
>>>>> 2011-06-16 12:18:08,640 DEBUG [org.castor.core.util.AbstractProperties]
>>>>> Properties loaded from classpath: /org/castor/xml/castor.xml.properties
>>>>> 2011-06-16 12:18:12,473 DEBUG [org.castor.core.util.AbstractProperties]
>>>>> Properties loaded from classpath:
>>>>> /org/castor/core/castor.core.properties
>>>>> 2011-06-16 12:18:12,474 DEBUG [org.castor.core.util.AbstractProperties]
>>>>> Properties loaded from classpath: /org/castor/xml/castor.xml.properties
>>>>> 2011-06-16 12:18:12,500 DEBUG [org.castor.core.util.AbstractProperties]
>>>>> Properties loaded from classpath:
>>>>> /org/castor/core/castor.core.properties
>>>>> 2011-06-16 12:18:12,500 DEBUG [org.castor.core.util.AbstractProperties]
>>>>> Properties loaded from classpath: /org/castor/xml/castor.xml.properties
>>>>> 2011-06-16 12:18:14,328 DEBUG [org.castor.core.util.AbstractProperties]
>>>>> Properties loaded from classpath:
>>>>> /org/castor/core/castor.core.properties
>>>>> ...Constantly repeating, everytime castor is used.
>>>>>
>>>>> We did not see these messages with the older version. Is this normal
>>>>> behavior?
>>>>>
>>>>> Thanks,
>>>>> Mark Miller
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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