Here is the services.xml which accompanies the axis2.1.3 SpringAwareService 
sample

 <service name="SpringAwareService">
    <description>
        simple spring example which uses 2 parameters and 1 service
    </description>
    <parameter name="ServiceObjectSupplier" 
locked="false">org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier</parameter>
    <parameter name="SpringBeanName" 
locked="false">springAwareService</parameter>
    <operation name="getValue">
        <messageReceiver 
class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
    </operation>
</service> 

spring classes/jars should be located in $AXIS_HOME/modules/spring
RawXMLINOUTMessageReceiver should be located in $AXIS_HOME/modules/kernel

I would work with the working Spring sample and then add 1 parameter at a time 
until you find your error
HTH
Martin Gainty 
______________________________________________ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 


> Date: Mon, 2 Jun 2008 11:14:07 -0300
> From: [EMAIL PROTECTED]
> To: [email protected]
> Subject: Re: Spring service bean not initialized in the skeleton class.
> 
> Dwipin, I see no obvious problem. I'm afraid you're going to have to
> put all your axis2, spring, and userspace classes in debug and check
> the logs. Sure you don't have a name mismatch and that you really are
> using this services.xml ? Try double checking that your
> applicationContext.xml and services.xml are matching correctly.
> 
> Robert
> 
> On Mon, Jun 2, 2008 at 10:44 AM, Dwipin C <[EMAIL PROTECTED]> wrote:
> >
> > This the services.xml I am using -
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <!-- This file was auto-generated from WSDL -->
> > <!-- by the Apache Axis2 version: 1.4  Built on : Apr 26, 2008 (06:24:30
> > EDT) -->
> > <serviceGroup>
> >     <service name="ACLAndAuthService">
> >         <messageReceivers>
> >             <messageReceiver mep="http://www.w3.org/ns/wsdl/in-out";
> > class="services.ACLAndAuthServiceMessageReceiverInOut"/>
> >         </messageReceivers>
> >         <parameter name="serviceObjectSupplier" locked="false">
> >
> > org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier
> >                 </parameter>
> >         <parameter name="SpringBeanName" locked="false">
> >                         aclService
> >                 </parameter>
> >         <parameter name="ServiceClass">
> >                         services.ACLAndAuthServiceSkeleton
> >                 </parameter>
> >         <parameter name="useOriginalwsdl">true</parameter>
> >         <parameter name="modifyUserWSDLPortAddress">true</parameter>
> >         <operation name="authenticate"
> > mep="http://www.w3.org/ns/wsdl/in-out"; namespace="http://foundation.com";>
> >             <actionMapping>urn:authenticate</actionMapping>
> >             <outputActionMapping>
> >                                 urn:authenticateResponse
> >                         </outputActionMapping>
> >             <faultActionMapping faultName="AuthenticationException">
> >                                 urn:authenticateAuthenticationException
> >                         </faultActionMapping>
> >         </operation>
> >         <operation name="retrieveAcl" mep="http://www.w3.org/ns/wsdl/in-out";
> > namespace="http://foundation.com";>
> >             <actionMapping>urn:retrieveAcl</actionMapping>
> >             <outputActionMapping>
> >                                 urn:retrieveAclResponse
> >                         </outputActionMapping>
> >             <faultActionMapping faultName="AclRetrievalException">
> >                                 urn:retrieveAclAclRetrievalException
> >                         </faultActionMapping>
> >         </operation>
> >     </service>
> > </serviceGroup>
> >
> > Dwipin Chandran
> > Tata Consultancy Services
> > Discoverer Bldg, 4th Floor
> > International Technology Park Ltd, Whitefield Road
> > Bangalore - 560066,Karnataka
> > India
> > Mailto: [EMAIL PROTECTED]
> > Website: http://www.tcs.com
> > ____________________________________________
> > Experience certainty.        IT Services
> >                        Business Solutions
> >                        Outsourcing
> > ____________________________________________
> >
> >
> > "robert lazarski" <[EMAIL PROTECTED]>
> >
> > 06/02/2008 07:03 PM
> >
> > Please respond to
> > [email protected]
> > To
> > [email protected]
> > cc
> > Subject
> > Re: Spring service bean not initialized in the skeleton class.
> >
> >
> >
> >
> > To have the skeleton and the spring service bean get linked, you need
> > to manually tweak your services.xml . Try that, and if you still have
> > problems, paste your services.xml .
> >
> > Robert
> >
> > On Mon, Jun 2, 2008 at 10:29 AM, Dwipin C <[EMAIL PROTECTED]> wrote:
> >>
> >> Hi Robert,
> >>         I have the required web.xml entries -
> >>
> >>         <listener>
> >>
> >>
> >> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
> >>         </listener>
> >>         <context-param>
> >>               <param-name>contextConfigLocation</param-name>
> >>               <param-value>/WEB-INF/applicationContext.xml</param-value>
> >>         </context-param>
> >>
> >>         From the spring logs, I can see the beans being initialised. Its
> >> just that axis skeleton and the spring service bean did not get linked.
> >> I couldnt find anything in the server log too.
> >>
> >> Thanks and Regards,
> >> Dwipin Chandran
> >> Tata Consultancy Services
> >> Discoverer Bldg, 4th Floor
> >> International Technology Park Ltd, Whitefield Road
> >> Bangalore - 560066,Karnataka
> >> India
> >> Mailto: [EMAIL PROTECTED]
> >> Website: http://www.tcs.com
> >> ____________________________________________
> >> Experience certainty.        IT Services
> >>                        Business Solutions
> >>                        Outsourcing
> >> ____________________________________________
> >>
> >>
> >> "robert lazarski" <[EMAIL PROTECTED]>
> >>
> >> 06/02/2008 06:34 PM
> >>
> >> Please respond to
> >> [email protected]
> >> To
> >> [email protected]
> >> cc
> >> Subject
> >> Re: Spring service bean not initialized in the skeleton class.
> >>
> >>
> >>
> >>
> >> The way you describe your service, you would need some web.xml entries
> >> to load spring, ie, axis2 expects spring to be configured when using
> >> SpringServletContextObjectSupplier. By putting spring in debug, you
> >> should see it initializing correctly - in which case axis2 should be
> >> able to find it. If you can start spring, but axis2 can't find it -
> >> try looking at the servlet container logs. If you still have problems
> >> after all that, let us know.
> >>
> >> HTH,
> >> Robert
> >>
> >> On Mon, Jun 2, 2008 at 9:54 AM, Dwipin C <[EMAIL PROTECTED]> wrote:
> >>>
> >>> Hi,
> >>>         I am in the process of integrating Axis2 with Spring2.5.
> >>> Scenario -
> >>> I have created the aar with the xsds, services.xml, the wsdl file.
> >>> The rest of my classes are present under the WEB-INF/classes folder and
> >>> the
> >>> dependant jars in the WEB-INF/lib of the axis2 app.
> >>> I've updated the services.xml to have the "serviceObjectSupplier" as
> >>>
> >>>
> >>> "org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier"
> >>> and "SpringBeanName" set as the skeleton class.
> >>>
> >>> When I call this web-service, I get a NullpointerException from this
> >>> skeleton class because the service (which is supposed to be injected by
> >>> Spring) class was not initialised.
> >>> I am not sure if I've missed out something here; Any help or pointers
> >>> would
> >>> be of great help.
> >>>
> >>> Thanks,
> >>> Dwipin Chandran
> >>>
> >>> ForwardSourceID:NT00014DF2
> >>> ForwardSourceID:NT00014E02
> >>>
> >>> =====-----=====-----=====
> >>> Notice: The information contained in this e-mail
> >>> message and/or attachments to it may contain
> >>> confidential or privileged information. If you are
> >>> not the intended recipient, any dissemination, use,
> >>> review, distribution, printing or copying of the
> >>> information contained in this e-mail message
> >>> and/or attachments to it are strictly prohibited. If
> >>> you have received this communication in error,
> >>> please notify us by reply e-mail or telephone and
> >>> immediately and permanently delete the message
> >>> and any attachments. Thank you
> >>>
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >> ForwardSourceID:NT00014E1A
> >>
> >> =====-----=====-----=====
> >> Notice: The information contained in this e-mail
> >> message and/or attachments to it may contain
> >> confidential or privileged information. If you are
> >> not the intended recipient, any dissemination, use,
> >> review, distribution, printing or copying of the
> >> information contained in this e-mail message
> >> and/or attachments to it are strictly prohibited. If
> >> you have received this communication in error,
> >> please notify us by reply e-mail or telephone and
> >> immediately and permanently delete the message
> >> and any attachments. Thank you
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > ForwardSourceID:NT00014E22
> >
> > =====-----=====-----=====
> > Notice: The information contained in this e-mail
> > message and/or attachments to it may contain
> > confidential or privileged information. If you are
> > not the intended recipient, any dissemination, use,
> > review, distribution, printing or copying of the
> > information contained in this e-mail message
> > and/or attachments to it are strictly prohibited. If
> > you have received this communication in error,
> > please notify us by reply e-mail or telephone and
> > immediately and permanently delete the message
> > and any attachments. Thank you
> >
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

_________________________________________________________________
Change the world with e-mail. Join the i’m Initiative from Microsoft.
http://im.live.com/Messenger/IM/Join/Default.aspx?source=EML_WL_ChangeWorld

Reply via email to