[
http://jira.codehaus.org/browse/XFIRE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boletho updated XFIRE-1051:
---------------------------
Attachment: ModifiedNotWorking-Xfire-Servlet.xml
Never mind this bug! I have solved it on my own.
Following are the steps to handle ws addressing for anybody who has problem
finding documentation. Look at *ModifiedNotWorking-Xfire-Servlet.xml* file for
complete *WORKING* example.
In your *xfire-servlet.xml*
1. add a bean which extends *ObjectServiceFactory* and takes at least two
parameters, the default transport manager and default aegis binding provider.
See below :
bq
{color:green}
<bean id="wsaServiceFactory"
class="com.argushealth.enterprise.webservice.xfire.servicefactory.WsaObjectServiceFactory"
singleton="true">
<constructor-arg index="0">
<ref bean="xfire.transportManager" />
</constructor-arg>
<constructor-arg index="1">
<ref bean="xfire.aegisBindingProvider" />
</constructor-arg>
<constructor-arg
index="2"><value>urn:getHelloWorld</value></constructor-arg>
</bean>
{color}
2. add the bean as service factroy
bq
{color:green}
<property name="serviceFactory">
<ref bean="wsaServiceFactory" />
</property>
{color}
3. add address in handler and change your action value from just
*UserNameToken* to *UserNameToken Timestamp* (and yes! order matters!)
bq
{color:green}
<property name="inHandlers">
<list>
<bean class="org.codehaus.xfire.util.dom.DOMInHandler" />
<bean class="org.codehaus.xfire.addressing.AddressingInHandler" />
<bean
class="org.codehaus.xfire.security.wss4j.WSS4JInHandler">
<property name="properties">
<map>
<entry key="passwordCallbackRef" >
<ref bean="userNameTokenPasswordCallback" />
</entry>
<entry key="action" value="UsernameToken Timestamp" />
</map>
</property>
</bean>
<!-- look in applicationContext_ws-security.xml for definition -->
<ref bean="customerNumberAuthorizationHandler" />
<ref bean="userAuthorizationHandler" />
<ref bean="userNameTokenValidationHandler"/>
</list>
</property>
{color}
4. add address out handler
bq
{color:green}
<property name="outHandlers">
<list>
<bean
class="org.codehaus.xfire.addressing.AddressingOutHandler"> </bean>
</list>
</property>
{color}
{color:red}
Please close this bug.
{color}
> Invalid wsdlsoap:address location is created when using custom service
> factory.
> -------------------------------------------------------------------------------
>
> Key: XFIRE-1051
> URL: http://jira.codehaus.org/browse/XFIRE-1051
> Project: XFire
> Issue Type: Bug
> Affects Versions: 1.2.5
> Environment: WAS 6.0, Java 1.4, Windows XP SP2
> Reporter: Boletho
> Assignee: Dan Diephouse
> Attachments: ModifiedNotWorking-Xfire-Servlet.xml,
> NotWorking-Xfire-Servlet.xml, web.xml, Working-Xfire-Servlet.xml
>
>
> I have looked around and found two bugs
> (http://jira.codehaus.org/browse/XFIRE-366 and
> http://jira.codehaus.org/browse/XFIRE-243) but they didn't solve my problem.
> I have created a web service and it worked fine, following are the relevant
> configuration files:
> web.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
