Hi Doug,

After I reviewed your stack trace , I just found you need to set the
servicePreference in the FileUtilities first.

Willem.

java.lang.NullPointerException
> >         at
> > au.net.mmsn.pfc.servlet.serbices.rfio.impl.FileUtilities.getServicePrefer
> >ence(FileUtilities.java:76) at
> > au.net.mmsn.pfc.servlet.serbices.rfio.impl.RemoteFileImpl.<init>(RemoteFi
> >leImpl.java:29) at
> > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)


doug wrote:
> Hi Willem,
> Thanks to you both for that. 
> Now the depends-on attribute parses ok in the jaxws:endpoint elements of the 
> beans.xml file, but I still have the same error as before. i.e. it doesn't 
> seem to have preloaded the depends-on bean.
>
> thanks again
> Doug
>
> On Thursday 06 September 2007 17:56, Willem Jiang wrote:
>   
>> Hi doug ,
>>
>> I just committed a patch CXF-955 which is contributed by Fred into the
>> trunk.
>> It added the depends-on attribute in the jaxws:endpoint. I think you
>> just want that :)
>>
>> You can try latest version in the trunk , or wait for the next snapshot.
>>
>> Willem.
>>
>> doug wrote:
>>     
>>> I have implemented some services and configure them in a
>>> WEB-INF/beans.xml file. I was using this file to specify some
>>> initialization parameters that get stored in a bean (FileUtilities)
>>> and which are subsequently accessed by several other jaxws:endpoint
>>> definedservices. I thought everything was configured ok because all
>>> services are loaded without problems on my development server, running
>>> apache-tomcat-5.5.20 Unfortunately when I try to deploy to our
>>> production server, apache-tomcat-5.5.16 it fails to load, on account of
>>> the error below.
>>>
>>> Basically, it seems to me that the FileUtilities bean hasn't been
>>> loaded or initialized at the time the endpoint is being instatiated,
>>> whereas it was under tomcat 5.5.20.
>>>
>>> I read that there is a <bean depends-on="otherID"> attribute that induces
>>> otherID beans to be loaded and initialized first, but apparently that
>>> doesn't exist for jaxws:endpoint
>>>
>>> Is there another way to achieve the same result?
>>>
>>> Thanks
>>> Doug
>>>
>>>
>>>
>>> 879  [main] ERROR org.springframework.web.context.ContextLoader  -
>>> Context initialization failed
>>> org.springframework.beans.factory.BeanDefinitionStoreException:
>>> Unexpected exception parsing XML document from ServletContext r
>>> esource [/WEB-INF/beans.xml]; nested exception is
>>> org.springframework.beans.FatalBeanException: Could not load class:
>>> au.net.mm sn.pfc.servlet.serbices.rfio.impl.RemoteFileImpl; nested
>>> exception is java.lang.NullPointerException
>>> Caused by:
>>> org.springframework.beans.FatalBeanException: Could not load class:
>>> au.net.mmsn.pfc.servlet.serbices.rfio.impl.RemoteFileImpl;
>>> nested exception is java.lang.NullPointerException
>>> Caused by:
>>> java.lang.NullPointerException
>>>         at
>>> au.net.mmsn.pfc.servlet.serbices.rfio.impl.FileUtilities.getServicePrefer
>>> ence(FileUtilities.java:76) at
>>> au.net.mmsn.pfc.servlet.serbices.rfio.impl.RemoteFileImpl.<init>(RemoteFi
>>> leImpl.java:29) at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>>         at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAc
>>> cessorImpl.java:39) at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConst
>>> ructorAccessorImpl.java:27) at
>>> java.lang.reflect.Constructor.newInstance(Constructor.java:494)
>>>       
>
>   

Reply via email to