Details
-
Type: Improvement
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: PicoContainer (Java)
-
Labels:None
-
Environment:Depends upon picoextras -integrationkit and -servlet (tested against snapshots from 2004-02-02), and Axis-1.1
-
Number of attachments :
Description
I'm using the attached provider classes with Axis to resolve dependancies for my Axis service classes, and thought I'd contribute them to see if anyone's interested. The provider class works the same as the webwork action factory, so requires a ContainerComposer to be registered.
Usage (steps 1 and 2 as per the servlet/webwork integration):
1. Register the servlet container listener in web.xml:
<listener>
<listener-class>org.picoextras.servlet.ServletContainerListener</listener-class>
</listener>
2. Register a container composer in web.xml to handle your component registrations:
<context-param>
<param-name>assembler</param-name>
<param-value>com.company.WebContainerComposer</param-value>
</context-param>
3. Register your service in your Axis WSDD using the custom provider:
<service name="MyService" provider="Handler">
<parameter name="handlerClass" value="com.picoextras.axis.PicoRPCProvider"/>
<parameter name="className" value="com.company.MyService"/>
<parameter name="allowedMethods" value="*"/>
</service>
or if you want to use message-style encoding use com.picoextras.axis.PicMsgProvider.
cheers,
Evan.
Activity
Field | Original Value | New Value |
---|---|---|
Attachment | PicoMsgProvider.java [ 11332 ] |
Attachment | PicoRPCProvider.java [ 11333 ] |
Attachment | PicoAxisServlet.java [ 11342 ] |
Status | Open [ 1 ] | Closed [ 6 ] |
Assignee | Aslak Hellesoy [ rinkrank ] | |
Resolution | Fixed [ 1 ] |
Forgot to attach the PicoAxisServlet. This replaces the standard axis servlet in web.xml:
<servlet>
<servlet-name>AxisServlet</servlet-name>
<display-name>Apache-Axis Servlet</display-name>
<servlet-class>
org.picoextras.axis.PicoAxisServlet
</servlet-class>
</servlet>