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
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:
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 -
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
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.
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:
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
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.
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
:
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
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();
Thanks Deepal,
I had 2 port type in my wsdl
portType name=HelloWorldAsync
operation name=initiate
input message=tns:HelloWorldAsyncRequestMessage/
/operation
/portType
portType name=HelloWorldAsyncCallback
operation name=onResult
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
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
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
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
soap:address location=
http://localhost:8080/axis2/services/keystone/
/port /service service name=
keystoneCallBackport name=keystonePort0 binding
=tns:keystoneBinding soap:address location=
http://localhost:8080/axis2/services/keystone//port /service/
definitions
On 3/31/06, Gopal
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
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
?xml version=1.0 encoding=UTF-8?
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
20 matches
Mail list logo
