Hi Sagara,
Attached is my skeleton class & service.xml files.Thanks Raghu -----Original Message----- From: Sagara Gunathunga [mailto:sagara.gunathu...@gmail.com] Sent: Thursday, April 09, 2009 1:37 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Setting hostname in axis2.xml ???? - NOT WORKING Hi Raghu, Can you post your skeleton class along with service.xml file....? Thanks, On Thu, Apr 9, 2009 at 11:59 PM, Raghu Upadhyayula <rupadhyay...@responsys.com> wrote: > Hi Sagara, > > I have a skeleton class generated from WSDL2Java. I've changed that > skeleton class to implement the ServiceLifeCycle interface & implemented the > startup method. > > Looks like that startup method is never called, because after that > change also I'm getting a private IP address in the soap:address location in > WSDL. I've put a debug point in the startup method & the control never > stopped at the debug point. > > Thanks > Raghu > > -----Original Message----- > From: Sagara Gunathunga [mailto:sagara.gunathu...@gmail.com] > Sent: Tuesday, April 07, 2009 2:36 PM > To: axis-user@ws.apache.org > Subject: Re: [Axis2] Setting hostname in axis2.xml ???? > > Hi Raghu , > You can use same "hostname" parameter programatically either in > service level or module level . one possible approach is given below . > > 1. Implement the "ServiceLifeCycle" interface within your service > class or as a separate class . > > 2. set the value to "hostname" parameter within the startUp ( ...) method. > > axisService.getAxisConfiguration().addParameter("hostname", > "myhost.com"); > > 3. add your LifeCycle class to service.xml file. > > <service name="SimpleService" class="LifeCycleClassName"> > > > Thanks > > > On Tue, Apr 7, 2009 at 9:39 PM, Raghu Upadhyayula > <rupadhyay...@responsys.com> wrote: >> Hi, >> >> >> >> I’m using Axis2 1.4 version. I have to set the hostname in axis2.xml so >> that the soap:address location in the WSDL (when user types ?wsdl) uses that >> hostname instead of showing a IP address. >> >> >> >> The problem I have is that my webservices war file is deployed on multiple >> servers and I can’t manually edit each axis2.xml file for each server. >> >> >> >> Is there any option to read the server name from some properties file & set >> it to the hostname in axis2.xml programmatically? >> >> >> >> Thanks >> >> Raghu > > > > -- > Sagara Gunathunga > > Blog - http://ssagara.blogspot.com > Web - http://sagaras.awardspace.com/ > -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://sagaras.awardspace.com/
<?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="ResponsysWSService">
<messageReceivers>
<messageReceiver mep="http://www.w3.org/ns/wsdl/in-out"; class="com.rsys.ws.ResponsysWSServiceMessageReceiverInOut"/>
</messageReceivers>
<parameter name="ServiceClass">com.rsys.ws.ResponsysWSServiceSkeleton</parameter>
<parameter name="useOriginalwsdl">true</parameter>
<parameter name="modifyUserWSDLPortAddress">true</parameter>
<operation name="login" mep="http://www.w3.org/ns/wsdl/in-out"; namespace="urn:ws.rsys.com">
<actionMapping>\"\"</actionMapping>
<outputActionMapping>urn:ws.rsys.com:ResponsysWS:loginResponse</outputActionMapping>
<faultActionMapping faultName="AccountFault">urn:ws.rsys.com:ResponsysWS:login:Fault:AccountFault</faultActionMapping>
<faultActionMapping faultName="UnexpectedErrorFault">urn:ws.rsys.com:ResponsysWS:login:Fault:UnexpectedErrorFault</faultActionMapping>
</operation>
<operation name="logout" mep="http://www.w3.org/ns/wsdl/in-out"; namespace="urn:ws.rsys.com">
<actionMapping>\"\"</actionMapping>
<outputActionMapping>urn:ws.rsys.com:ResponsysWS:logoutResponse</outputActionMapping>
<faultActionMapping faultName="UnexpectedErrorFault">urn:ws.rsys.com:ResponsysWS:logout:Fault:UnexpectedErrorFault</faultActionMapping>
</operation>
<operation name="createFolder" mep="http://www.w3.org/ns/wsdl/in-out"; namespace="urn:ws.rsys.com">
<actionMapping>\"\"</actionMapping>
<outputActionMapping>urn:ws.rsys.com:ResponsysWS:createFolderResponse</outputActionMapping>
<faultActionMapping faultName="UnexpectedErrorFault">urn:ws.rsys.com:ResponsysWS:createFolder:Fault:UnexpectedErrorFault</faultActionMapping>
<faultActionMapping faultName="FolderFault">urn:ws.rsys.com:ResponsysWS:createFolder:Fault:FolderFault</faultActionMapping>
</operation>
<operation name="listFolders" mep="http://www.w3.org/ns/wsdl/in-out"; namespace="urn:ws.rsys.com">
<actionMapping>\"\"</actionMapping>
<outputActionMapping>urn:ws.rsys.com:ResponsysWS:listFoldersResponse</outputActionMapping>
<faultActionMapping faultName="UnexpectedErrorFault">urn:ws.rsys.com:ResponsysWS:listFolders:Fault:UnexpectedErrorFault</faultActionMapping>
</operation>
<operation name="deleteFolder" mep="http://www.w3.org/ns/wsdl/in-out"; namespace="urn:ws.rsys.com">
<actionMapping>\"\"</actionMapping>
<outputActionMapping>urn:ws.rsys.com:ResponsysWS:deleteFolderResponse</outputActionMapping>
<faultActionMapping faultName="UnexpectedErrorFault">urn:ws.rsys.com:ResponsysWS:deleteFolder:Fault:UnexpectedErrorFault</faultActionMapping>
<faultActionMapping faultName="FolderFault">urn:ws.rsys.com:ResponsysWS:deleteFolder:Fault:FolderFault</faultActionMapping>
</operation>
</service>
</serviceGroup>
ResponsysWSServiceSkeleton.java
Description: ResponsysWSServiceSkeleton.java
