Axis2[1.0] missing POM file on Maven2 repository
Axis2 Team, Is it possible to upload a axis2 1.0 pom.xml on maven2 repository. http://www.ibiblio.org/maven2/axis2/axis2/1.0/ I get this error if pom file is not uploaded, when I manually added my dependencies. May this is maven2 problem Project ID: ws-commons:axiom-impl Reason: Error getting POM for 'ws-commons:axiom-impl' from the repository: Error transferring file ws-commons:axiom-impl:pom:1.0 (Internal repository, running maven-proxy) from the specified remote repositories: central (http://flygon.liquid.com:/repository) Thanks Gopal -- View this message in context: http://www.nabble.com/Axis2-1.0-+missing+POM+file+on+Maven2+repository-t1687923.html#a4580015 Sent from the Axis - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2[1.0] war in Weblogic 9.1
Thanks guys, now I am more clear weblogic 9.1 behaviour with axis2.war I like 2nd option b'cos with 1st option I can't deploy exploded war in production -Gopal -- View this message in context: http://www.nabble.com/Axis2-1.0-+war+in+Weblogic+9.1-t1685447.html#a4579488 Sent from the Axis - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2[1.0] war in Weblogic 9.1
I tried axis2.war deploying on weblogic 9.1 as war, deployment was sucessful but unable to load version service. But if I use exploded war it works.. Any idea why it's happening, did any one had success runing axis2.war under weblogic 9.1 Thanks Gopal -- View this message in context: http://www.nabble.com/Axis2-1.0-+war+in+Weblogic+9.1-t1685447.html#a4571990 Sent from the Axis - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2[1.0] BUG in WSDL2Java Error running test
Is this is a BUG I have used WSDL2Java to generate code and test class, Axis2 1.0, I get this error when I run it, I have copied schema and wsdl to can recreate this problem after generating code from WSDL2Java and running test I get this problem with all my wsdl?? Even I tried with sample Axis2SampleDocLit.wsdl from axis2 distribution Testcase: testHelloWorldOperation took 1.059 sec Caused an ERROR java.lang.IllegalStateException org.apache.axiom.om.OMException: java.lang.IllegalStateException at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:206) at org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:144) at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:322) at org.apache.axis2.HelloWorldStub.toOM(HelloWorldStub.java:302) at org.apache.axis2.HelloWorldStub.toEnvelope(HelloWorldStub.java:317) at org.apache.axis2.HelloWorldStub.HelloWorldOperation(HelloWorldStub.java:119) at org.apache.axis2.HelloWorldTest.testHelloWorldOperation(HelloWorldTest.java:30) Caused by: java.lang.IllegalStateException at org.apache.xmlbeans.impl.store.Jsr173$XMLStreamReaderForString.next(Jsr173.java:1110) at org.apache.xmlbeans.impl.store.Jsr173$SyncedJsr173.next(Jsr173.java:1138) at org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:68) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:123) ... 21 more -- HelloWorld.wsdl http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:tns="http://www.liquid.com/ns/keystone/helloworld"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; name="HelloWorld" targetNamespace="http://www.liquid.com/ns/keystone/helloworld"; xmlns:ass="http://www.liquid.com/ns/keystone/asset";> http://www.liquid.com/ns/keystone/asset"; location="asset.xsd"> http://schemas.xmlsoap.org/soap/http"/> http://la00771.liquid.com:8080/axis2/services/helloWorld"/> asset.xsd http://www.w3.org/2001/XMLSchema"; xmlns:ns1="http://www.liquid.com/ns/keystone/asset"; targetNamespace="http://www.liquid.com/ns/keystone/asset"; elementFormDefault="qualified" attributeFormDefault="unqualified"> -- View this message in context: http://www.nabble.com/Axis2-1.0-+BUG+in+WSDL2Java+Error+running+test-t1685417.html#a4571923 Sent from the Axis - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 1.0 AbstractInOnlyAsyncMessageReceiver
Any plans for AbstractInOnlyAsyncMessageReceiver. I have check source code but unable to fine InOnly Async receiver. We need to use InOnly receiver for BPEL async process, I have a copy AbstractInOutAsyncMessageReceiver and Utils classes in my service with minor fix to Utils class >From AbstractInOnlyAsyncMessageReceiver line 58: MessageContext newmsgCtx = Utils.createOutMessageContext(messageCtx); I made some changes to Utils.createOutMessageContext(messageCtx) to make it work not sure that is correct approach. Added out only operation to new message context in Utils class OutOnlyAxisOperation outOnly = new OutOnlyAxisOperation(); OperationContext optCtx = new OperationContext(outOnly); // newmsgCtx.setOperationContext(inMessageContext.getOperationContext()); newmsgCtx.setOperationContext(optCtx); //newmsgCtx.setServiceContext(inMessageContext.getServiceContext()); Thanks Gopal Patwa -- View this message in context: http://www.nabble.com/Axis2-1.0-AbstractInOnlyAsyncMessageReceiver-t1561832.html#a4241714 Sent from the Axis - User forum at Nabble.com.
Re: Axis2 1.0 RC1 Weblogic 9.1 installation problem
Does anybody treid Axis2 on Weblogic 9.1 -- View this message in context: http://www.nabble.com/Axis2-1.0-RC1-Weblogic-9.1-installation-problem-t1495632.html#a4223798 Sent from the Axis - User forum at Nabble.com.
Re: does axis2 always mangle the wsdl file
What I got information from Deepal, if you try to access wsdl from http://my.endpoint.com/service?wsdl it will always generate new one. But still uses the wsdl you have specified in meta-inf folder. The workaround for this problem we had, to copy your wsdl which in meta-inf folder also to some other location where it is accessible to client. I had deployed same wsdl in http://localhost:8080/axis2/mywsdl.wsdl so my client can see this wsdl Not sure sure if it will fix in 1.0 release, I was using RC1 Hope this help Gopal Patwa -- View this message in context: http://www.nabble.com/does-axis2-always-mangle-the-wsdl-file-t1507411.html#a4089081 Sent from the Axis - User forum at Nabble.com.
Axis2 1.0 RC1 Weblogic 9.1 installation problem
H Developesi, I am trying to install Axis2 1.0 RC1 war on weblogic 9.1 through it console as war file. Installation seems sucessful but I am unable to see Any service (default version.aar) or module deployed (default addressing-SNAPSHOT.mar). Even I cann't deployed any services. Does Weblogic is able to understand Axis2 service archive (.aar) and modules (.mar) files. Did anybody got sucess using Axis2 and Wblogic 9.1 Thanks Gopal -- View this message in context: http://www.nabble.com/Axis2-1.0-RC1-Weblogic-9.1-installation-problem-t1495632.html#a4053735 Sent from the Axis - User forum at Nabble.com.
Re: Having problem in-only operation calling through stub
try using RPCInOnlyMessageReceiver or if you need better control on message create your owm message receiver which override invokeBusinessLogic method. or try using WSDL2Java it will generate for you. Hope it helps Gopal -- View this message in context: http://www.nabble.com/Having-problem-in-only-operation-calling-through-stub-t1476382.html#a4001190 Sent from the Axis - User forum at Nabble.com.
Axis2 1.0 RC1 WSDL2Java error when import WS-Addressing
When I have WS-Addressing schema imported in my wsdl, I get this error running WSDL2Java -uri C:\gpatwa\workspace\BPELAxisAsyncTest\tmp\HelloWorldAsync.wsdl -a on -ss -sd -d xmlbeans -o C:\gpatwa\workspace\BPELAxisAsyncTest\tmp -p com.liquid.helloworld Both xmlbeans and JAxme throws error. Retrieving schema at 'http://www.w3.org/2006/03/addressing/ws-addr.xsd', relative to 'file:/C:/gpatwa/workspace/BPELAxisAsyncTest/tmp/'. Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: cvc-complex-type.2.4b: Element not allowed: [EMAIL PROTECTED]://www.w3.org/2001/XMLSchema in element [EMAIL PROTECTED]://www.w3.org/2001/XMLSchema at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:185) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: cvc-complex-type.2.4b: Element not allowed: [EMAIL PROTECTED]://www.w3.org/2001/XMLSchema in element [EMAIL PROTECTED]://www.w3.org/2001/XMLSchema at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:140) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:140) ... 2 more Caused by: org.apache.xmlbeans.XmlException: error: cvc-complex-type.2.4b: Element not allowed: [EMAIL PROTECTED]://www.w3.org/2001/XMLSchema in element [EMAIL PROTECTED]://www.w3.org/2001/XMLSchema at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:665) at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:117) ... 3 more -- View this message in context: http://www.nabble.com/Axis2-1.0-RC1-WSDL2Java-error-when-import-WS-Addressing-t1471363.html#a3978572 Sent from the Axis - User forum at Nabble.com.
BPEL and Axis2 Asynchronous
Hi Developers, I am using axis2 async service with Oracle BPEL and I want to use AsyncMessageReceiver from inetegration module in SVN. BPEL need In-Only type for Async but AsyncMessageReceiver extend AbstractInOutAsyncMessageReceiver type Any suggestion?? is there any In-Only type AsyncMessageReceiver extend AbstractInAsyncMessageReceiver. Or do I missing something here !! Note: I got successful working with In-Only way and using ServiceClient to make Call to BPEL process with fireAndForget method but this methode create always new Message Context to call EPR, so how to specify existing Messsage Context to this method. But I want to use AsyncMessageReceiver so thread and resources management can be handle by axis2 engine. Thanks Gopal -- View this message in context: http://www.nabble.com/BPEL-and-Axis2-Asynchronous-t1469698.html#a3973256 Sent from the Axis - User forum at Nabble.com.
Re: [Axis2 1.0 RC1] User defined WSDL
Thanks Deepal, I had 2 port type in my wsdl and it completely ignore portType HelloWorldAsyncCallback only one portType is displayed HelloWorldAsync. I have BPEL client whose is going to invoke this service and I want him to see same wsdl which I created not the generated one, work around for this problem I manually copy same wsdl in some webapp location like http://localhost:8080/axis2/HelloWorld.wsdl and BPEL access this WSDL Instead of http://localhost:8080/axis2/services/HelloWorld?wsdl Thanks Gopal -- View this message in context: http://www.nabble.com/-Axis2-1.0-RC1-User-defined-WSDL-t1460029.html#a3946362 Sent from the Axis - User forum at Nabble.com.
Re[Axis2 1.0RC1]: Small changing in Service implementation class
Thanks Deepal, I already made changes according to Chintaka. Now I have BPEL to Axis2 asynchronous echo service working, earlier when I was invoking BPEL process as Callback from server, I was usning Axis2 client to make callback like ServiceClient sender = new ServiceClient(); sender.engageModule(new QName(Constants.MODULE_ADDRESSING)); And this use to throw null pointer error, infact I don't need to engage module b'cos my service and client both running on server side with globally engage addressing module. Since I was creating new service client instead from existing current context like ServiceClient sender = new ServiceClient(msgContext.getConfigurationContext(), msgContext.getAxisService()); And this take care of addressing in SOAP Header. I still have some issue to fix 1) Specifying userdefined wsdl and let axis2 uses my custome wsdl instead of generating new one( I did meta-inf/services.wsdl in service archive but same result) 2) Getting error from WSDL2Java when importing ws-addressing schema in wsdl http://www.w3.org/2001/XMLSchema";> http://schemas.xmlsoap.org/ws/2004/08/addressing"; schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing"/> You can try yourself , I tried with Xmlbean and Jaxme I am going to use AsyncMessageReceiver example from integration folder in SVN to make call back to BPEL process instead of using ServiceClient. I am not sure it will work without making some changes , I will update the result. Thanks Gopal -- View this message in context: http://www.nabble.com/-Axis2-1.0RC1-Problem-getting-MessageContext-in-ServiceImpl-class-t1423137.html#a3946331 Sent from the Axis - User forum at Nabble.com.
Re: [Axis2 1.0 RC1] User defined WSDL
Thanks for reply, I have same service name (HelloWorld) and service archive (HelloWorld.aar) Even I tried changing wsdl file name from HelloWorld.wsdl to services.wsdl but nothing change it's still same result Does anybody tried using user defined wsdl and it worked successfuly showing user defined wsdl when try to acccess from url http://localhost:8080/axis2/services/HelloWorld?wsdl instead of new one -Gopal Ajith Ranabahu wrote: > > Hi, > is the service name equal to the name of your sevice (name of the .aar > file) ? > > Ajith > > On 4/17/06, Inoguchi, Kinichiro <[EMAIL PROTECTED]> wrote: >> Gopal, >> >> I think HelloWorld.wsdl should be services.wsdl. >> >> >> -Original Message- >> From: Gopal Patwa [mailto:[EMAIL PROTECTED] >> Sent: Monday, April 17, 2006 1:13 PM >> To: axis-user@ws.apache.org >> Subject: [Axis2 1.0 RC1] User defined WSDL >> >> >> >> >> I havve user defined wsdl and added wsdl file into META-INF directory >> and deploy >> to service archive file look like below; >> >> HelloWorld.aar >> META-INF >> HelloWorld.wsdl >> services.xml >> com >> test >>helloworld >>hello.class >> >> But still when I access my wsdl from browser it is different than user >> defined >> >> I am still wonder why it doesn't show the wsdl which I provided in >> service archive instead of generating new one. >> >> How to stop Axis2 to generating wsdl and use which is provided in >> service archive under meta-inf folder. >> >> Is there something I am doing wrong?? >> >> Please help >> >> Thanks >> Gopal >> -- >> View this message in context: >> http://www.nabble.com/-Axis2-1.0-RC1-User-defined-WSDL-t1460029.html#a39 >> 45891 >> Sent from the Axis - User forum at Nabble.com. >> >> > > > -- > Ajith Ranabahu > > -- View this message in context: http://www.nabble.com/-Axis2-1.0-RC1-User-defined-WSDL-t1460029.html#a3946202 Sent from the Axis - User forum at Nabble.com.
[Axis2 1.0 RC1] User defined WSDL
I havve user defined wsdl and added wsdl file into META-INF directory and deploy to service archive file look like below; HelloWorld.aar META-INF HelloWorld.wsdl services.xml com test helloworld hello.class But still when I access my wsdl from browser it is different than user defined I am still wonder why it doesn't show the wsdl which I provided in service archive instead of generating new one. How to stop Axis2 to generating wsdl and use which is provided in service archive under meta-inf folder. Is there something I am doing wrong?? Please help Thanks Gopal -- View this message in context: http://www.nabble.com/-Axis2-1.0-RC1-User-defined-WSDL-t1460029.html#a3945891 Sent from the Axis - User forum at Nabble.com.
Re: [Axis2 1.0RC1] Problem getting MessageContext in ServiceImpl class
let me clear couple of things, even if my service runing in tomcat with axis2 webapp with addressing module engage globaly but if my service Impl class uses ServiceClient class to call BPEL process does it will be running in different environment. here is scenario, I have an asynchronous echo service which uses ServiceClient to Callback BPEL after some time when process is done and everything is running in server under tomcat. Only for debugging I am running tomcat in debug mode in eclipse to step through my service which deployed on tomcat server. Still my code will run in different environment if it uses ServiceClient class.?? Thanks for reply Chinthaka. Eran Chinthaka wrote: > > Gopal Patwa wrote: >> Thanks Chinthaka, It work now but I have some other problem. >> >> I have wrote axis2 asynchronous service to work with BPEL. When I am >> trying >> to call BPEL service while to engaging addressing module >> >> ServiceClient sender = new ServiceClient(); >> sender.engageModule(new QName(Constants.MODULE_ADDRESSING)); >> >> Note: this code run on tomcat 5.5 not from some java client >> >> I get module not found, since my service is deployed in tomcat 5.5 with >> axis >> 1.0RC1 webapp and globally engage addressing module which I can see from >> admin page. > > You have engaged addressing in server side. Client is running in a > different environment. > >> >> Do I need to engage addressing module for ServiceClient even I have >> globally >> set for all service >> >> When I am debugging my service in eclipse 3.1, I see error module not >> found >> ?? after this line of code >> >> sender.engageModule(new QName(Constants.MODULE_ADDRESSING)); >> >> any idea why it is happening > > Hmm, it seems I better update the FAQ abt this. > > When you run your client, try putting addressing-.mar in your > classpath. > > -- Chinthaka > > > -- View this message in context: http://www.nabble.com/-Axis2-1.0RC1-Problem-getting-MessageContext-in-ServiceImpl-class-t1423137.html#a3875656 Sent from the Axis - User forum at Nabble.com.
Re: [Axis2 1.0RC1] Problem getting MessageContext in ServiceImpl class
Thanks Chinthaka, It work now but I have some other problem. I have wrote axis2 asynchronous service to work with BPEL. When I am trying to call BPEL service while to engaging addressing module ServiceClient sender = new ServiceClient(); sender.engageModule(new QName(Constants.MODULE_ADDRESSING)); Note: this code run on tomcat 5.5 not from some java client I get module not found, since my service is deployed in tomcat 5.5 with axis 1.0RC1 webapp and globally engage addressing module which I can see from admin page. Do I need to engage addressing module for ServiceClient even I have globally set for all service When I am debugging my service in eclipse 3.1, I see error module not found ?? after this line of code sender.engageModule(new QName(Constants.MODULE_ADDRESSING)); any idea why it is happening Thanks Gopal -- View this message in context: http://www.nabble.com/-Axis2-1.0RC1-Problem-getting-MessageContext-in-ServiceImpl-class-t1423137.html#a3874474 Sent from the Axis - User forum at Nabble.com.
Re: [Axis2 1.0RC1] Problem getting MessageContext in ServiceImpl class
Anybody from developer?? Why I am getting NullPointerException for
MessageContext.
I have tried below method also but both MessageContext and OperationContext
are Null
public void setOpctx(OperationContext opctx) {
this.opctx = opctx;
}
init(MessageContext msgContext) use to work in 0.95 but not anymore in
1.0RC1 (Tomcat 5.5 app server)
thanks
Gopal
--
View this message in context:
http://www.nabble.com/-Axis2-1.0RC1-Problem-getting-MessageContext-in-ServiceImpl-class-t1423137.html#a3853507
Sent from the Axis - User forum at Nabble.com.
Small changing in Service implementation class
I am wondering does below propose from Deepal change is included in axis2
1.0 RC1.
I had init method in my service implementation class to get access SOAP
header from MessageContext to read ws-addressing information but after
migrating to 1.0RC1 my msgContext is always null, does this method still
support or there is method signature change.
public void init(MessageContext msgContext) {
this.msgContext = msgContext;
}
===
Previous mail from Deepal, I am posting this message for reference couldn't
find the thread .
Hi all;
To support the scenario describe by the JIRA
http://issues.apache.org/jira/browse/AXIS2-341 , it is require to do
small changes into service implementation class.
In the current code base in order to get access to message context he
has to add init method , and if the init method is present , it will
call for each and every invocation. (init method can take one message
context or two message context). I propose to change that to get
operation context instead of message context and rename method to
setOperationContext(OperationContext opctx);
When the session get start up , the init() method of the service class
will be called (using reflection) if it is present. And method will be
given the serviceContext corresponds to that service.
init(ServiceContext serviceCtx)
When the session get invalidate destroy method of the service impl class
will be called if it present giving ServiceContext as argument.
destroy(ServiceContext serviceCtx);
--
Thanks,
Deepal
~Future is Open~
--
View this message in context:
http://www.nabble.com/Small-changing-in-Service-implementation-class-t1423137.html#a3836353
Sent from the Axis - User forum at Nabble.com.
Re: unable to get soap header in Axis2
Axis2 0.95 on Tomcat 5.5, even I tried using wsdl from source /axis2/modules/codegen/test-resources/headers.wsdl and generated server code form WSDL2Java and included headers.wsdl in service archive, it read the wsdl but still has same result no soap header. Thanks GopalOn 4/3/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: Hi Gopal;is this happen in 0.95 or current code base ?Gopal Patwa wrote:> Anybody from development team ??>> why my soap:header are not appearing on browser when I try to view> from http://localhost:8080/axis2/services/keystone?wsdl even it is> define in my wsdl>> Due to this problem my BPEL process is unable to send ws-addressing > headers>> this output from browser, does Axis2 remove soap:header>>>>"keystone" targetNamespace=" http://org.apache.axis2/">xmlns:tns="http://org.apache.axis2/" xmlns:wsa="> http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns1="http://org.apache.axis2/xsd">xmlns:xs="http://www.w3.org/2001/XMLSchema " xmlns:soap>="http://schemas.xmlsoap.org/wsdl/soap/" xmlns=">http://schemas.xmlsoap.org/wsdl/ ">> >>"http://www.w3.org/2001/XMLSchema" attributeFormDefault="qualified">elementFormDefault="qualified" targetNamespace=" http://schemas.xmlsoap.org/wsdl/> <http://schemas.xmlsoap.org/wsdl/>" xmlns=" http://www.w3.org/2001/XMLSchema">><>import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing" >schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing">/>>>http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace=>"http://org.apache.axis2/xsd " xmlns="http://www.w3.org/2001/XMLSchema> <http://www.w3.org/2001/XMLSchema>">> ><>xs:sequence>>>type="xs:string"/>>>>> > > name="echoAsyncResponse"> >><>xs:element name="return" type="xs:string">/>>> >> name="EchoAsyncRequest" type="ns1:echoAsyncRequest"/>>>>"ns1:echoAsyncResponse"/> >>>> > >> >/>> > >>>>"wsa:MessageID"/>>>element="wsa:ReplyTo"/>> > > name="echoAsyncRequestMessage">>>>>"ns1:EchoAsyncRequest"/> > > >"echoAsyncResponseMessage">>>element="ns1:EchoAsyncResponse"/>> > <>portType name="keystonePortCallBack">>>="onResult">> >/> >>>> > >>> > message="tns:echoAsyncRequestMessage"/> >> >portType>> >="tns:keystonePortCallBack">>>transport="http://schemas.xmlsoap.org/soap/http"/>>>>>> >"document"/>> >>>>="literal" namespace>="http://org.apache.axis2/"/ >>> >>> > >"keystoneBinding" type="tns:keystonePort">>> style="document" transport="http://schemas.xmlsoap.org/soap/http> <http://schemas.xmlsoap.org/soap/http >"/>>>>> >="document"/>> >>>>="literal" namespace>="http://org.apache.axis2/"/>>> >> > > >"keystone">>>="tns:keystoneBinding">> http://localhost:8080/axis2/services/keystone"/>>>>> > >"keystoneCallBack">>>="tns:keystoneBinding">> http://localhost:8080/axis2/services/keystone"/>>> >>>definitions>>>>>> On 3/31/06, *Gopal Patwa* < [EMAIL PROTECTED]> [EMAIL PROTECTED]>> wrote:>> Hi,>> I have custom wsdl with just an echo service which contain soap > header as input for action but when I view my wsdl from browser it> does not show up the soap header part??>> Any help ??, let me if anything wrong in wsdl it self>> Thanks > Gopal>> my wsdl file>> > > targetNamespace=" http://org.apache.axis2/" xmlns:tns="> http://org.apa
Re: unable to get soap header in Axis2
Anybody from development team ?? why my soap:header are not appearing on browser when I try to view from http://localhost:8080/axis2/services/keystone?wsdl even it is define in my wsdl Due to this problem my BPEL process is unable to send ws-addressing headers this output from browser, does Axis2 remove soap:header <definitions name= "keystone" targetNamespace="http://org.apache.axis2/" xmlns:tns="http://org.apache.axis2/" xmlns:wsa=" http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns1="http://org.apache.axis2/xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap ="http://schemas.xmlsoap.org/wsdl/soap/" xmlns=" http://schemas.xmlsoap.org/wsdl/"> <types><xs:schema xmlns:xs= "http://www.w3.org/2001/XMLSchema" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://schemas.xmlsoap.org/wsdl/ " xmlns="http://www.w3.org/2001/XMLSchema">< import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing" schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing" />xs:schema><xs:schema xmlns:xs=" http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace= "http://org.apache.axis2/xsd" xmlns="http://www.w3.org/2001/XMLSchema "> <xs:complexType name="echoAsyncRequest">< xs:sequence><xs:element name="param1" type="xs:string"/> xs:sequence> xs:complexType><xs:complexType name="echoAsyncResponse"><xs:sequence>< xs:element name="return" type="xs:string" />xs:sequence> xs:complexType> <xs:element name="EchoAsyncRequest" type="ns1:echoAsyncRequest"/ ><xs:element name="EchoAsyncResponse" type= "ns1:echoAsyncResponse"/>xs:schema> types> <message name="ContinueHeader"> <part name="RelatesTo" element="wsa:RelatesTo" /> message> <message name="StartHeader" ><part name="MessageID" element= "wsa:MessageID"/><part name="ReplyTo" element="wsa:ReplyTo"/> message> <message name="echoAsyncRequestMessage"> <part name="part1" element= "ns1:EchoAsyncRequest"/> message> <message name= "echoAsyncResponseMessage"><part name="part2" element="ns1:EchoAsyncResponse"/> message> < portType name="keystonePortCallBack"><operation name ="onResult"> <input message="tns:echoAsyncResponseMessage" />operation> portType> <portType name="keystonePort"> <operation name="echoAsync"> <input message="tns:echoAsyncRequestMessage"/>operation> portType> <binding name="keystoneCallBackBinding" type ="tns:keystonePortCallBack"><soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/ ><operation name="onResult"> <soap:operation soapAction="onResult" style= "document"/> <input ><soap:body use ="literal" namespace ="http://org.apache.axis2/"/ > input> operation> binding> <binding name= "keystoneBinding" type="tns:keystonePort"><soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http "/><operation name="echoAsync"> <soap:operation soapAction="echoAsync" style ="document"/> <input ><soap:body use ="literal" namespace ="http://org.apache.axis2/"/ > input> operation> binding> <service name= "keystone"><port name="keystonePort0" binding ="tns:keystoneBinding"> <soap:address location=" http://localhost:8080/axis2/services/keystone"/> port> service> <service name= "keystoneCallBack"><port name="keystonePort0" binding ="tns:keystoneBinding"> <soap:address location=" http://localhost:8080/axis2/services/keystone"/>port> service> defi
unable to get soap header in Axis2
Hi, I have custom wsdl with just an echo service which contain soap header as input for action but when I view my wsdl from browser it does not show up the soap header part?? Any help ??, let me if anything wrong in wsdl it self Thanks Gopal my wsdl file http://org.apache.axis2/" xmlns:tns="http://org.apache.axis2/" xmlns:ns1="http://org.apache.axis2/xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"> targetNamespace="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema"> http://schemas.xmlsoap.org/ws/2004/08/addressing" schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing" /> http://www.w3.org/2001/XMLSchema" targetNamespace="http://org.apache.axis2/xsd"> http://schemas.xmlsoap.org/soap/http" /> part="MessageID" use="literal"/> part="ReplyTo" use="literal"/> http://schemas.xmlsoap.org/soap/http" /> part="RelatesTo" use="literal"/> http://localhost:8080/axis2/services/keystone"/> http://set.by.caller"/>
BPEL and Axis2 Asynchronous service
I am in process of writing some BPEL process with Oracle BPM and using Axis2 for Asynchronous weberservice. Does anybody have sample example or experince with BPEL and Axis2 asynchronous service interaction. Thanks Gopal
