date:20060510

Yah I understand that marking message with Urgent won't help in getting
quick reply from others.Anyways,I want to send a SOAP Envelope in the way
that I don't need to manipulate the requested parameter (OMELEMENT) there to
get the parameters.

I tried it but with no success. Exception is coming:

Cannot find binding operation definition of soapAction '/orabpel' in
http://daff06:9700/orabpel/default/ProcessManager/1.0/ProcessManager.wsdl

My Request was:


My request was: 

?xml version='1.0' encoding='UTF-8'?

soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header /

soapenv:Body

Process:initiateProcess
xmlns:Process=http://services.oracle.com/bpel/Process;Process:primaryKeyV
alue1/Process:primaryKeyValueProcess:businessProcessId1/Process:busine
ssProcessId/Process:initiateProcess/soapenv:Body/soapenv:Envelope


And my ProcessManager.wsdl has no defined SOAP BINDINGS.

Is it necessary to define soap bindings with wsdl.
Why axis2 is taking /orabpel as soapaction?

Thanks
Nancy

-Original Message-
From: Eran Chinthaka [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 10, 2006 1:11 PM
To: axis-user@ws.apache.org
Subject: Re: URGENT Use axis2 to call bpel

Hi Nancy,

First, marking your messages to this list as URGENT won't help you in
any means. Rather it will make the case worse. Opensource developers are
willing and like to help others, but can not be forced to do so (except
you have a private service contract with them ;) ).


nancy wrote:
 Can anyone tell how to use axis 2 to call bpel process. Earlier I was
 using java classes generated by wsdl2java tool of axis1.But now; I don't
 want to use java classes. I want to just mention web service URL,
 message name and parameters.For eg:
 

..


 But using this I need to write code to get result out of OMElement. Or
 you can say I want to know how bpel process can understand the output or
 input of axis2? I am using ORACLE BPEL.
 

Sorry I can not understand this problem. Do you wanna send a SOAPEnvelop
e and get back only the Body first child ? If you can explain a bit more
I might be able to help you.

BTW, Axis2 or any web service engine do not care whether you talk to a
BPEL server or not. It sends out and receive SOAP messages, that's all.

-- Chinthaka

  
 
 Thanks

Axis2 1.0 Ant codegen, extension properties


Hi,

Is it possible to use ant codegen task with extension properties ?

I want to invoke codegen with a jibx databinding and I have this error 
jibx binding option requires -bindingfile {file path} parameter
The only way I have find is to invoke WSDL2java from ant, but I think it 
is a dirty solution.


Thanks
Arnaud

Re: Use axis2 to call bpel

2006-05-10 Thread Eran Chinthaka

Axis2 will never set a non-empty SOAPAction, if you have not called
options.setAction(youraction).

Are u sure you have not called that method.

-- Chinthaka

nancy wrote:
 Yah I understand that marking message with Urgent won't help in getting
 quick reply from others.Anyways,I want to send a SOAP Envelope in the way
 that I don't need to manipulate the requested parameter (OMELEMENT) there to
 get the parameters.
 
 I tried it but with no success. Exception is coming:
 
 Cannot find binding operation definition of soapAction '/orabpel' in
 http://daff06:9700/orabpel/default/ProcessManager/1.0/ProcessManager.wsdl
 
 My Request was:
 
 
 My request was: 
 
 ?xml version='1.0' encoding='UTF-8'?
 
 soapenv:Envelope
 xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header /
 
 soapenv:Body
 
 Process:initiateProcess
 xmlns:Process=http://services.oracle.com/bpel/Process;Process:primaryKeyV
 alue1/Process:primaryKeyValueProcess:businessProcessId1/Process:busine
 ssProcessId/Process:initiateProcess/soapenv:Body/soapenv:Envelope
 
 
 And my ProcessManager.wsdl has no defined SOAP BINDINGS.
 
 Is it necessary to define soap bindings with wsdl.
 Why axis2 is taking /orabpel as soapaction?
 
 Thanks
 Nancy
 
 -Original Message-
 From: Eran Chinthaka [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, May 10, 2006 1:11 PM
 To: axis-user@ws.apache.org
 Subject: Re: URGENT Use axis2 to call bpel
 
 Hi Nancy,
 
 First, marking your messages to this list as URGENT won't help you in
 any means. Rather it will make the case worse. Opensource developers are
 willing and like to help others, but can not be forced to do so (except
 you have a private service contract with them ;) ).
 
 
 nancy wrote:
 Can anyone tell how to use axis 2 to call bpel process. Earlier I was
 using java classes generated by wsdl2java tool of axis1.But now; I don't
 want to use java classes. I want to just mention web service URL,
 message name and parameters.For eg:

 
 ..
 
 
 But using this I need to write code to get result out of OMElement. Or
 you can say I want to know how bpel process can understand the output or
 input of axis2? I am using ORACLE BPEL.

 
 Sorry I can not understand this problem. Do you wanna send a SOAPEnvelop
 e and get back only the Body first child ? If you can explain a bit more
 I might be able to help you.
 
 BTW, Axis2 or any web service engine do not care whether you talk to a
 BPEL server or not. It sends out and receive SOAP messages, that's all.
 
 -- Chinthaka
 
  

 Thanks

 
 
 
 




signature.asc
Description: OpenPGP digital signature

RE: Use axis2 to call bpel

Hi,
I have not used that method. My code is:

Public void invoke(){
Options options = new Options();
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
boolean exit = false;
String serviceGroupContextId = null;
EndpointReference EPR=new EndpointReference(webserviceURL);

options.setTo(EPR);
options.setTimeOutInMilliSeconds(5);

ServiceClient serviceClient;
serviceClient = new ServiceClient();
serviceClient.setOptions(options);  
MessageContext requestMessageContext = new MessageContext();

requestMessageContext.setEnvelope(getRequestEnvelope(messageName,
parametersList,
serviceGroupContextId));

OperationClient opClient = serviceClient
.createClient(ServiceClient.ANON_OUT_IN_OP);
opClient.addMessageContext(requestMessageContext);
opClient.setOptions(options);

opClient.execute(true);
}

private SOAPEnvelope getRequestEnvelope(String operationName,
HashMap param, String groupContextId) {
String namespace1=http://services.oracle.com/bpel/Process;;

SOAPFactory fac = OMAbstractFactory.getSOAP11Factory();
SOAPEnvelope envelope = fac.getDefaultEnvelope();
OMNamespace namespace = fac.createOMNamespace(

namespace1, Process);

OMElement params1 = fac.createOMElement(operationName,
namespace); 
Set set=param.keySet();
Iterator iter=set.iterator();

while(iter.hasNext()){
String paramName=iter.next().toString();
String paramValue=param.get(paramName).toString();
 OMElement paramOM =
fac.createOMElement(paramName,namespace);
 paramOM.setText(paramValue);
 params1.addChild(paramOM);
}
envelope.getBody().setFirstChild(params1);  


return envelope;
} 

Thanks
Nancy

-Original Message-
From: Eran Chinthaka [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 10, 2006 2:34 PM
To: axis-user@ws.apache.org
Subject: Re: Use axis2 to call bpel

Axis2 will never set a non-empty SOAPAction, if you have not called
options.setAction(youraction).

Are u sure you have not called that method.

-- Chinthaka

nancy wrote:
 Yah I understand that marking message with Urgent won't help in getting
 quick reply from others.Anyways,I want to send a SOAP Envelope in the way
 that I don't need to manipulate the requested parameter (OMELEMENT) there
to
 get the parameters.
 
 I tried it but with no success. Exception is coming:
 
 Cannot find binding operation definition of soapAction '/orabpel' in
 http://daff06:9700/orabpel/default/ProcessManager/1.0/ProcessManager.wsdl
 
 My Request was:
 
 
 My request was: 
 
 ?xml version='1.0' encoding='UTF-8'?
 
 soapenv:Envelope
 xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header
/
 
 soapenv:Body
 
 Process:initiateProcess

xmlns:Process=http://services.oracle.com/bpel/Process;Process:primaryKeyV

alue1/Process:primaryKeyValueProcess:businessProcessId1/Process:busine
 ssProcessId/Process:initiateProcess/soapenv:Body/soapenv:Envelope
 
 
 And my ProcessManager.wsdl has no defined SOAP BINDINGS.
 
 Is it necessary to define soap bindings with wsdl.
 Why axis2 is taking /orabpel as soapaction?
 
 Thanks
 Nancy
 
 -Original Message-
 From: Eran Chinthaka [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, May 10, 2006 1:11 PM
 To: axis-user@ws.apache.org
 Subject: Re: URGENT Use axis2 to call bpel
 
 Hi Nancy,
 
 First, marking your messages to this list as URGENT won't help you in
 any means. Rather it will make the case worse. Opensource developers are
 willing and like to help others, but can not be forced to do so (except
 you have a private service contract with them ;) ).
 
 
 nancy wrote:
 Can anyone tell how to use axis 2 to call bpel process. Earlier I was
 using java classes generated by wsdl2java tool of axis1.But now; I don't
 want to use java classes. I want to just mention web service URL,
 message name and parameters.For eg:

 
 ..
 
 
 But using this I need to write code to get result out of OMElement. Or
 you can say I want to know how bpel process can understand the output or
 input of axis2? I am using ORACLE BPEL.

 
 Sorry I can not understand this problem. Do you wanna send a SOAPEnvelop
 e and get back only the Body first child ? If you can explain a bit more
 I might be able to help you.
 
 BTW, Axis2 or any web service engine do not care whether you talk to a
 BPEL server or

axis2: using jndi datasource/hibernate

2006-05-10 Thread Jilles van Gurp


Hi,

I'm currently exploring axis2. I am developing a web service that includes a 
few pojos that persist to a hibernate datalayer. Currently I am using the 
tomcat db connection pool and I was wondering at what is the recommended 
practice for configuring all this as a nice aar.


What I would prefer not to do is make any modifications to the axis2 web 
application. However, currently I see no other way of doing this:
- I need to enable the hibernate listener somewhere, the axis2 web.xml seems 
the only place to do that.
- I need to provide a context.xml with the jndi datasource: the axis2 
META-INF directory seems the place to put it.
- hibernate libraries need to be available for the service container so I 
need to add libraries to the WEB-INF/lib directory.
- the mysql jdbc driver needs to be available to tomcat, common/lib is the 
place to put it


In other words I am putting files all over the place to achieve an extremely 
simple use case (simple database connectivity).


Is there an alternative to this or do I need to break encapsulation here and 
modify the container to deploy my web service? In practice this is what I do 
for axis1: all my services come with a customized service container based on 
the axis1 web application. Effectively my unit of deployment is a war file. 
I see myself ending up doing exactly the same for axis2 now even though the 
intention of the whole aar thing seems to be not to do that.


_
Talk with your online friends with MSN Messenger http://messenger.msn.nl/

cannot find binding operation definition of soapAction '/orabpel' -Urgent











Hi,



I am trying to call BPEL process using Axis2.



I have given it the web service port address: http://daff06:9700/orabpel/default/ProcessManager/1.0
which is given in class generated by wsdl2java .



My request is:



?xml
version='1.0' encoding='UTF-8'?

soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/soapenv:Header
/

soapenv:Body

Process:initiateProcess
xmlns:Process=http://services.oracle.com/bpel/ProcessProcess:primaryKeyValue1/Process:primaryKeyValueProcess:businessProcessId1/Process:businessProcessId/Process:initiateProcess/soapenv:Body/soapenv:Envelope





Can any body tell from where it is assuming
soapAction:/oraBPEL?





following error is coming:



2006-05-10 12:41:16,031 DEBUG
default.collaxa.cube.ws CXSOAPProvider::processBPELMessage soapAction: /orabpel



2006-05-10 12:41:16,031 DEBUG
default.collaxa.cube.engine.deployment
CubeProcessHolder::loadAndBind Check if process Pro

revision 1.0 needs to be reloaded

2006-05-10 12:41:16,062 DEBUG
default.collaxa.cube.ws CXSOAPProvider::invoke Error when
process incoming message

AxisFault

faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException

faultSubcode:

faultString: Cannot find binding operation definition
of soapAction '/orabpel' in http://daff06:9700/orabpel/default/ProcessMan

ocessManager.wsdl

faultActor:

faultNode:

faultDetail:


{http://xml.apache.org/axis/}stackTrace:Cannot find binding operation
definition of soapAction '/orabpel' in http://daff

pel/default/ProcessManager/1.0/_ProcessManager.wsdl

 at com.collaxa.cube.ws.soap.providers.CXSOAPProvider.getBindingOperation(CXSOAPProvider.java:726)

 at
com.collaxa.cube.ws.soap.providers.CXSOAPProvider.processBPELMessage(CXSOAPProvider.java:217)

 at
com.collaxa.cube.ws.soap.providers.CXSOAPProvider.invoke(CXSOAPProvider.java:119)

 at
org.collaxa.thirdparty.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)

 at
org.collaxa.thirdparty.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)

 at org.collaxa.thirdparty.apache.axis.SimpleChain.invoke(SimpleChain.java:83)

 at
org.collaxa.thirdparty.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:450)

 at
org.collaxa.thirdparty.apache.axis.server.AxisServer.invoke(AxisServer.java:285)

 at
org.collaxa.thirdparty.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:653)

 at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

 at
org.collaxa.thirdparty.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:301)

 at
com.collaxa.cube.fe.CollaxaServlet.service(CollaxaServlet.java:134)

 at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

 at
com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810)

 at
com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)

 at
com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)

 at
com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)

 at
com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)

 at
com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)

 at
java.lang.Thread.run(Thread.java:534)




{http://xml.apache.org/axis/}hostname:daff06

Re: Enable soap monitor

See me responses inline. On 5/10/06, [EMAIL PROTECTED] 
[EMAIL PROTECTED] wrote:













Hi,

 Not able to understand this point 

3) Deploy the soapmonitor web service via the admin client

The soap monitor in axis 1.x also has a wsdd - which IIRC needs to be deployed first. 


And

"assuming a axis.war"



This requires axis to be deployed along with my web application ?
Nope - you can use myApp.war just fine. 

Is this url http://localhost:8080/axis/services/AdminService
to be converted to http://localhost:8080/mywebcontext/myservices/myservice
?

Yes. 

HTH,
Robert
http://www.braziloutsource.com/

Sorry. Haven't worked with axis before ?





Thanks,

Mohan











From: robert lazarski
[mailto:[EMAIL PROTECTED]] 
Sent: Tuesday, May 09, 2006 5:54
PM
To: axis-user@ws.apache.org
Subject: Re: Enable soap monitor





The steps in axis 1.x,
assuming a axis.war, are:

1) Compile the applet and put it under axis/*applet.class*/WEB-INF
2) Configure the soapmonitor servlet via web.xml
3) Deploy the soapmonitor web service via the admin client
4) Place references in your web service wsdd such as: 

 requestFlow
 handler type=soapmonitor/
 /requestFlow
 responseFlow
 handler type=soapmonitor/
 /responseFlow

5) Load the soap applet in a java 1.3 and higher enabled browser via: 

http://localhost:8080/axis/SOAPMonitor

HTH,
Robert
http://www.braziloutsource.com/



On 5/9/06, 
[EMAIL PROTECTED]

[EMAIL PROTECTED] wrote:





Hi,


I am trying to enable the soap monitor for my liferay portal application. The
first step is to

install
axis along with this web application. Is that correct ?



What
does the url in the following axis instruction mean ? I have to substitute
axis with my web

application
context ?? What does this services/AdminService mean ? What do I
substitute it with ?





Deploy
the SOAPMonitorService web service with the admin client and the
deploy-monitor.wsdd file 



java
-cp %AXISCLASSPATH% org.apache.axis.client.AdminClient
-lhttp://localhost:8080/axis/services/AdminService

deploy-monitor.wsdd



I
am trying to monitor my WSRP communication.



Thanks,

Mohan





This
message is for the designated recipient only and may contain privileged,
proprietary, or otherwise private information. If you have received it in
error, please notify the sender immediately and delete the original. Any other
use of the email by you is prohibited.











This
message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is prohibited.

Axis2 1.0 getOutputStream() has already been called for this response

Hi, 


I want to generate a web service from a wsdl file with WSDL2Java.
I'have tried adb data binding and jibx data binding.
I successfully deploy my web service in tomcat (5.5.17)
When I invoke the service, I'have an HTTP 500 server error 
java.lang.IllegalStateException: getOutputStream() has already been called for this 
response
whith both adb and jibx databinding.
The only code I have written is in generated skeleton and I only return the 
response object.

Is something has similar problem ?

thanks

RE: load: class SOAPMonitorApplet.class not found

2006-05-10 Thread Vignesh M.P.N.

Title: Message



Could 
anyone please help me on this?

Thanks
Vignesh.

  
  -Original Message-From: Vignesh M.P.N. 
  [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 9:34 
  PMTo: axis-user@ws.apache.orgSubject: RE: load: class 
  SOAPMonitorApplet.class not found
  I 
  uncommented and tried telnet and it is responding.
  
  Yes, 
  I already posted the error message in the console. 
  
  Exception! java.net.ConnectException: connect: Address is invalid on 
  local machine, or port is not valid on remote 
  machinejava.net.ConnectException: connect: Address is invalid on local 
  machine, or port is not valid on remote machineat 
  java.net.PlainSocketImpl.socketConnect(Native Method)at 
  java.net.PlainSocketImpl.doConnect(Unknown Source)at 
  java.net.PlainSocketImpl.connectToAddress(Unknown Source)at 
  java.net.PlainSocketImpl.connect(Unknown Source)at 
  java.net.SocksSocketImpl.connect(Unknown Source)at 
  java.net.Socket.connect(Unknown Source)at 
  java.net.Socket.connect(Unknown Source)at 
  java.net.Socket.init(Unknown Source)at 
  java.net.Socket.init(Unknown Source)at 
  SOAPMonitorApplet$SOAPMonitorPage.start(SOAPMonitorApplet.java:355)at 
  SOAPMonitorApplet$SOAPMonitorPage.actionPerformed(SOAPMonitorApplet.java:571)at 
  javax.swing.AbstractButton.fireActionPerformed(Unknown Source)at 
  javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)at 
  javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)at 
  javax.swing.DefaultButtonModel.setPressed(Unknown Source)at 
  javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown 
  Source)at java.awt.Component.processMouseEvent(Unknown 
  Source)at javax.swing.JComponent.processMouseEvent(Unknown 
  Source)at java.awt.Component.processEvent(Unknown 
  Source)at java.awt.Container.processEvent(Unknown 
  Source)at java.awt.Component.dispatchEventImpl(Unknown 
  Source)at java.awt.Container.dispatchEventImpl(Unknown 
  Source)at java.awt.Component.dispatchEvent(Unknown 
  Source)at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown 
  Source)at java.awt.LightweightDispatcher.processMouseEvent(Unknown 
  Source)at java.awt.LightweightDispatcher.dispatchEvent(Unknown 
  Source)at java.awt.Container.dispatchEventImpl(Unknown 
  Source)at java.awt.Component.dispatchEvent(Unknown 
  Source)at java.awt.EventQueue.dispatchEvent(Unknown 
  Source)at 
  java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown 
  Source)at 
  java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown 
  Source)at java.awt.EventDispatchThread.pumpEvents(Unknown 
  Source)at java.awt.EventDispatchThread.pumpEvents(Unknown 
  Source)at java.awt.EventDispatchThread.run(Unknown 
  Source)
  Thanks
  Vignesh.
  

-Original Message-From: robert 
lazarski [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 
2006 9:21 PMTo: axis-user@ws.apache.orgSubject: Re: 
load: class SOAPMonitorApplet.class not foundIn the the 
browser, open the java console I believe by right clicking, maybe under 
tools ... and see what the error is. Also, it may be worth trying to comment 
out the serlvet in web.xml , and see if the server is still listening on 
port 5001. 'nmap -p 5001' or 'telnet localhost 5001' should do the 
trick . Roberthttp://www.braziloutsource.com/
On 5/9/06, Vignesh 
M.P.N. [EMAIL PROTECTED]  
wrote: 

  
  Thanks, but it is already 
  there in the web.xml. The following is the entry.
  
  servlet 
  servlet-nameSOAPMonitorService/servlet-name 
  display-nameSOAPMonitorService/display-name 
  servlet-class
   
  org.apache.axis.monitor.SOAPMonitorService
   /servlet-class 
  init-param 
  param-nameSOAPMonitorPort/param-name 
  param-value5001/param-value 
  /init-param 
  load-on-startup100/load-on-startup 
  /servlet
  
  Thanks
  Vignesh.
  


-Original Message-From: robert lazarski 
[mailto:[EMAIL PROTECTED]] 

Sent: Tuesday, May 09, 2006 9:02 
PMTo: axis-user@ws.apache.orgSubject: Re: load: 
class SOAPMonitorApplet.class not found

  Meant to 
  say - add the soap monitor servlet by editing web.xmlRoberthttp://www.braziloutsource.com/
  On 5/9/06, Vignesh 
  M.P.N. [EMAIL PROTECTED]  
  wrote: 
  

Thanks for your prompt 
reply.

I fixed the problem. I 
had to place the class files in the root directory of Axis web 
application.

But now I am facing 
another problem. Now the applet got loaded but it says, "The SOAP 
Monitor is unable to communcate with the server". Again read thru the 
archive, but couldn't fix it.

The Java console says: 

Exception! java.net.ConnectException: 
connect: Address is invalid on local machine, or port is not

Re: axis2: using jndi datasource/hibernate

I use most of these libs with axis2 - except I use spring for the
datasource. The way I do it is I only put the ServiceClass - referenced
in service.xml - inside the aar. In this case, the aar uses a seperate
classloader only for this case.

An aar provides good isolation and versioning for multiple services,
and for those not using hibernate, spring etc, there is an advantage.
The deployment and structure of an aar is IMHO simple that axis 1.x and
in my experience its easier to explain. But I'd just stick with a plain
old WEB-INF configuration when using libs that depend on the TCCL.

HTH,
Robert
http://www.braziloutsource.com/
On 5/10/06, Jilles van Gurp [EMAIL PROTECTED] wrote:
Hi,I'm currently exploring axis2. I am developing a web service that includes afew pojos that persist to a hibernate datalayer. Currently I am using thetomcat db connection pool and I was wondering at what is the recommended
practice for configuring all this as a nice aar.What I would prefer not to do is make any modifications to the axis2 webapplication. However, currently I see no other way of doing this:- I need to enable the hibernate listener somewhere, the axis2
web.xml seemsthe only place to do that.- I need to provide a context.xml with the jndi datasource: the axis2META-INF directory seems the place to put it.- hibernate libraries need to be available for the service container so I
need to add libraries to the WEB-INF/lib directory.- the mysql jdbc driver needs to be available to tomcat, common/lib is theplace to put itIn other words I am putting files all over the place to achieve an extremely
simple use case (simple database connectivity).Is there an alternative to this or do I need to break encapsulation here andmodify the container to deploy my web service? In practice this is what I dofor axis1: all my services come with a customized service container based on
the axis1 web application. Effectively my unit of deployment is a war file.I see myself ending up doing exactly the same for axis2 now even though theintention of the whole aar thing seems to be not to do that.
_Talk with your online friends with MSN Messenger http://messenger.msn.nl/

Re: Use axis2 to call bpel

What is the SOAPAction URI specified in the WSDL for initiateProcess operation? You should specify that URI in setAction method.AnneOn 5/10/06, 
nancy [EMAIL PROTECTED] wrote:
Hi,I have not used that method. My code is:Public void invoke(){Options options = new Options();options.setTransportInProtocol(Constants.TRANSPORT_HTTP);boolean exit = false;
String serviceGroupContextId = null;EndpointReference EPR=new EndpointReference(webserviceURL);options.setTo(EPR);options.setTimeOutInMilliSeconds
(5);ServiceClient serviceClient;serviceClient = new ServiceClient();serviceClient.setOptions(options);MessageContext requestMessageContext = new MessageContext();
requestMessageContext.setEnvelope(getRequestEnvelope(messageName,parametersList,serviceGroupContextId));OperationClient opClient = serviceClient.createClient(
ServiceClient.ANON_OUT_IN_OP);opClient.addMessageContext(requestMessageContext);opClient.setOptions(options);opClient.execute(true);}private SOAPEnvelope getRequestEnvelope(String operationName,
HashMap param, String groupContextId) {String namespace1=http://services.oracle.com/bpel/Process;SOAPFactory fac = 
OMAbstractFactory.getSOAP11Factory();SOAPEnvelope envelope = fac.getDefaultEnvelope();OMNamespace namespace = fac.createOMNamespace(namespace1, Process);
OMElement params1 = fac.createOMElement(operationName,namespace);Set set=param.keySet();Iterator iter=set.iterator();while(iter.hasNext
()){String paramName=iter.next().toString();String paramValue=param.get(paramName).toString(); OMElement paramOM =fac.createOMElement
(paramName,namespace); paramOM.setText(paramValue); params1.addChild(paramOM);}envelope.getBody().setFirstChild(params1);
return envelope;}ThanksNancy-Original Message-From: Eran Chinthaka [mailto:[EMAIL PROTECTED]]Sent: Wednesday, May 10, 2006 2:34 PM
To: axis-user@ws.apache.orgSubject: Re: Use axis2 to call bpelAxis2 will never set a non-empty SOAPAction, if you have not calledoptions.setAction(youraction).
Are u sure you have not called that method.-- Chinthakanancy wrote: Yah I understand that marking message with Urgent won't help in getting quick reply from others.Anyways,I want to send a SOAP Envelope in the way
 that I don't need to manipulate the requested parameter (OMELEMENT) thereto get the parameters. I tried it but with no success. Exception is coming: Cannot find binding operation definition of soapAction '/orabpel' in
 http://daff06:9700/orabpel/default/ProcessManager/1.0/ProcessManager.wsdl My Request was:
 My request was: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/
soapenv:Header/ soapenv:Body Process:initiateProcessxmlns:Process=http://services.oracle.com/bpel/Process
Process:primaryKeyValue1/Process:primaryKeyValueProcess:businessProcessId1/Process:busine ssProcessId/Process:initiateProcess/soapenv:Body/soapenv:Envelope
 And my ProcessManager.wsdl has no defined SOAP BINDINGS. Is it necessary to define soap bindings with wsdl. Why axis2 is taking /orabpel as soapaction? Thanks
 Nancy -Original Message- From: Eran Chinthaka [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 10, 2006 1:11 PM To: 
axis-user@ws.apache.org Subject: Re: URGENT Use axis2 to call bpel Hi Nancy, First, marking your messages to this list as URGENT won't help you in
 any means. Rather it will make the case worse. Opensource developers are willing and like to help others, but can not be forced to do so (except you have a private service contract with them ;) ).
 nancy wrote: Can anyone tell how to use axis 2 to call bpel process. Earlier I was using java classes generated by wsdl2java tool of axis1.But now; I don't want to use java classes. I want to just mention web service URL,
 message name and parameters.For eg: .. But using this I need to write code to get result out of OMElement. Or you can say I want to know how bpel process can understand the output or
 input of axis2? I am using ORACLE BPEL. Sorry I can not understand this problem. Do you wanna send a SOAPEnvelop e and get back only the Body first child ? If you can explain a bit more
 I might be able to help you. BTW, Axis2 or any web service engine do not care whether you talk to a BPEL server or not. It sends out and receive SOAP messages, that's all. -- Chinthaka
 Thanks

Re: Axis2 1.0 getOutputStream() has already been called for this response


This is stack  trace
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265)
   
org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75)
   
org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222)
   
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76)
   
org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183)
   
org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168)

   org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

Arnaud MERGEY a écrit :

Hi,
I want to generate a web service from a wsdl file with WSDL2Java.
I'have tried adb data binding and jibx data binding.
I successfully deploy my web service in tomcat (5.5.17)
When I invoke the service, I'have an HTTP 500 server error 
java.lang.IllegalStateException: getOutputStream() has already been 
called for this response

whith both adb and jibx databinding.
The only code I have written is in generated skeleton and I only 
return the response object.


Is something has similar problem ?

thanks

Re: load: class SOAPMonitorApplet.class not found

Looks like an OS config issue to me: 

Address is invalid on 
  local machine, or port is not valid on remote 
  machine

Shutdown tomcat. If you can still telnet to port 5001, something else
is listening, and the applet will be passed zero as the port to
connect. My guess is that for some reason, the SOAPMonitorService can't
connect to 5001, and your seeing the applet trying to connect to port
zero - the default. 

BTW - axis2 has improved the logging here and your problem would be easy to track down. 

HTH,
Robert
http://www.braziloutsource.com/
On 5/10/06, Vignesh M.P.N. [EMAIL PROTECTED] wrote:







Could 
anyone please help me on this?

Thanks
Vignesh.

  
  -Original Message-From: Vignesh M.P.N. 
  [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 09, 2006 9:34 
  PMTo: axis-user@ws.apache.org
Subject: RE: load: class 
  SOAPMonitorApplet.class not found
  I 
  uncommented and tried telnet and it is responding.
  
  Yes, 
  I already posted the error message in the console. 
  
  Exception! java.net.ConnectException: connect: Address is invalid on 
  local machine, or port is not valid on remote 
  machinejava.net.ConnectException: connect: Address is invalid on local 
  machine, or port is not valid on remote machineat 
  java.net.PlainSocketImpl.socketConnect(Native Method)at 
  java.net.PlainSocketImpl.doConnect(Unknown Source)at 
  java.net.PlainSocketImpl.connectToAddress(Unknown Source)at 
  java.net.PlainSocketImpl.connect(Unknown Source)at 
  java.net.SocksSocketImpl.connect(Unknown Source)at 
  java.net.Socket.connect(Unknown Source)at 
  java.net.Socket.connect(Unknown Source)at 
  java.net.Socket.init(Unknown Source)at 
  java.net.Socket.init(Unknown Source)at 
  SOAPMonitorApplet$SOAPMonitorPage.start(SOAPMonitorApplet.java:355)at 
  SOAPMonitorApplet$SOAPMonitorPage.actionPerformed(SOAPMonitorApplet.java:571)at 
  javax.swing.AbstractButton.fireActionPerformed(Unknown Source)at 
  javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)at 
  javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)at 
  javax.swing.DefaultButtonModel.setPressed(Unknown Source)at 
  javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown 
  Source)at java.awt.Component.processMouseEvent(Unknown 
  Source)at javax.swing.JComponent.processMouseEvent(Unknown 
  Source)at java.awt.Component.processEvent(Unknown 
  Source)at java.awt.Container.processEvent(Unknown 
  Source)at java.awt.Component.dispatchEventImpl(Unknown 
  Source)at java.awt.Container.dispatchEventImpl(Unknown 
  Source)at java.awt.Component.dispatchEvent(Unknown 
  Source)at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown 
  Source)at java.awt.LightweightDispatcher.processMouseEvent(Unknown 
  Source)at java.awt.LightweightDispatcher.dispatchEvent(Unknown 
  Source)at java.awt.Container.dispatchEventImpl(Unknown 
  Source)at java.awt.Component.dispatchEvent(Unknown 
  Source)at java.awt.EventQueue.dispatchEvent(Unknown 
  Source)at 
  java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown 
  Source)at 
  java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown 
  Source)at java.awt.EventDispatchThread.pumpEvents(Unknown 
  Source)at java.awt.EventDispatchThread.pumpEvents(Unknown 
  Source)at java.awt.EventDispatchThread.run(Unknown 
  Source)
  Thanks
  Vignesh.
  

-Original Message-From: robert 
lazarski [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 09, 
2006 9:21 PMTo: axis-user@ws.apache.orgSubject: Re: 
load: class SOAPMonitorApplet.class not foundIn the the 
browser, open the java console I believe by right clicking, maybe under 
tools ... and see what the error is. Also, it may be worth trying to comment 
out the serlvet in web.xml , and see if the server is still listening on 
port 5001. 'nmap -p 5001' or 'telnet localhost 5001' should do the 
trick . Roberthttp://www.braziloutsource.com/
On 5/9/06, Vignesh 
M.P.N. [EMAIL PROTECTED]  
wrote: 

  
  Thanks, but it is already 
  there in the web.xml. The following is the entry.
  
  servlet 
  servlet-nameSOAPMonitorService/servlet-name 
  display-nameSOAPMonitorService/display-name 
  servlet-class
   
  org.apache.axis.monitor.SOAPMonitorService
   /servlet-class 
  init-param 
  param-nameSOAPMonitorPort/param-name 
  param-value5001/param-value 
  /init-param 
  load-on-startup100/load-on-startup 
  /servlet
  
  Thanks
  Vignesh.
  


-Original Message-From: robert lazarski 
[mailto:[EMAIL PROTECTED]] 

Sent: Tuesday, May 09, 2006 9:02 
PMTo: axis-user@ws.apache.orgSubject: Re: load: 
class SOAPMonitorApplet.class not found

  Meant to 
  say - add the soap monitor servlet by editing web.xmlRoberthttp://www.braziloutsource.com/

  On 5/9/06, Vignesh 
  M.P.N. [EMAIL PROTECTED]

Re: Axis2 1.0 getOutputStream() has already been called for this response

2006-05-10 Thread Ali Sadik Kumlali

Hi Arnaud,

Do you, by any chance, use a program such as TCPMon or Eclipse WTP's
TCP/IP monitor? If you do, could you try without it?Last week I faced
with the same problem and it disappeared when I stopped using Eclipse
WTP's TCP/IP monitor.

If your problem is solved with this way, but you really need to see the
message flow, you may use a sniffer program.

Hope this helps.

Ali Sadik Kumlali

--- Arnaud MERGEY [EMAIL PROTECTED] wrote:

 This is stack  trace

org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265)
 

org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75)
 

org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222)
 

org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76)
 

org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183)
 

org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168)


org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 
 Arnaud MERGEY a ï¿½crit :
  Hi,
  I want to generate a web service from a wsdl file with WSDL2Java.
  I'have tried adb data binding and jibx data binding.
  I successfully deploy my web service in tomcat (5.5.17)
  When I invoke the service, I'have an HTTP 500 server error 
  java.lang.IllegalStateException: getOutputStream() has already
 been 
  called for this response
  whith both adb and jibx databinding.
  The only code I have written is in generated skeleton and I only 
  return the response object.
 
  Is something has similar problem ?
 
  thanks
 
 
 
 
 
 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Re: Use axis2 to call bpel

2006-05-10 Thread Anamitra . Bhattacharyya

with the limited experience that I have with oracle bpel engine - if you do
not provide a soapaction the oracle bpel engine which is hosting your
process web service will default the soapaction to orabpel and will try
to find that binding - which obviously does not exist. You have to look at
ur oracle generated process wsdl and see what the soapction for ur web
service call is and then explicitly set that soapaction from your client.

HTH
Anamitra


   
 Eran Chinthaka
 [EMAIL PROTECTED] 
 urce.lk   To 
   axis-user@ws.apache.org 
 05/10/2006 05:03   cc 
 AM
   Subject 
   Re: Use axis2 to call bpel  
 Please respond to 
 [EMAIL PROTECTED] 
  he.org   
   
   
   




Axis2 will never set a non-empty SOAPAction, if you have not called
options.setAction(youraction).

Are u sure you have not called that method.

-- Chinthaka

nancy wrote:
 Yah I understand that marking message with Urgent won't help in getting
 quick reply from others.Anyways,I want to send a SOAP Envelope in the way
 that I don't need to manipulate the requested parameter (OMELEMENT) there
to
 get the parameters.

 I tried it but with no success. Exception is coming:

 Cannot find binding operation definition of soapAction '/orabpel' in
 http://daff06:9700/orabpel/default/ProcessManager/1.0/ProcessManager.wsdl

 My Request was:


 My request was:

 ?xml version='1.0' encoding='UTF-8'?

 soapenv:Envelope
 xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header
/

 soapenv:Body

 Process:initiateProcess
 xmlns:Process=http://services.oracle.com/bpel/Process
Process:primaryKeyV

alue1/Process:primaryKeyValueProcess:businessProcessId1/Process:busine

 ssProcessId/Process:initiateProcess/soapenv:Body/soapenv:Envelope


 And my ProcessManager.wsdl has no defined SOAP BINDINGS.

 Is it necessary to define soap bindings with wsdl.
 Why axis2 is taking /orabpel as soapaction?

 Thanks
 Nancy

 -Original Message-
 From: Eran Chinthaka [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, May 10, 2006 1:11 PM
 To: axis-user@ws.apache.org
 Subject: Re: URGENT Use axis2 to call bpel

 Hi Nancy,

 First, marking your messages to this list as URGENT won't help you in
 any means. Rather it will make the case worse. Opensource developers are
 willing and like to help others, but can not be forced to do so (except
 you have a private service contract with them ;) ).


 nancy wrote:
 Can anyone tell how to use axis 2 to call bpel process. Earlier I was
 using java classes generated by wsdl2java tool of axis1.But now; I don't
 want to use java classes. I want to just mention web service URL,
 message name and parameters.For eg:


 ..


 But using this I need to write code to get result out of OMElement. Or
 you can say I want to know how bpel process can understand the output or
 input of axis2? I am using ORACLE BPEL.


 Sorry I can not understand this problem. Do you wanna send a SOAPEnvelop
 e and get back only the Body first child ? If you can explain a bit more
 I might be able to help you.

 BTW, Axis2 or any web service engine do not care whether you talk to a
 BPEL server or not. It sends out and receive SOAP messages, that's all.

 -- Chinthaka



 Thanks







(See attached file: signature.asc)

signature.asc
Description: Binary data

Re: WSE 817 error - bad wsdl or just newbie stupidity?

So you should tell the folks that built the service that they should define a more reasonable Actor attribute. To make it easier for consumers, the Actor attribute should be the same as the service endpoint URL. The wsa:To value specifies the destination property, which is a URI that represents the Actor to whom the request is targeted -- not the physical location of the service. (The physical location may change, after all.)
Based on your error message, you should specify the destination property as urn:AWordICannotFindAnywhereInMyCode.AnneOn 5/9/06, 
James Gough [EMAIL PROTECTED] wrote:
I am very new to Axis and web services in general.I am writing aclient for a .NET-based web service using the Axis WSDL2Java generatorto create my client.Once I compiled the resulting code and set up atest program for a very small part of the client, I ran it and got this:
Destination Unreachable -- WSE817: The lt;Togt; header must match theActor attribute on this receiver. The lt;Togt; header containedquot;https://ws.somedomain.com/webservices/engine.asmxquot; whereas
the Actor attribute was quot;urn:AWordICannotFindAnywhereInMyCodequot;.So I looked into the wsdl file and the location attribute of the soaptag is 
https://ws.somedomain.com/webservices/engine.asmx, but thesoapAction attribute of the operation I want to use ishttp://somedomain.com/MinorAction.Like I said, I am new to this, and
I have access to the guys who set up this wsdl, but prefer to have abetter Idea of what my problem is before I ask for help from them.Ishould add that they have a .NET client for this that does work (myapplication is in Java so I'd prefer to use Axis).
Anybody?

Re: Axis2 1.0 getOutputStream() has already been called for this response


Hi,
I didn't use any program TCP monitor.
I use tomcat starded with the startup.bat batch and invoke my web 
service with SOAP UI


thanks,
Arnaud


Ali Sadik Kumlali a écrit :

Hi Arnaud,

Do you, by any chance, use a program such as TCPMon or Eclipse WTP's
TCP/IP monitor? If you do, could you try without it?Last week I faced
with the same problem and it disappeared when I stopped using Eclipse
WTP's TCP/IP monitor.

If your problem is solved with this way, but you really need to see the
message flow, you may use a sniffer program.

Hope this helps.

Ali Sadik Kumlali

--- Arnaud MERGEY [EMAIL PROTECTED] wrote:

  

This is stack  trace



org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265)
  




org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75)
  




org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222)
  




org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76)
  




org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183)
  




org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168)
  
   



org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)
  

javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

Arnaud MERGEY a ï¿½crit :


Hi,
I want to generate a web service from a wsdl file with WSDL2Java.
I'have tried adb data binding and jibx data binding.
I successfully deploy my web service in tomcat (5.5.17)
When I invoke the service, I'have an HTTP 500 server error 
java.lang.IllegalStateException: getOutputStream() has already
  
been 


called for this response
whith both adb and jibx databinding.
The only code I have written is in generated skeleton and I only 
return the response object.


Is something has similar problem ?

thanks




  




__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Re: Axis2 1.0 getOutputStream() has already been called for this response


In tomcat logs I have:

GRAVE: Exception Processing ErrorPage[errorCode=500, 
location=/axis2-web/Error/error500.jsp]
org.apache.jasper.JasperException: getOutputStream() a déjà été appelé 
pour cette réponse
   at 
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
   at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
   at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)

   at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
   at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
   at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
   at 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:465)
   at 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
   at 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
   at 
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:363)
   at 
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284)
   at 
org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:228)
   at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:134)
   at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
   at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
   at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
   at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
   at 
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
   at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
   at 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
   at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)

   at java.lang.Thread.run(Thread.java:595)

Davanum Srinivas a écrit :

Can you please check the tomcat logs?

thanks,
dims

On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:

This is stack  trace
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265) 



org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75) 



org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222) 



org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76) 



org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183) 



org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168) 


org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)

javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

Arnaud MERGEY a écrit :
 Hi,
 I want to generate a web service from a wsdl file with WSDL2Java.
 I'have tried adb data binding and jibx data binding.
 I successfully deploy my web service in tomcat (5.5.17)
 When I invoke the service, I'have an HTTP 500 server error
 java.lang.IllegalStateException: getOutputStream() has already been
 called for this response
 whith both adb and jibx databinding.
 The only code I have written is in generated skeleton and I only
 return the response object.

 Is something has similar problem ?

 thanks









--
Davanum Srinivas : http://wso2.com/blogs/

Re: Axis2 1.0 getOutputStream() has already been called for this response


Hmm...i think i can guess where the problem is. could u please try
adding an empty soap header in the soapui (when u send the request
message?)

thanks,
dims

On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:

In tomcat logs I have:

GRAVE: Exception Processing ErrorPage[errorCode=500,
location=/axis2-web/Error/error500.jsp]
org.apache.jasper.JasperException: getOutputStream() a déjà été appelé
pour cette réponse
at
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:465)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
at
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:363)
at
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284)
at
org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:228)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:134)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)

Davanum Srinivas a écrit :
 Can you please check the tomcat logs?

 thanks,
 dims

 On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:
 This is stack  trace
 
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265)


 
org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75)


 
org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222)


 
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76)


 
org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183)


 org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168)


 org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

 Arnaud MERGEY a écrit :
  Hi,
  I want to generate a web service from a wsdl file with WSDL2Java.
  I'have tried adb data binding and jibx data binding.
  I successfully deploy my web service in tomcat (5.5.17)
  When I invoke the service, I'have an HTTP 500 server error
  java.lang.IllegalStateException: getOutputStream() has already been
  called for this response
  whith both adb and jibx databinding.
  The only code I have written is in generated skeleton and I only
  return the response object.
 
  Is something has similar problem ?
 
  thanks
 
 
 
 




 --
 Davanum Srinivas : http://wso2.com/blogs/






--
Davanum Srinivas : http://wso2.com/blogs/

Re: Axis2 1.0 getOutputStream() has already been called for this response


With empty soap header, invocation works !

Arnaud

Davanum Srinivas a écrit :

Hmm...i think i can guess where the problem is. could u please try
adding an empty soap header in the soapui (when u send the request
message?)

thanks,
dims

On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:

In tomcat logs I have:

GRAVE: Exception Processing ErrorPage[errorCode=500,
location=/axis2-web/Error/error500.jsp]
org.apache.jasper.JasperException: getOutputStream() a déjà été appelé
pour cette réponse
at
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510) 


at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387) 


at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) 


at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) 


at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) 


at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:465) 


at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398) 


at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) 


at
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:363) 


at
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284) 


at
org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:228) 


at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:134) 


at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) 


at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) 


at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) 


at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) 


at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) 


at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) 


at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) 


at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) 


at java.lang.Thread.run(Thread.java:595)

Davanum Srinivas a écrit :
 Can you please check the tomcat logs?

 thanks,
 dims

 On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:
 This is stack  trace
 
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265) 




 
org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75) 




 
org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222) 




 
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76) 




 
org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183) 




 
org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168) 




 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)

 javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

 Arnaud MERGEY a écrit :
  Hi,
  I want to generate a web service from a wsdl file with WSDL2Java.
  I'have tried adb data binding and jibx data binding.
  I successfully deploy my web service in tomcat (5.5.17)
  When I invoke the service, I'have an HTTP 500 server error
  java.lang.IllegalStateException: getOutputStream() has already 
been

  called for this response
  whith both adb and jibx databinding.
  The only code I have written is in generated skeleton and I only
  return the response object.
 
  Is something has similar problem ?
 
  thanks
 
 
 
 




 --
 Davanum Srinivas : http://wso2.com/blogs/






--
Davanum Srinivas : http://wso2.com/blogs/

Re: Axis2 1.0 getOutputStream() has already been called for this response


Ah...let me see how to fix it.

thanks,
dims

On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:

With empty soap header, invocation works !

Arnaud

Davanum Srinivas a écrit :
 Hmm...i think i can guess where the problem is. could u please try
 adding an empty soap header in the soapui (when u send the request
 message?)

 thanks,
 dims

 On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:
 In tomcat logs I have:

 GRAVE: Exception Processing ErrorPage[errorCode=500,
 location=/axis2-web/Error/error500.jsp]
 org.apache.jasper.JasperException: getOutputStream() a déjà été appelé
 pour cette réponse
 at
 
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)

 at
 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)

 at
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
 at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 at
 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)

 at
 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)

 at
 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)

 at
 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:465)

 at
 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)

 at
 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)

 at
 org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:363)

 at
 org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284)

 at
 
org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:228)

 at
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:134)

 at
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)

 at
 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)

 at
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)

 at
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)

 at
 
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)

 at
 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)

 at
 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)

 at
 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)

 at java.lang.Thread.run(Thread.java:595)

 Davanum Srinivas a écrit :
  Can you please check the tomcat logs?
 
  thanks,
  dims
 
  On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:
  This is stack  trace
 
 
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265)

 
 
 
 
org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75)

 
 
 
 
org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222)

 
 
 
 
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76)

 
 
 
 
org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183)

 
 
 
 org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168)

 
 
 
 org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)
  javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
  javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 
  Arnaud MERGEY a écrit :
   Hi,
   I want to generate a web service from a wsdl file with WSDL2Java.
   I'have tried adb data binding and jibx data binding.
   I successfully deploy my web service in tomcat (5.5.17)
   When I invoke the service, I'have an HTTP 500 server error
   java.lang.IllegalStateException: getOutputStream() has already
 been
   called for this response
   whith both adb and jibx databinding.
   The only code I have written is in generated skeleton and I only
   return the response object.
  
   Is something has similar problem ?
  
   thanks
  
  
  
  
 
 
 
 
  --
  Davanum Srinivas : http://wso2.com/blogs/
 




 --
 Davanum Srinivas : http://wso2.com/blogs/






--
Davanum Srinivas : http://wso2.com/blogs/

Re: [axis2]axis2 + mtom

2006-05-10 Thread Stefan Vladov

  Hi,

sorry to bother you again with the same old stuff... my problem was the
javamail implementation... an exception of type ParseException is thrown
somewhere in
javax.mail.internet.ContentType#ContentType(String type)
, which is called by
public Attachments(InputStream inStream, String contentTypeString,
   boolean fileCacheEnable, String attachmentRepoDir,
   String fileThreshold)
in org.apache.axiom.attachments.Attachments,
called from TransportUtils and so on...
I wasn't able to debug javamail further to see the exact cause.
Anyway my question is: is MTOM in axis2 meant to work only with geronimo
mail implementation and if you are familiar with the issue, have you
come up with some workaround.
As I am totally unfamiliar with the differences between geronimo's and
sun's implementations I thought the problem might be in the registered
handlers in the mailcap-s of the jars, however now I saw that the code is
different althogh packages, classes and methods are the same :( .
geronimo source is looks like that:

public ContentType(String type)
throws ParseException
{
int slash = type.indexOf(/);
int semi = type.indexOf(;);

try
{
_major = type.substring(0, slash);
if(semi == -1)
{
_minor = type.substring(slash + 1);
} else
{
_minor = type.substring(slash + 1, semi);
_list = new ParameterList(type.substring(semi + 1));
}
}
catch(StringIndexOutOfBoundsException e)
{
throw new ParseException(Type invalid:  + type);
}
}
,whereas sun's javamail 1.4 as well as 1.3.1 are:

public ContentType(String s)
throws ParseException
{
HeaderTokenizer headertokenizer = new HeaderTokenizer(s,
()@,;:t []/?=);
HeaderTokenizer.Token token = headertokenizer.next();
if(token.getType() != -1)
throw new ParseException();
primaryType = token.getValue();
token = headertokenizer.next();
if((char)token.getType() != '/')
throw new ParseException();
token = headertokenizer.next();
if(token.getType() != -1)
throw new ParseException();
subType = token.getValue();
String s1 = headertokenizer.getRemainder();
if(s1 != null)
list = new ParameterList(s1);
}
Anyway I am serving the web services on Jetty embedded in an application
(which actually provides the services ) and I somehow don't want to switch
to geronimo's implementation, so please if somebody has been through this
HEEELP!


 I have fixed the SOAP version issue+  a potential content type issue
 recently.
 Are you using Sun's impl of Java Mail?

 Please try with the latest svn heads.. Even the latest Axis2 RC + Axiom
 RC would be fine..

 ~Thilina


 On 5/2/06, Stefan Vladov [EMAIL PROTECTED] wrote:

 Hi guys,

 This is probably a very stupid problem, however since I consider myself
 a
 newbie and I've been using web services for about 2-3 weeks the issue
 has
 turned out to be quite a bottleneck for me. So here is my problem: I was
 trying to make the following scenario with apache axis2 0.95 - a client
 requests a file from by providing a name and a web service sends it (the
 file) as a binary attachment. However since things did not work I tried
 rewriting the sample and I still have the same problem. My version that
 is
 quite similar to the original looks like that:

 public class MTOMClient
 {
private static EndpointReference targetEPR = new
 EndpointReference(http://localhost:8011/services/WSMTOMTest;);
private static imageFileName = some image name;

public static void main (String[] args)
{
try
{
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs = fac.createOMNamespace(http://blabla;,
 bla);
OMElement method = fac.createOMElement(handle, omNs);
Image image;
image = new ImageIO().loadImage(new
 FileInputStream(imagefilename));
ImageDataSource dataSource = new
 ImageDataSource(calendar.jpg,image);
DataHandler dataHandler = new DataHandler(dataSource);
OMText textData = fac.createText(dataHandler, true);
OMElement imageElement = fac.createOMElement(imageElement,
 omNs);
imageElement.addChild(textData);
method.addChild(imageElement);

Options options = new Options();
options.setTo(targetEPR);
options.setSoapVersionURI(
 SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);

AXIS Serialization / Deserialization problem with namespace prefixes

2006-05-10 Thread Brown, Chris

Title: Message



Hi, 

 I am using the code 
below to serialize / deserialize AXIS beans back and forthto 
XML.
 However, I have 
recently came across a situation where say...

 
Original
 n:test 
xmlns:n="http:/blah"
 
bob1/bob
 
jim2/jim
 
/n:test

 Turns 
in to  

 n:test 
xmlns:n="http:/blah"
 
n:bob1/n:bob
 
n:jim2/n:jim
 
/n:test

Once serialization / 
deserialization has occured.

Does anyone know of a way to 
prevent this happening as it causing a lot of problems when attempting to 
use
 XPath on the resulting XML 
document.

Many thanks in advance
Chris

=



Andy,This should make your boss happy:public static 
Document serializeFromBinding(Object object, QName 
qname) 
throws ApplicationException { 
MessageContext msgContext = new 
MessageContext(newAxisServer()); 
msgContext.setEncodingStyle(null); 
TypeMappingRegistry tmr = new 
TypeMappingRegistryImpl(); 
msgContext.setTypeMappingRegistry(tmr); 
StringWriter writer = new StringWriter(); 
//temp SerializationContext ser = 
new 
SerializationContext(writer,msgContext); 
ser.setPretty(true); 
ser.setSendDecl(false); 
ser.setDoMultiRefs(false); try 
{ 
ser.serialize(qname, new AttributesImpl(), object, null,Boolean.FALSE, 
Boolean.FALSE); 
writer.flush(); 
return XMLUtils.newDocument(new 
InputSource(newStringReader(writer.toString(; 
} 
catch(ParserConfigurationException e) 
{ throw 
new ApplicationException(e.getMessage(), 
e); 
} catch(SAXException e) 
{ throw 
new DocumentStructureException(e.getMessage(), 
e); 
} catch(IOException e) 
{ throw 
new ApplicationException(e.getMessage(), 
e); } 
}YvesOn Fri, 2005-11-11 at 18:10 -0500, Andy Foster 
wrote: Hi all,  I'm at my last chance now, so if someone 
can help that would be great else I'm going to have to hand code XML 
output.  If you use WSDL2JAVA to generate stubs and call them 
you get a java response object back that represents the XML 
response  I need to get that response back into XML not the stub 
java representation.  I know axis can re serialise for me I just 
do not know how to invoke it  Please help as I have been 
searching for two days now and my boss is giving me the weekend and then 
we have to find another way to hand crank it which would be a very poor 
solution  Andy

Chris BrownSystem 
BuilderSopra Newell  Budge 

  
  
Tel
+44 (0)131 332 3311 

Fax
+44 (0)131 332 5938 

  

  


  
  
Sopra 
  Newell  Budge, Queensway House, 1 Queensferry Terrace, Edinburgh, EH4 
  3ER 
  
www.sopranewellandbudge.com 



_

Sopra Newell & Budge is the trading name of: Newell & Budge Limited (Registered in Scotland No. 94545 with Registered Offices at: 1 Queensferry Terrace, Edinburgh, EH4 3ER, VAT No. 774 7553 86), Newell & Budge Security Limited (Registered in Northern Ireland No. 39008, with Registered Offices at: 199 Airport Road West, Belfast, BT3 9ED, VAT No. 774 7553 86) and Sopra Group Limited (Registered in England, No. 1588948 with Registered Offices at: 17 St Helen's Place, London, EC3A 6DG, VAT No. 366 9784 84).

IMPORTANT NOTICE: This message is intended for the addressee only. The content may be confidential, legally privileged and protected by law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you are not the intended recipient please notify the sender and remove it from your system. Internet e-mails are not necessarily secure. Although we have taken steps to ensure this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice you should ensure they are actually virus free. The right to monitor e-mail communications through our network is reserved by Sopra Newell & Budge.
_

RE: AXIS Serialization / Deserialization problem with namespace prefixes

2006-05-10 Thread Griffin, Mark

Title: Message



Chris,
The 
difference is coming from being fully qualified to the namespace and not fully 
qualified. In your first example, bob is assumed to be part of http:/blah, where 
as in your second example it is explicitly set.

Depending on how your WSDL is constructed, clients will 
send either fully qualified or will assume the default namespace. I've 
found that this varies from Client to Client depending on the stack they are 
using for web services/soap/xml etc and how they interpret the WSDL. So 
you might get a prefix from some clients. Your xpath query should be able to 
handle this by using a wildcard for the prefix spot. Something like 
//*:test/*:bob/text() for example. I believe the clients should follow the 
namespace qualification as it is set in the WSDL but I haven't always found this 
to be the case.


markg
-Original Message-From: Brown, 
Chris [mailto:[EMAIL PROTECTED] Sent: Wednesday, 
May 10, 2006 10:50 AMTo: axis-user@ws.apache.orgSubject: 
AXIS Serialization / Deserialization problem with namespace 
prefixes

  Hi, 
  
   I am using the 
  code below to serialize / deserialize AXIS beans back and forthto 
  XML.
   However, I have 
  recently came across a situation where say...
  
   
  Original
   n:test 
  xmlns:n="http:/blah"
   
  bob1/bob
   
  jim2/jim
   
  /n:test
  
   Turns 
  in to  
  
   n:test 
  xmlns:n="http:/blah"
   
  n:bob1/n:bob
   
  n:jim2/n:jim
   
  /n:test
  
  Once serialization / 
  deserialization has occured.
  
  Does anyone know of a way to 
  prevent this happening as it causing a lot of problems when attempting to 
  use
   XPath on the resulting XML 
  document.
  
  Many thanks in advance
  Chris
  
  =
  
  
  
  Andy,This should make your boss happy:public static 
  Document serializeFromBinding(Object object, QName 
  qname) 
  throws ApplicationException 
  { MessageContext msgContext 
  = new 
  MessageContext(newAxisServer()); 
  msgContext.setEncodingStyle(null); 
  TypeMappingRegistry tmr = new 
  TypeMappingRegistryImpl(); 
  msgContext.setTypeMappingRegistry(tmr); 
  StringWriter writer = new StringWriter(); 
  //temp SerializationContext ser 
  = new 
  SerializationContext(writer,msgContext); 
  ser.setPretty(true); 
  ser.setSendDecl(false); 
  ser.setDoMultiRefs(false); 
  try { 
  ser.serialize(qname, new AttributesImpl(), object, null,Boolean.FALSE, 
  Boolean.FALSE); 
  writer.flush(); 
  return XMLUtils.newDocument(new 
  InputSource(newStringReader(writer.toString(; 
  } 
  catch(ParserConfigurationException e) 
  { throw 
  new ApplicationException(e.getMessage(), 
  e); 
  } catch(SAXException e) 
  { throw 
  new DocumentStructureException(e.getMessage(), 
  e); 
  } catch(IOException e) 
  { throw 
  new ApplicationException(e.getMessage(), 
  e); } 
  }YvesOn Fri, 2005-11-11 at 18:10 -0500, Andy Foster 
  wrote: Hi all,  I'm at my last chance now, so if 
  someone can help that would be great else I'm going to have to hand 
  code XML output.  If you use WSDL2JAVA to generate stubs and 
  call them you get a java response object back that represents the XML 
  response  I need to get that response back into XML not the 
  stub java representation.  I know axis can re serialise for me 
  I just do not know how to invoke it  Please help as I have 
  been searching for two days now and my boss is giving me the weekend 
  and then we have to find another way to hand crank it which would be a 
  very poor solution  Andy
  
  Chris 
  BrownSystem BuilderSopra Newell  Budge 
  
  


  Tel
  +44 (0)131 332 3311 
  
  Fax
  +44 (0)131 332 5938 
  

  

  
  


  Sopra 
Newell  Budge, Queensway House, 1 Queensferry Terrace, Edinburgh, 
EH4 3ER 

  www.sopranewellandbudge.com 
  
  _Sopra 
  Newell  Budge is the trading name of: Newell  Budge Limited 
  (Registered in Scotland No. 94545 with Registered Offices at: 1 Queensferry 
  Terrace, Edinburgh, EH4 3ER, VAT No. 774 7553 86), Newell  Budge Security 
  Limited (Registered in Northern Ireland No. 39008, with Registered Offices at: 
  199 Airport Road West, Belfast, BT3 9ED, VAT No. 774 7553 86) and Sopra Group 
  Limited (Registered in England, No. 1588948 with Registered Offices at: 17 St 
  Helen's Place, London, EC3A 6DG, VAT No. 366 9784 84).IMPORTANT 
  NOTICE: This message is intended for the addressee only. The content may be 
  confidential, legally privileged and protected by law. Unauthorised use, 
  copying or disclosure of any of it may be unlawful. If you are not the 
  intended recipient please notify the sender and remove it from your system. 
  Internet e-mails are not necessarily secure. Although we have taken steps to 
  ensure this e-mail and attachments are free from any virus, we advise that in 
  keeping with good

Re: AXIS Serialization / Deserialization problem with namespace prefixes


Would you be able to test latest AXIOM jars? There should be a nightly
jar you can pick from
http://cvs.apache.org/repository/ws-commons/jars/ i remember a bug
getting fixed in this area.

thanks,
dims

On 5/10/06, Brown, Chris [EMAIL PROTECTED] wrote:



Hi,

  I am using the code  below to serialize / deserialize AXIS beans back and 
forth to  XML.
  However, I have  recently came across a situation where say...

   Original
  n:test  xmlns:n=http:/blah
 bob1/bob
 jim2/jim
   /n:test

   Turns  in to

  n:test  xmlns:n=http:/blah
 n:bob1/n:bob
 n:jim2/n:jim
   /n:test

  Once serialization /  deserialization has occured.

  Does anyone know of a way to  prevent this happening as it causing a lot of 
problems when attempting to  use
  XPath on the resulting XML  document.

Many thanks in advance
Chris

=



Andy,

This should make your boss happy:

public static  Document serializeFromBinding(Object object, QName  qname)
 throws ApplicationException {

 MessageContext msgContext = new  MessageContext(new
AxisServer());
 msgContext.setEncodingStyle(null);

 TypeMappingRegistry tmr = new  TypeMappingRegistryImpl();
 msgContext.setTypeMappingRegistry(tmr);

 StringWriter writer = new StringWriter();  //temp
SerializationContext ser =  new  SerializationContext(writer,
msgContext);
 ser.setPretty(true);
 ser.setSendDecl(false);
 ser.setDoMultiRefs(false);

try  {
 ser.serialize(qname, new AttributesImpl(), object, null,
Boolean.FALSE,  Boolean.FALSE);
 writer.flush();
 return XMLUtils.newDocument(new  InputSource(new
StringReader(writer.toString(;
 }
 catch(ParserConfigurationException e)  {
throw  new ApplicationException(e.getMessage(),  e);
 }
catch(SAXException e)  {
throw  new DocumentStructureException(e.getMessage(),  e);
 }
catch(IOException e)  {
throw  new ApplicationException(e.getMessage(),  e);
}
 }

Yves

On Fri, 2005-11-11 at 18:10 -0500, Andy Foster  wrote:
 Hi all,

 I'm at my last chance now, so if someone  can help that would be great else
 I'm going to have to hand code XML  output.

 If you use WSDL2JAVA to generate stubs and call them  you get a java response
 object back that represents the XML  response

 I need to get that response back into XML not the stub  java representation.

 I know axis can re serialise for me I just  do not know how to invoke it

 Please help as I have been  searching for two days now and my boss is giving
 me the weekend and then  we have to find another way to hand crank it which
 would be a very poor  solution

 Andy


Chris Brown
System  Builder
Sopra Newell  Budge


 Tel +44 (0)131 332 3311Fax +44 (0)131 332 5938


 SopraNewell  Budge, Queensway House, 1 Queensferry Terrace, 
Edinburgh, EH43ER
 www.sopranewellandbudge.com

 
_

 Sopra Newell  Budge is the trading name of: Newell  Budge Limited (Registered in 
Scotland No. 94545 with Registered Offices at: 1 Queensferry Terrace, Edinburgh, EH4 3ER, 
VAT No. 774 7553 86), Newell  Budge Security Limited (Registered in Northern Ireland 
No. 39008, with Registered Offices at: 199 Airport Road West, Belfast, BT3 9ED, VAT No. 774 
7553 86) and Sopra Group Limited (Registered in England, No. 1588948 with Registered 
Offices at: 17 St Helen's Place, London, EC3A 6DG, VAT No. 366 9784 84).

 IMPORTANT NOTICE: This message is intended for the addressee only. The content may 
be confidential, legally privileged and protected by law. Unauthorised use, copying 
or disclosure of any of it may be unlawful. If you are not the intended recipient 
please notify the sender and remove it from your system. Internet e-mails are not 
necessarily secure. Although we have taken steps to ensure this e-mail and 
attachments are free from any virus, we advise that in keeping with good computing 
practice you should ensure they are actually virus free. The right to monitor 
e-mail communications through our network is reserved by Sopra Newell  Budge.
 
_





--
Davanum Srinivas : http://wso2.com/blogs/

Re: Axis2 1.0 getOutputStream() has already been called for this response

Just to inform you, with xmlbeans data binding I have the 
getOutputStream() has already been called for this response error



Davanum Srinivas a écrit :

Ah...let me see how to fix it.

thanks,
dims

On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:

With empty soap header, invocation works !

Arnaud

Davanum Srinivas a écrit :
 Hmm...i think i can guess where the problem is. could u please try
 adding an empty soap header in the soapui (when u send the request
 message?)

 thanks,
 dims

 On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:
 In tomcat logs I have:

 GRAVE: Exception Processing ErrorPage[errorCode=500,
 location=/axis2-web/Error/error500.jsp]
 org.apache.jasper.JasperException: getOutputStream() a déjà été 
appelé

 pour cette réponse
 at
 
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510) 



 at
 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387) 



 at
 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
 at 
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)

 at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 at
 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) 



 at
 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) 



 at
 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) 



 at
 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:465) 



 at
 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398) 



 at
 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) 



 at
 
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:363) 



 at
 
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284) 



 at
 
org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:228) 



 at
 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:134) 



 at
 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) 



 at
 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) 



 at
 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) 



 at
 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) 



 at
 
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) 



 at
 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) 



 at
 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) 



 at
 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) 



 at java.lang.Thread.run(Thread.java:595)

 Davanum Srinivas a écrit :
  Can you please check the tomcat logs?
 
  thanks,
  dims
 
  On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:
  This is stack  trace
 
 
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265) 



 
 
 
 
org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75) 



 
 
 
 
org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222) 



 
 
 
 
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76) 



 
 
 
 
org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183) 



 
 
 
 
org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168) 



 
 
 
 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)

  javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
  javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 
  Arnaud MERGEY a écrit :
   Hi,
   I want to generate a web service from a wsdl file with 
WSDL2Java.

   I'have tried adb data binding and jibx data binding.
   I successfully deploy my web service in tomcat (5.5.17)
   When I invoke the service, I'have an HTTP 500 server error
   java.lang.IllegalStateException: getOutputStream() has already
 been
   called for this response
   whith both adb and jibx databinding.
   The only code I have written is in generated skeleton and I only
   return the response object.
  
   Is something has similar problem ?
  
   thanks
  
  
  
  
 
 
 
 
  --
  Davanum Srinivas : http://wso2.com/blogs/
 




 --
 Davanum Srinivas : http://wso2.com/blogs/






--
Davanum Srinivas : http://wso2.com/blogs/

Re: Axis2 1.0 getOutputStream() has already been called for this response


Could u please open a new JIRA bug? with your wsdl and soap request?

thanks,
dims

On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:

Just to inform you, with xmlbeans data binding I have the
getOutputStream() has already been called for this response error


Davanum Srinivas a écrit :
 Ah...let me see how to fix it.

 thanks,
 dims

 On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:
 With empty soap header, invocation works !

 Arnaud

 Davanum Srinivas a écrit :
  Hmm...i think i can guess where the problem is. could u please try
  adding an empty soap header in the soapui (when u send the request
  message?)
 
  thanks,
  dims
 
  On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:
  In tomcat logs I have:
 
  GRAVE: Exception Processing ErrorPage[errorCode=500,
  location=/axis2-web/Error/error500.jsp]
  org.apache.jasper.JasperException: getOutputStream() a déjà été
 appelé
  pour cette réponse
  at
 
 
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)

 
  at
 
 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)

 
  at
 
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
  at
 org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at
 
 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)

 
  at
 
 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)

 
  at
 
 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)

 
  at
 
 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:465)

 
  at
 
 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)

 
  at
 
 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)

 
  at
 
 org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:363)

 
  at
 
 org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284)

 
  at
 
 
org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:228)

 
  at
 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:134)

 
  at
 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)

 
  at
 
 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)

 
  at
 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)

 
  at
 
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)

 
  at
 
 
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)

 
  at
 
 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)

 
  at
 
 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)

 
  at
 
 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)

 
  at java.lang.Thread.run(Thread.java:595)
 
  Davanum Srinivas a écrit :
   Can you please check the tomcat logs?
  
   thanks,
   dims
  
   On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:
   This is stack  trace
  
 
 
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265)

 
  
  
  
 
 
org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75)

 
  
  
  
 
 
org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222)

 
  
  
  
 
 
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76)

 
  
  
  
 
 
org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183)

 
  
  
  
 
 org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168)

 
  
  
  
 
 org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  
   Arnaud MERGEY a écrit :
Hi,
I want to generate a web service from a wsdl file with
 WSDL2Java.
I'have tried adb data binding and jibx data binding.
I successfully deploy my web service in tomcat (5.5.17)
When I invoke the service, I'have an HTTP 500 server error
java.lang.IllegalStateException: getOutputStream() has already
  been
called for this response
whith both adb and jibx databinding.
The only code I have written is in generated skeleton and I only
return the response object.
   
Is something has similar problem ?
   
thanks
   
   
   
   
  
  
  
  
   --
   Davanum Srinivas : http://wso2.com/blogs/
  
 
 
 
 
  --
  Davanum Srinivas : http://wso2.com/blogs/
 




 --
 Davanum Srinivas :

Is there any way to add additional restrictions into auto-generated schema?

2006-05-10 Thread Collin VanDyck

I'm really liking the schema generation capabilities of Axis.  I'm 
currently using 1.3, and am curious if there is any good way to keep 
Axis generating the XML Schema for my wrapped services but also to 
supply suggestions for some restrictions:


1. Enumerations - Can I say that a particular String member may have one 
of X different values?

2. Maximum field lengths or non-nillability for String member fields?

I seem to remember reading that this was not possible, but I figured I'd 
ask you guys as a last resort.  If this is not possible, I think that 
I'll likely finalize my object model, and then modify the schema to add 
my own restrictions (not desirable if the object model changes later)..


thanks
Collin

re: axis-wsdl2java task problem

2006-05-10 Thread James Armstrong

Hi,
I am using Axis wsdl2java to autogenerate needed stubs to that I can
deploy my web service using axis-admin task. The wsdl2java keeps on
over-writing my java source that java2wsdl used to generate the wsdl. Can I
tell it not to do that?!

Here is my axis-wsdl2java target:

target name=wsdl2java depends=java2wsdl description=Generates
a SOAP stubs.
mkdir dir=my source root/ !-- when I point output at
my original source root wsdl2java overwrites my java source--
axis-wsdl2java output=my source root
serverside=${serverside} url=${wsdl.file} deployscope=${deployscope}
helpergen=${helpergen} debug=true all=${all}/
echo message=wsdl2java has finished/
custom-modifyWsdd wsddaction=${wsdd}
wscodebehind=${classname}/
echo message=modifyWsdd has been completed./
/target

Here are my property definitions:

property name=url value=${wsdl.file} description=The URL to fetch and
generate the WSDL for. The URL can be remote or a local file./
property name=deployscope value=Application description=This
optional attribute adds scope to deploy.xml. The options are Application,
Request, Session./
property name=serverside value=true description=Generate
server-side bindings for the web service. The default is false./
property name=helpergen value=true description=Turns Helper
class generation on or off. The default is false./
property name=all value=true description=Generates code for
all elements, even unreferenced ones. The default is false/
property name=output value=${autogenerated.src}
description=The output directory for generated files./
property name=target.build.jar.name value=ecweb.jar/

Problem: Axis overwrites my java source with autogenerated code. Is there
anyway around this?
james

[Axis2 1.0] SGCCalculator sample

2006-05-10 Thread Rob Henley




Hi - I seem to get a couple of errors with the 
SGCCalculator:
1. out-of-the-box I get a 'log4j not properly 
initialised' error. I 'fxied' this by modifying the supplied client to turn off 
logging for the moment.
2. more seriously i get a 'module not found' when 
the client tries to engage the addressing module (trace below)

 [java] Exception in thread 
"main" org.apache.axis2.AxisFault: Module not found 
[java] at 
org.apache.axis2.description.AxisService.engageModule(AxisService.java:395) 
[java] at 
org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:279) 
[java] at sample.sgccalculator.CalcClient.main(Unknown 
Source)

A few questions:

i) should this sample work out of the box? If so, 
how does the client know where to find the module? (My understanding is that it 
would need to get the location of a 'repository' from somewhere?)
ii) is there any help on these samples - e.g. what 
they do, which data bindings they exercise etc.
iii) which ones have people got to work :-)

Many thanks
Rob

Re: Axis2 1.0 getOutputStream() has already been called for this response


http://issues.apache.org/jira/browse/AXIS2-707
thanks
Davanum Srinivas a écrit :

Could u please open a new JIRA bug? with your wsdl and soap request?

thanks,
dims

On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:

Just to inform you, with xmlbeans data binding I have the
getOutputStream() has already been called for this response error


Davanum Srinivas a écrit :
 Ah...let me see how to fix it.

 thanks,
 dims

 On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:
 With empty soap header, invocation works !

 Arnaud

 Davanum Srinivas a écrit :
  Hmm...i think i can guess where the problem is. could u please try
  adding an empty soap header in the soapui (when u send the request
  message?)
 
  thanks,
  dims
 
  On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:
  In tomcat logs I have:
 
  GRAVE: Exception Processing ErrorPage[errorCode=500,
  location=/axis2-web/Error/error500.jsp]
  org.apache.jasper.JasperException: getOutputStream() a déjà été
 appelé
  pour cette réponse
  at
 
 
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510) 



 
  at
 
 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387) 



 
  at
 
 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)

  at
 org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
  at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

  at
 
 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) 



 
  at
 
 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) 



 
  at
 
 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) 



 
  at
 
 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:465) 



 
  at
 
 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398) 



 
  at
 
 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) 



 
  at
 
 
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:363) 



 
  at
 
 
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284) 



 
  at
 
 
org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:228) 



 
  at
 
 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:134) 



 
  at
 
 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) 



 
  at
 
 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) 



 
  at
 
 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) 



 
  at
 
 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) 



 
  at
 
 
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) 



 
  at
 
 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) 



 
  at
 
 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) 



 
  at
 
 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) 



 
  at java.lang.Thread.run(Thread.java:595)
 
  Davanum Srinivas a écrit :
   Can you please check the tomcat logs?
  
   thanks,
   dims
  
   On 5/10/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:
   This is stack  trace
  
 
 
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265) 



 
  
  
  
 
 
org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75) 



 
  
  
  
 
 
org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222) 



 
  
  
  
 
 
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76) 



 
  
  
  
 
 
org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183) 



 
  
  
  
 
 
org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168) 



 
  
  
  
 
 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)
   
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
   
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

  
   Arnaud MERGEY a écrit :
Hi,
I want to generate a web service from a wsdl file with
 WSDL2Java.
I'have tried adb data binding and jibx data binding.
I successfully deploy my web service in tomcat (5.5.17)
When I invoke the service, I'have an HTTP 500 server error
java.lang.IllegalStateException: getOutputStream() has 
already

  been
called for this response
whith both adb and jibx databinding.
The only code I have written is in generated skeleton and 
I only

return the response object.
   
Is something has similar problem ?

Re: [Axis2 1.0] SGCCalculator sample

2006-05-10 Thread Eran Chinthaka

Rob Henley wrote:
 Hi - I seem to get a couple of errors with the SGCCalculator:
 1. out-of-the-box I get a 'log4j not properly initialised' error. I
 'fxied' this by modifying the supplied client to turn off logging for
 the moment.
 2. more seriously i get a 'module not found' when the client tries to
 engage the addressing module (trace below)
  
  [java] Exception in thread main org.apache.axis2.AxisFault:
 Module not found
  [java] at
 org.apache.axis2.description.AxisService.engageModule(AxisService.java:395)
  [java] at
 org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:279)
  [java] at sample.sgccalculator.CalcClient.main(Unknown Source)
 A few questions:

Did u read the para under Engaging Addressing in Client Side in
http://ws.apache.org/axis2/1_0/userguide3.html ?

  
 i) should this sample work out of the box? If so, how does the client
 know where to find the module? (My understanding is that it would need
 to get the location of a 'repository' from somewhere?)
 ii) is there any help on these samples - e.g. what they do, which data
 bindings they exercise etc.
 iii) which ones have people got to work :-)

All of them :)



  
 Many thanks
 Rob




signature.asc
Description: OpenPGP digital signature

Re: AXIS Serialization / Deserialization problem with namespace prefixes

Mark's comment here is inaccurate:

In your first example, bob is assumed to be part of http:/blah, where 
as in your second example it is explicitly set.

In this example:


n:test 
xmlns:n=http:/blah
 bob1/bob
 jim2/jim
/n:test












bob and jim are never assumed to be in the namespace of their parent element. When no namespace qualification is specified, the elements are assigned to the default
namespace (the namespace declared with no prefix set, e.g.,
xmlns=urn:foo.bar). If no default namespace has been declared, or if
the default namespace has been declared as xmlns=, then bob
and jim are in no namespace. Clients must always follow the namespace qualification rules specified in the WSDL or schema. The question is, how is the WSDL and/or schema defined for this document instance?
If you are using RPC style, then the accessor elements for the parameter types (bob and jim) must always be in no namespace. If you are using document style, then the schema dictates whether or not bob and jim should be qualified. If the schema specifies elementFormDefault=qualified or if bob and jim are defined as global elements, then bob and jim must be qualified.
If you are using document style and you want bob and jim to be unqualified, then you must define these element within the complexType definition for test, and you must make sure that the schema does not specify elementFormDefault=qualified. (Either explicitly specify elementFormDefault=unqualified or do not include the attribute. I recommend the former.)
AnneOn 5/10/06, Griffin, Mark [EMAIL PROTECTED] wrote:





Chris,
The 
difference is coming from being fully qualified to the namespace and not fully 
qualified. In your first example, bob is assumed to be part of http:/blah, where 
as in your second example it is explicitly set.

Depending on how your WSDL is constructed, clients will 
send either fully qualified or will assume the default namespace. I've 
found that this varies from Client to Client depending on the stack they are 
using for web services/soap/xml etc and how they interpret the WSDL. So 
you might get a prefix from some clients. Your xpath query should be able to 
handle this by using a wildcard for the prefix spot. Something like 
//*:test/*:bob/text() for example. I believe the clients should follow the 
namespace qualification as it is set in the WSDL but I haven't always found this 
to be the case.


markg

-Original Message-From: Brown, 
Chris [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 
May 10, 2006 10:50 AMTo: axis-user@ws.apache.orgSubject: 
AXIS Serialization / Deserialization problem with namespace 
prefixes

  Hi, 
  
   I am using the 
  code below to serialize / deserialize AXIS beans back and forthto 
  XML.
   However, I have 
  recently came across a situation where say...
  
   
  Original
   n:test 
  xmlns:n=http:/blah
   
  bob1/bob
   
  jim2/jim
   
  /n:test
  
   Turns 
  in to  
  
   n:test 
  xmlns:n=http:/blah
   
  n:bob1/n:bob
   
  n:jim2/n:jim
   
  /n:test
  
  Once serialization / 
  deserialization has occured.
  
  Does anyone know of a way to 
  prevent this happening as it causing a lot of problems when attempting to 
  use
   XPath on the resulting XML 
  document.
  
  Many thanks in advance
  Chris
  
  =
  
  
  
  Andy,This should make your boss happy:public static 
  Document serializeFromBinding(Object object, QName 
  qname) 
  throws ApplicationException 
  { MessageContext msgContext 
  = new 
  MessageContext(newAxisServer()); 
  msgContext.setEncodingStyle(null); 
  TypeMappingRegistry tmr = new 
  TypeMappingRegistryImpl(); 
  msgContext.setTypeMappingRegistry(tmr); 
  StringWriter writer = new StringWriter(); 
  //temp SerializationContext ser 
  = new 
  SerializationContext(writer,msgContext); 
  ser.setPretty(true); 
  ser.setSendDecl(false); 
  ser.setDoMultiRefs(false); 
  try { 
  ser.serialize(qname, new AttributesImpl(), object, null,Boolean.FALSE, 
  Boolean.FALSE); 
  writer.flush(); 
  return XMLUtils.newDocument(new 
  InputSource(newStringReader(writer.toString(; 
  } 
  catch(ParserConfigurationException e) 
  { throw 
  new ApplicationException(e.getMessage(), 
  e); 
  } catch(SAXException e) 
  { throw 
  new DocumentStructureException(e.getMessage(), 
  e); 
  } catch(IOException e) 
  { throw 
  new ApplicationException(e.getMessage(), 
  e); } 
  }YvesOn Fri, 2005-11-11 at 18:10 -0500, Andy Foster 
  wrote: Hi all,  I'm at my last chance now, so if 
  someone can help that would be great else I'm going to have to hand 
  code XML output.  If you use WSDL2JAVA to generate stubs and 
  call them you get a java response object back that represents the XML 
  response  I need to get that response back into XML not the 
  stub java representation.  I know axis can re serialise for me 
  I just do not know how to invoke it  Please help as I have 
  been searching for two days now and my boss is giving me the weekend 
  and

Re: axis-wsdl2java task problem

2006-05-10 Thread Rob Henley


Hi James
I'm not an expert, but I had a similar problem. I generated a server 
skeleton using java2wsdl and then added my implementation code, but of 
course next time I run java2wsdl it is overwritten. I have a directory 
structure something like:


axis2
  samples
 mySample ... MySkeleton.java
 src
org.apache.axis2 ... MySkeleton.java

I keep all my own code in the 'parent' directory (e.g. mySample), so first 
time around after running wsdl2java I moved the generated skeleton to this 
top level. Subsequently if i regenerate the code I just delete or rename the 
newly-generated skeleton (its a good idea to check it still has the same 
'interface' as your 'original'). When you build it doesn't seem to matter 
whether the file is in a subdirectory corresponding to its package name or 
not, so this seems like a simple way to keep your generated code separate 
from the stuff you've modified.


Cheers
Rob



- Original Message - 
From: James Armstrong [EMAIL PROTECTED]

To: axis-user@ws.apache.org
Sent: Wednesday, May 10, 2006 4:51 PM
Subject: re: axis-wsdl2java task problem



Hi,
I am using Axis wsdl2java to autogenerate needed stubs to that I can
deploy my web service using axis-admin task. The wsdl2java keeps on
over-writing my java source that java2wsdl used to generate the wsdl. Can 
I

tell it not to do that?!

Here is my axis-wsdl2java target:

target name=wsdl2java depends=java2wsdl description=Generates
a SOAP stubs.
mkdir dir=my source root/ !-- when I point output at
my original source root wsdl2java overwrites my java source--
axis-wsdl2java output=my source root
serverside=${serverside} url=${wsdl.file} deployscope=${deployscope}
helpergen=${helpergen} debug=true all=${all}/
echo message=wsdl2java has finished/
custom-modifyWsdd wsddaction=${wsdd}
wscodebehind=${classname}/
echo message=modifyWsdd has been completed./
/target

Here are my property definitions:

property name=url value=${wsdl.file} description=The URL to fetch 
and

generate the WSDL for. The URL can be remote or a local file./
property name=deployscope value=Application description=This
optional attribute adds scope to deploy.xml. The options are Application,
Request, Session./
property name=serverside value=true description=Generate
server-side bindings for the web service. The default is false./
property name=helpergen value=true description=Turns Helper
class generation on or off. The default is false./
property name=all value=true description=Generates code for
all elements, even unreferenced ones. The default is false/
property name=output value=${autogenerated.src}
description=The output directory for generated files./
property name=target.build.jar.name value=ecweb.jar/

Problem: Axis overwrites my java source with autogenerated code. Is there
anyway around this?
james

RE: AXIS Serialization / Deserialization problem with namespace prefixes

2006-05-10 Thread Griffin, Mark

Title: Message



Anne 
is right, of course. I was assuming that since your client was sending the 
prefix with qualifies it to http:/blah, that bob and jim belong to that 
namespace in your WSDL. Your second client(example) is interpreting 
it that way.

markg

  
  -Original Message-From: Anne Thomas 
  Manes [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 10, 2006 
  12:19 PMTo: axis-user@ws.apache.orgSubject: Re: AXIS 
  Serialization / Deserialization problem with namespace 
  prefixesMark's comment here is inaccurate:
  In 
  your first example, bob is assumed to be part of http:/blah, where as in your 
  second example it is explicitly set.In this 
  example:
  n:test 
  xmlns:n="http:/blah" 
  bob1/bob 
  jim2/jim/n:test
  
  bob and jim are 
  never "assumed" to be in the namespace of their parent element. When no 
  namespace qualification is specified, the elements are assigned to the default 
  namespace (the namespace declared with no prefix set, e.g., 
  xmlns="urn:foo.bar"). If no default namespace has been declared, or if the 
  default namespace has been declared as xmlns="", then bob and 
  jim are in no namespace. Clients must always follow the 
  namespace qualification rules specified in the WSDL or schema. The 
  question is, how is the WSDL and/or schema defined for this document instance? 
  If you are using RPC style, then the accessor elements for the 
  parameter types (bob and jim) must always be in no namespace. 
  If you are using document style, then the schema dictates whether or 
  not bob and jim should be qualified. If the schema specifies 
  elementFormDefault="qualified" or if bob and jim are defined 
  as global elements, then bob and jim must be qualified. 
  If you are using document style and you want bob and 
  jim to be unqualified, then you must define these element within the 
  complexType definition for test, and you must make sure that the 
  schema does not specify elementFormDefault="qualified". (Either explicitly 
  specify elementFormDefault="unqualified" or do not include the attribute. I 
  recommend the former.) Anne
  On 5/10/06, Griffin, 
  Mark [EMAIL PROTECTED] 
  wrote:
  

Chris,
The difference is coming 
from being fully qualified to the namespace and not fully qualified. In your 
first example, bob is assumed to be part of http:/blah, where as in your 
second example it is explicitly set.

Depending on how your WSDL 
is constructed, clients will send either fully qualified or will assume the 
default namespace. I've found that this varies from Client to Client 
depending on the stack they are using for web services/soap/xml etc and how 
they interpret the WSDL. So you might get a prefix from some clients. 
Your xpath query should be able to handle this by using a wildcard for the 
prefix spot. Something like //*:test/*:bob/text() for example. I 
believe the clients should follow the namespace qualification as it is set 
in the WSDL but I haven't always found this to be the 
case.


markg

-Original Message-From: 
Brown, Chris [mailto:[EMAIL PROTECTED]] Sent: 
Wednesday, May 10, 2006 10:50 AMTo: axis-user@ws.apache.orgSubject: AXIS 
Serialization / Deserialization problem with namespace 
prefixes

  Hi, 
  
   I am using the code below to serialize 
  / deserialize AXIS beans back and forthto XML.
   However, I have recently came across a 
  situation where say...
  
   Original
   n:test 
  xmlns:n="http:/blah"
   
  bob1/bob
   
  jim2/jim
   /n:test
  
   Turns in to  
  
  
   n:test 
  xmlns:n="http:/blah"
   
  n:bob1/n:bob
   
  n:jim2/n:jim
   
  /n:test
  
  Once serialization / 
  deserialization has occured.
  
  Does anyone know of a way 
  to prevent this happening as it causing a lot of problems when attempting 
  to use
   XPath on the resulting XML 
  document.
  
  Many thanks in 
  advance
  Chris
  
  =
  
  
  
  Andy,This should make your boss happy:public static 
  Document serializeFromBinding(Object object, QName 
  qname) 
  throws ApplicationException 
  { MessageContext 
  msgContext = new 
  MessageContext(newAxisServer()); 
  msgContext.setEncodingStyle(null); 
  TypeMappingRegistry tmr = new 
  TypeMappingRegistryImpl(); 
  msgContext.setTypeMappingRegistry(tmr); 
  StringWriter writer = new StringWriter(); 
  //temp SerializationContext 
  ser = new 
  SerializationContext(writer,msgContext); 
  ser.setPretty(true); 
  ser.setSendDecl(false); 
  ser.setDoMultiRefs(false); 
  try 
  { 
  ser.serialize(qname, new AttributesImpl(), object, null,Boolean.FALSE, 
  Boolean.FALSE);

policy on web-methods!!!

2006-05-10 Thread Wolfgang Schwarz

HiIs there any way in axis2 to impose restriction on webmethods i.e. who is allowed to access or make call to the particular method?Thanksschuller

RE: Jibx, Axis2 and multiple binding files

2006-05-10 Thread Andres Olave

Thanks Dennis,

Yeah, basically because i was just implementing a proof of concept and hadn't 
got around to having a single file which included all 4 files. Fixed that up 
and came across another interesting thing, which is that the wsdl message 
components have to be specified in the top level binding file. 

We will probably share some of those message components in different services, 
so (if i could sneakily suggest) that it'd be great if the code generator would 
be able to look at the mappings that are being included as well.

Anyway it all looks brilliant now as the interface the generator popped out 
with is exactly as expected - matching our thoroughly unit tested 
implementation. Now on to the axis2 testing :)

Cheers,
Andres

-Original Message-
From: Dennis Sosnoski [mailto:[EMAIL PROTECTED]
Sent: 09 May 2006 22:06
To: axis-user@ws.apache.org
Subject: Re: Jibx, Axis2 and multiple binding files


Hi Andres,

I didn't realize there'd be a need for handling multiple binding 
definitions as part of a single service, since generally a service is 
working with related data. Is there a reason you have your binding 
structured this way?

Right now the code makes the assumption (in both WSDL2Java and runtime) 
that there'll only be a single binding per service. I'm generalizing the 
code to handle unwrapped operations now so that you don't need to create 
or bind those wrapper classes for method parameters. Hopefully I can fix 
things for your case as well.

  - Dennis

Dennis M. Sosnoski
SOA, Web Services, and XML
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117



Andres Olave wrote:

 Hi there,

 I have been playing around with the Jibx support, but the current 
 project i am trying to migrate across to Axis 2 has 4 jibx mapping 
 files. How should I go about running the code generator to take in all 
 of the binding?files?

 Thanks,
 Andres


 IMPORTANT
 The contents of this email (and any attachment):
 (1) are confidential and may be legally privileged - if it is not 
 meant for
 you, please tell the sender, do not forward or copy the contents
 and delete it from your system immediately;
 (2) come from its author and may not necessarily reflect the opinions
 of Virgin Mobile.
 While emails and attachments are virus checked,
 we cannot accept any liability in respect of any viruses.
 We may monitor emails sent to Virgin Mobile.

 Want to know more about Virgin Mobile?
 Visit our website for the latest info, phones and special offers
 http://www.virgin.com/mobile

 Virgin Mobile Telecoms Ltd


IMPORTANT
The contents of this email (and any attachment):
(1) are confidential and may be legally privileged - if it is not meant for
you, please tell the sender, do not forward or copy the contents
and delete it from your system immediately;
(2) come from its author and may not necessarily reflect the opinions
of Virgin Mobile.
While emails and attachments are virus checked,
we cannot accept any liability in respect of any viruses.
We may monitor emails sent to Virgin Mobile.

Want to know more about Virgin Mobile?
Visit our website for the latest info, phones and special offers
http://www.virgin.com/mobile

Virgin Mobile Telecoms Ltd

Re: [Axis2 1.0] SGCCalculator sample

2006-05-10 Thread Rob Henley


Hi Eran
excellent - actually i had read it, but I'd forgotten :-(. I've got this 
working in 2 ways:


1. (as described in http://ws.apache.org/axis2/1_0/userguide3.html), by 
setting ConfigurationContext.

2. by setting -Daxis2.repo on the java command line

BUT the above page also says .. There are two ways of (engaging addressing 
for the Client). One is to get the addressing-version.mar from modules 
folder of the std-bin distribution. And then making that available in your 
classpath.


I added addressing-1.0.mar to the classpath I supply on the java command 
line and it doesn't help. I guess I'm missing something?


I also had to edit the supplied client to give the full (versioned) name of 
the module, i.e.


serviceClient.engageModule(new QName(addressing-1.0));

I'm not sure this is explained anywhere (?). All good stuff though ... 
thanks again!

Rob

- Original Message - 
From: Eran Chinthaka [EMAIL PROTECTED]

To: axis-user@ws.apache.org
Sent: Wednesday, May 10, 2006 5:17 PM
Subject: Re: [Axis2 1.0] SGCCalculator sample

Re: Jibx, Axis2 and multiple binding files

2006-05-10 Thread Dennis Sosnoski

Ah, good point on the top level binding file issue. I'll modify the code 
to also work with included bindings.


 - Dennis

Andres Olave wrote:


Thanks Dennis,

Yeah, basically because i was just implementing a proof of concept and hadn't got around to having a single file which included all 4 files. Fixed that up and came across another interesting thing, which is that the wsdl message components have to be specified in the top level binding file. 


We will probably share some of those message components in different services, 
so (if i could sneakily suggest) that it'd be great if the code generator would 
be able to look at the mappings that are being included as well.

Anyway it all looks brilliant now as the interface the generator popped out 
with is exactly as expected - matching our thoroughly unit tested 
implementation. Now on to the axis2 testing :)

Cheers,
Andres

-Original Message-
From: Dennis Sosnoski [mailto:[EMAIL PROTECTED]
Sent: 09 May 2006 22:06
To: axis-user@ws.apache.org
Subject: Re: Jibx, Axis2 and multiple binding files


Hi Andres,

I didn't realize there'd be a need for handling multiple binding 
definitions as part of a single service, since generally a service is 
working with related data. Is there a reason you have your binding 
structured this way?


Right now the code makes the assumption (in both WSDL2Java and runtime) 
that there'll only be a single binding per service. I'm generalizing the 
code to handle unwrapped operations now so that you don't need to create 
or bind those wrapper classes for method parameters. Hopefully I can fix 
things for your case as well.


 - Dennis

Dennis M. Sosnoski
SOA, Web Services, and XML
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117



Andres Olave wrote:

 


Hi there,

I have been playing around with the Jibx support, but the current 
project i am trying to migrate across to Axis 2 has 4 jibx mapping 
files. How should I go about running the code generator to take in all 
of the binding?files?


Thanks,
Andres


IMPORTANT
The contents of this email (and any attachment):
(1) are confidential and may be legally privileged - if it is not 
meant for

you, please tell the sender, do not forward or copy the contents
and delete it from your system immediately;
(2) come from its author and may not necessarily reflect the opinions
of Virgin Mobile.
While emails and attachments are virus checked,
we cannot accept any liability in respect of any viruses.
We may monitor emails sent to Virgin Mobile.

Want to know more about Virgin Mobile?
Visit our website for the latest info, phones and special offers
http://www.virgin.com/mobile

Virgin Mobile Telecoms Ltd
   




IMPORTANT
The contents of this email (and any attachment):
(1) are confidential and may be legally privileged - if it is not meant for
you, please tell the sender, do not forward or copy the contents
and delete it from your system immediately;
(2) come from its author and may not necessarily reflect the opinions
of Virgin Mobile.
While emails and attachments are virus checked,
we cannot accept any liability in respect of any viruses.
We may monitor emails sent to Virgin Mobile.

Want to know more about Virgin Mobile?
Visit our website for the latest info, phones and special offers
http://www.virgin.com/mobile

Virgin Mobile Telecoms Ltd

RE: axis-wsdl2java task problem

2006-05-10 Thread James Armstrong

 Rob,
I really appreciate your help. Yes, I did something similar and now
everything is working.
Thanks again,
james

-Original Message-
From: Rob Henley [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 10, 2006 10:23 AM
To: axis-user@ws.apache.org
Subject: Re: axis-wsdl2java task problem

Hi James
I'm not an expert, but I had a similar problem. I generated a server 
skeleton using java2wsdl and then added my implementation code, but of 
course next time I run java2wsdl it is overwritten. I have a directory 
structure something like:

axis2
   samples
  mySample ... MySkeleton.java
  src
 org.apache.axis2 ... MySkeleton.java

I keep all my own code in the 'parent' directory (e.g. mySample), so first 
time around after running wsdl2java I moved the generated skeleton to this 
top level. Subsequently if i regenerate the code I just delete or rename the

newly-generated skeleton (its a good idea to check it still has the same 
'interface' as your 'original'). When you build it doesn't seem to matter 
whether the file is in a subdirectory corresponding to its package name or 
not, so this seems like a simple way to keep your generated code separate 
from the stuff you've modified.

Cheers
Rob

- Original Message - 
From: James Armstrong [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Wednesday, May 10, 2006 4:51 PM
Subject: re: axis-wsdl2java task problem

 Hi,
 I am using Axis wsdl2java to autogenerate needed stubs to that I can
 deploy my web service using axis-admin task. The wsdl2java keeps on
 over-writing my java source that java2wsdl used to generate the wsdl. Can 
 I
 tell it not to do that?!

 Here is my axis-wsdl2java target:

 target name=wsdl2java depends=java2wsdl description=Generates
 a SOAP stubs.
 mkdir dir=my source root/ !-- when I point output at
 my original source root wsdl2java overwrites my java source--
 axis-wsdl2java output=my source root
 serverside=${serverside} url=${wsdl.file} deployscope=${deployscope}
 helpergen=${helpergen} debug=true all=${all}/
 echo message=wsdl2java has finished/
 custom-modifyWsdd wsddaction=${wsdd}
 wscodebehind=${classname}/
 echo message=modifyWsdd has been completed./
 /target

 Here are my property definitions:

 property name=url value=${wsdl.file} description=The URL to fetch 
 and
 generate the WSDL for. The URL can be remote or a local file./
 property name=deployscope value=Application description=This
 optional attribute adds scope to deploy.xml. The options are Application,
 Request, Session./
 property name=serverside value=true description=Generate
 server-side bindings for the web service. The default is false./
 property name=helpergen value=true description=Turns Helper
 class generation on or off. The default is false./
 property name=all value=true description=Generates code for
 all elements, even unreferenced ones. The default is false/
 property name=output value=${autogenerated.src}
 description=The output directory for generated files./
 property name=target.build.jar.name value=ecweb.jar/

 Problem: Axis overwrites my java source with autogenerated code. Is there
 anyway around this?
 james

[Axis2 1.0] Data binding Error after WSDL2Java code generation

2006-05-10 Thread Sebastian J. Schultheiss


Hi there!

We've used the attached WSDL to create a service  client by means of
the WSDL2Java tool (xmlbeans databinding). After implementing the
simplest of business logics in the server, we deployed the service .aar
in the axis2 install inside a tomcat server. According to the status
page, the service is running error free.

The client was also created by WSDL2Java, where we wrote a simple main()
class to test the client. We've pasted it below.

public static void main(String[] args) {
   try {
 PredictLocalizationRequestDocument pdoc =
PredictLocalizationRequestDocument.Factory.newInstance();
 pdoc.addNewPredictLocalizationRequest();
 pdoc.getPredictLocalizationRequest().setSequence(ASDF);
 pdoc.getPredictLocalizationRequest().setOrganism(ANIMAL);
 TextLocServiceStub sender = new
TextLocServiceStub(http://localhost/axis2/services/TextLocService;);
 PredictLocalizationResponseDocument res =
sender.predictLocalization(pdoc);
 System.out.println(res.toString());
   } catch (Exception e) {
 e.printStackTrace();
   }
}

The client now runs up until the document is being sent, where it throws
an Exception. The stack trace is below. We think it is still a
client-side problem, although the client does complain if it is not
connected to the server and doesn't throw this exception.

Please let us know if we should change anything about our client
generation procedure, or how we can use the test client jar that is also
generated by the WSDL2Java tool.

Thanks a lot for your time!

Greetings,

-- Sebastian


org.apache.axis2.AxisFault: Data binding error
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287)
at
org.apache.axis2.TextLocServiceStub.predictLocalization(TextLocServiceStub.java:133)
at org.apache.axis2.runLoc.main(runLoc.java:26)
Caused by: java.lang.Exception: org.apache.axis2.AxisFault: Data binding
error; nested exception is:
java.lang.RuntimeException: Data binding error
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)
at
org.apache.axis2.TextLocServiceMessageReceiverInOut.invokeBusinessLogic(TextLocServiceMessageReceiverInOut.java:66)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.RuntimeException: Data binding error
at
org.apache.axis2.TextLocServiceMessageReceiverInOut.fromOM(TextLocServiceMessageReceiverInOut.java:158)
at
org.apache.axis2.TextLocServiceMessageReceiverInOut.invokeBusinessLogic(TextLocServiceMessageReceiverInOut.java:50)
... 20 more
Caused by: java.lang.NullPointerException
at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.attr(Cur.java:3041)
at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.attr(Cur.java:3058)
at org.apache.xmlbeans.impl.store.Locale.doNamespaces(Locale.java:900)
at
org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1135)
at 
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)
at 
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826)
at

Re: [Axis2 1.0] Data binding Error after WSDL2Java code generation

2006-05-10 Thread Wolfgang Schuller

Hi,You need to run generated build.xml file or specific target ant jar-client, it will create jar file for which includes all the databinding code as well supported classes. Just make sure if that jar is in your client classpath along with other axis2 and xmlbean libraries.
Hope this helps,schullerOn 5/10/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote:
Hi there!We've used the attached WSDL to create a service  client by means ofthe WSDL2Java tool (xmlbeans databinding). After implementing thesimplest of business logics in the server, we deployed the service .aar
in the axis2 install inside a tomcat server. According to the statuspage, the service is running error free.The client was also created by WSDL2Java, where we wrote a simple main()class to test the client. We've pasted it below.
public static void main(String[] args) {try {PredictLocalizationRequestDocument pdoc =PredictLocalizationRequestDocument.Factory.newInstance();pdoc.addNewPredictLocalizationRequest();
pdoc.getPredictLocalizationRequest().setSequence(ASDF);pdoc.getPredictLocalizationRequest().setOrganism(ANIMAL);TextLocServiceStub sender = newTextLocServiceStub(
http://localhost/axis2/services/TextLocService);PredictLocalizationResponseDocument res =sender.predictLocalization(pdoc);
System.out.println(res.toString());} catch (Exception e) {e.printStackTrace();}}The client now runs up until the document is being sent, where it throwsan Exception. The stack trace is below. We think it is still a
client-side problem, although the client does complain if it is notconnected to the server and doesn't throw this exception.Please let us know if we should change anything about our clientgeneration procedure, or how we can use the test client jar that is also
generated by the WSDL2Java tool.Thanks a lot for your time!Greetings,-- Sebastianorg.apache.axis2.AxisFault: Data binding erroratorg.apache.axis2.description.OutInAxisOperationClient.execute
(OutInAxisOperation.java:287)atorg.apache.axis2.TextLocServiceStub.predictLocalization(TextLocServiceStub.java:133)at org.apache.axis2.runLoc.main(runLoc.java:26)Caused by: java.lang.Exception
: org.apache.axis2.AxisFault: Data bindingerror; nested exception is:java.lang.RuntimeException: Data binding errorat org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)atorg.apache.axis2.TextLocServiceMessageReceiverInOut.invokeBusinessLogic
(TextLocServiceMessageReceiverInOut.java:66)atorg.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)at org.apache.axis2.engine.AxisEngine.receive
(AxisEngine.java:454)atorg.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java
:136)at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:252)atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)atorg.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java
:213)atorg.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)atorg.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)atorg.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:105)atorg.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)atorg.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
atorg.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)atorg.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
atorg.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)atorg.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)at java.lang.Thread.run(Thread.java:595)Caused by: java.lang.RuntimeException: Data binding erroratorg.apache.axis2.TextLocServiceMessageReceiverInOut.fromOM
(TextLocServiceMessageReceiverInOut.java:158)atorg.apache.axis2.TextLocServiceMessageReceiverInOut.invokeBusinessLogic(TextLocServiceMessageReceiverInOut.java:50)... 20 moreCaused by: java.lang.NullPointerException
at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.attr(Cur.java:3041)at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.attr(Cur.java:3058)at org.apache.xmlbeans.impl.store.Locale.doNamespaces
(Locale.java:900)atorg.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1135)at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject

Re: [Axis2 1.0] Data binding Error after WSDL2Java code generation


Could you please log a bug in JIRA and then upload the wsdl? So that
we can track and fix the problem?

thanks,
dims

On 5/10/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote:

Hi there!

We've used the attached WSDL to create a service  client by means of
the WSDL2Java tool (xmlbeans databinding). After implementing the
simplest of business logics in the server, we deployed the service .aar
in the axis2 install inside a tomcat server. According to the status
page, the service is running error free.

The client was also created by WSDL2Java, where we wrote a simple main()
class to test the client. We've pasted it below.

public static void main(String[] args) {
try {
  PredictLocalizationRequestDocument pdoc =
PredictLocalizationRequestDocument.Factory.newInstance();
  pdoc.addNewPredictLocalizationRequest();
  pdoc.getPredictLocalizationRequest().setSequence(ASDF);
  pdoc.getPredictLocalizationRequest().setOrganism(ANIMAL);
  TextLocServiceStub sender = new
TextLocServiceStub(http://localhost/axis2/services/TextLocService;);
  PredictLocalizationResponseDocument res =
sender.predictLocalization(pdoc);
  System.out.println(res.toString());
} catch (Exception e) {
  e.printStackTrace();
}
}

The client now runs up until the document is being sent, where it throws
an Exception. The stack trace is below. We think it is still a
client-side problem, although the client does complain if it is not
connected to the server and doesn't throw this exception.

Please let us know if we should change anything about our client
generation procedure, or how we can use the test client jar that is also
generated by the WSDL2Java tool.

Thanks a lot for your time!

Greetings,

-- Sebastian


org.apache.axis2.AxisFault: Data binding error
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287)
at
org.apache.axis2.TextLocServiceStub.predictLocalization(TextLocServiceStub.java:133)
at org.apache.axis2.runLoc.main(runLoc.java:26)
Caused by: java.lang.Exception: org.apache.axis2.AxisFault: Data binding
error; nested exception is:
java.lang.RuntimeException: Data binding error
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)
at
org.apache.axis2.TextLocServiceMessageReceiverInOut.invokeBusinessLogic(TextLocServiceMessageReceiverInOut.java:66)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.RuntimeException: Data binding error
at
org.apache.axis2.TextLocServiceMessageReceiverInOut.fromOM(TextLocServiceMessageReceiverInOut.java:158)
at
org.apache.axis2.TextLocServiceMessageReceiverInOut.invokeBusinessLogic(TextLocServiceMessageReceiverInOut.java:50)
... 20 more
Caused by: java.lang.NullPointerException
at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.attr(Cur.java:3041)
at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.attr(Cur.java:3058)
at org.apache.xmlbeans.impl.store.Locale.doNamespaces(Locale.java:900)
at
org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1135)
at

Re: [Axis2 1.0] Data binding Error after WSDL2Java code generation

There is already is a jira for this error, judging by the stack trace: 

  http://issues.apache.org/jira/browse/AXIS2-649

I started digging deeper last weekend - I updated the issue - but I'm a bit swamped at the moment to go any further for now.  

Robert
http://www.braziloutsource.com/On 5/10/06, Davanum Srinivas [EMAIL PROTECTED]
 wrote:Could you please log a bug in JIRA and then upload the wsdl? So that
we can track and fix the problem?thanks,dimsOn 5/10/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote: Hi there! We've used the attached WSDL to create a service  client by means of
 the WSDL2Java tool (xmlbeans databinding). After implementing the simplest of business logics in the server, we deployed the service .aar in the axis2 install inside a tomcat server. According to the status
 page, the service is running error free. The client was also created by WSDL2Java, where we wrote a simple main() class to test the client. We've pasted it below. public static void main(String[] args) {
 try { PredictLocalizationRequestDocument pdoc = PredictLocalizationRequestDocument.Factory.newInstance(); pdoc.addNewPredictLocalizationRequest(); pdoc.getPredictLocalizationRequest
().setSequence(ASDF); pdoc.getPredictLocalizationRequest().setOrganism(ANIMAL); TextLocServiceStub sender = new TextLocServiceStub(
http://localhost/axis2/services/TextLocService); PredictLocalizationResponseDocument res =
sender.predictLocalization(pdoc); System.out.println(res.toString()); } catch (Exception e) { e.printStackTrace(); } } The client now runs up until the document is being sent, where it throws
 an Exception. The stack trace is below. We think it is still a client-side problem, although the client does complain if it is not connected to the server and doesn't throw this exception.
 Please let us know if we should change anything about our client generation procedure, or how we can use the test client jar that is also generated by the WSDL2Java tool. Thanks a lot for your time!
 Greetings, -- Sebastian org.apache.axis2.AxisFault: Data binding error at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java
:287) at org.apache.axis2.TextLocServiceStub.predictLocalization(TextLocServiceStub.java:133) at org.apache.axis2.runLoc.main(runLoc.java:26) Caused by: java.lang.Exception: 
org.apache.axis2.AxisFault: Data binding error; nested exception is: java.lang.RuntimeException: Data binding error at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318) at
 org.apache.axis2.TextLocServiceMessageReceiverInOut.invokeBusinessLogic(TextLocServiceMessageReceiverInOut.java:66) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java
:37) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
 at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service
(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java
:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java
:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.RuntimeException: Data binding error
 at org.apache.axis2.TextLocServiceMessageReceiverInOut.fromOM(TextLocServiceMessageReceiverInOut.java:158) at org.apache.axis2.TextLocServiceMessageReceiverInOut.invokeBusinessLogic
(TextLocServiceMessageReceiverInOut.java:50) ... 20 more Caused by: java.lang.NullPointerException at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.attr(Cur.java:3041) at 
org.apache.xmlbeans.impl.store.Cur$CurLoadContext.attr(Cur.java:3058) at org.apache.xmlbeans.impl.store.Locale.doNamespaces(Locale.java:900) at org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader
(Locale.java:1135) at

Axis 1.3 isn't working at all with JDK 1.5.0_06

2006-05-10 Thread robert

So I've got a web app and if I put in Axis's 1.3 jars (not including endorsed) I
get the following

please note if I change these to Axis 1.4's jars and redeploy everything works
correctly.

What am I missing?


AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: java.lang.reflect.InvocationTargetException
 faultActor:
 faultNode:
 faultDetail:
   
{http://xml.apache.org/axis/}stackTrace:java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
at
org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)



This message was sent using IMP, the Internet Messaging Program.

[AXIS2] Replication For High Availability

2006-05-10 Thread kensky


Hie, 
In my application I want to provide high availability and fault tolerance of
web services deployed on axis2 and tomcat. 

Is it possible to have this featrue using Axis2 with Tomcat. if so how? 

Thanks and Regards
kensky 
--
View this message in context: 
http://www.nabble.com/-AXIS2-Replication-For-High-Availability-t1596410.html#a4331183
Sent from the Axis - User forum at Nabble.com.

Re: Axis 1.3 isn't working at all with JDK 1.5.0_06

2006-05-10 Thread robert

This turned out to be missing jars. Thankfully I found a hint online that
suggested you catch Throwable in your binding implementation to see what the
root exception was. Thanks who whoever posted that you said me a lot of
headache. I sure hope that the later versions of Axis no longer swallow this
exception.

Quoting [EMAIL PROTECTED]:

 So I've got a web app and if I put in Axis's 1.3 jars (not including
 endorsed) I
 get the following
 
 please note if I change these to Axis 1.4's jars and redeploy everything
 works
 correctly.
 
 What am I missing?
 
 
 AxisFault
  faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
  faultSubcode:
  faultString: java.lang.reflect.InvocationTargetException
  faultActor:
  faultNode:
  faultDetail:


{http://xml.apache.org/axis/}stackTrace:java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at
 org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
 at

org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
 at
 org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
 at

org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
 at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
 
 
 
 This message was sent using IMP, the Internet Messaging Program.
 
 





This message was sent using IMP, the Internet Messaging Program.

Re: [Axis2 1.0] Data binding Error after WSDL2Java code generation

Sebastian,There are errors in your WSDL. You must remove the namespace attributes from the soap:body binding descriptions. (The namespace attribute must be use only with RPC style.)Anne
On 5/10/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote:
Hi there!We've used the attached WSDL to create a service  client by means ofthe WSDL2Java tool (xmlbeans databinding). After implementing thesimplest of business logics in the server, we deployed the service .aar
in the axis2 install inside a tomcat server. According to the statuspage, the service is running error free.The client was also created by WSDL2Java, where we wrote a simple main()class to test the client. We've pasted it below.
public static void main(String[] args) {try {PredictLocalizationRequestDocument pdoc =PredictLocalizationRequestDocument.Factory.newInstance();pdoc.addNewPredictLocalizationRequest();
pdoc.getPredictLocalizationRequest().setSequence(ASDF);pdoc.getPredictLocalizationRequest().setOrganism(ANIMAL);TextLocServiceStub sender = newTextLocServiceStub(
http://localhost/axis2/services/TextLocService);PredictLocalizationResponseDocument res =sender.predictLocalization(pdoc);
System.out.println(res.toString());} catch (Exception e) {e.printStackTrace();}}The client now runs up until the document is being sent, where it throwsan Exception. The stack trace is below. We think it is still a
client-side problem, although the client does complain if it is notconnected to the server and doesn't throw this exception.Please let us know if we should change anything about our clientgeneration procedure, or how we can use the test client jar that is also
generated by the WSDL2Java tool.Thanks a lot for your time!Greetings,-- Sebastianorg.apache.axis2.AxisFault: Data binding erroratorg.apache.axis2.description.OutInAxisOperationClient.execute
(OutInAxisOperation.java:287)atorg.apache.axis2.TextLocServiceStub.predictLocalization(TextLocServiceStub.java:133)at org.apache.axis2.runLoc.main(runLoc.java:26)Caused by: java.lang.Exception
: org.apache.axis2.AxisFault: Data bindingerror; nested exception is:java.lang.RuntimeException: Data binding errorat org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)atorg.apache.axis2.TextLocServiceMessageReceiverInOut.invokeBusinessLogic
(TextLocServiceMessageReceiverInOut.java:66)atorg.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)at org.apache.axis2.engine.AxisEngine.receive
(AxisEngine.java:454)atorg.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java
:136)at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:252)atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)atorg.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java
:213)atorg.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)atorg.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)atorg.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:105)atorg.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)atorg.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
atorg.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)atorg.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
atorg.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)atorg.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)at java.lang.Thread.run(Thread.java:595)Caused by: java.lang.RuntimeException: Data binding erroratorg.apache.axis2.TextLocServiceMessageReceiverInOut.fromOM
(TextLocServiceMessageReceiverInOut.java:158)atorg.apache.axis2.TextLocServiceMessageReceiverInOut.invokeBusinessLogic(TextLocServiceMessageReceiverInOut.java:50)... 20 moreCaused by: java.lang.NullPointerException
at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.attr(Cur.java:3041)at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.attr(Cur.java:3058)at org.apache.xmlbeans.impl.store.Locale.doNamespaces
(Locale.java:900)atorg.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1135)at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject
(Locale.java:826)atorg.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231)ataxis2.apache.org.xsd.PredictLocalizationRequestDocument$Factory.parse(PredictLocalizationRequestDocument.java

Re: REPOST FOR HELP: Axis client logging from web applet causes security error

2006-05-10 Thread ANTHONY ZIOLKOWSKI


Nope, still doesn't work. Looks like the same error to me.
Just to help this is the html code:
!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"htmlheadmeta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"titleDemo Page/title/headbodySomething Stupid 3brAPPLET CODE="com.zeesol.applets.BaseRunner.class" archive="ZeesolApplets.jar,axis.jar,jaxrpc.jar,commons-logging-1.0.4.jar,commons-discovery-0.2.jar" WIDTH=717 height=353/applet/body/html
Latest stack trace:

Java Plug-in 1.5.0_02Using JRE version 1.5.0_02 Java HotSpot(TM) Client VMException in thread "AWT-EventQueue-2" java.lang.ExceptionInInitializerErrorat org.apache.commons.discovery.jdk.JDKHooks.clinit(JDKHooks.java:75)at org.apache.commons.discovery.tools.DiscoverSingleton.find(DiscoverSingleton.java:412)at org.apache.commons.discovery.tools.DiscoverSingleton.find(DiscoverSingleton.java:378)at org.apache.axis.components.logger.LogFactory$1.run(LogFactory.java:45)at java.security.AccessController.doPrivileged(Native Method)at org.apache.axis.components.logger.LogFactory.getLogFactory(LogFactory.java:41)at org.apache.axis.components.logger.LogFactory.clinit(LogFactory.java:33)at org.apache.axis.handlers.BasicHandler.clinit(BasicHandler.java:43)at org.apache.axis.client.Service.getAxisClient(Service.java:104)at
 org.apache.axis.client.Service.init(Service.java:113)at com.zeesol.bizservice.client.BizService_ServiceLocator.init(BizService_ServiceLocator.java:12)at com.mazuma.applets.BaseRunner$1.actionPerformed(BaseRunner.java:156)at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)at javax.swing.DefaultButtonModel.setPressed(Unknown Source)at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)at java.awt.Component.processMouseEvent(Unknown Source)at javax.swing.JComponent.processMouseEvent(Unknown Source)at java.awt.Component.processEvent(Unknown Source)at java.awt.Container.processEvent(Unknown Source)at java.awt.Component.dispatchEventImpl(Unknown Source)at
 java.awt.Container.dispatchEventImpl(Unknown Source)at java.awt.Component.dispatchEvent(Unknown Source)at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)at java.awt.Container.dispatchEventImpl(Unknown Source)at java.awt.Component.dispatchEvent(Unknown Source)at java.awt.EventQueue.dispatchEvent(Unknown Source)at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)at java.awt.EventDispatchThread.pumpEvents(Unknown Source)at java.awt.EventDispatchThread.pumpEvents(Unknown Source)at java.awt.EventDispatchThread.run(Unknown Source)Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission
 createClassLoader)at java.security.AccessControlContext.checkPermission(Unknown Source)at java.security.AccessController.checkPermission(Unknown Source)at java.lang.SecurityManager.checkPermission(Unknown Source)at java.lang.SecurityManager.checkCreateClassLoader(Unknown Source)at java.lang.ClassLoader.init(Unknown Source)at org.apache.commons.discovery.jdk.PsuedoSystemClassLoader.init(PsuedoSystemClassLoader.java:73)at org.apache.commons.discovery.jdk.JDK12Hooks.findSystemClassLoader(JDK12Hooks.java:215)at org.apache.commons.discovery.jdk.JDK12Hooks.clinit(JDK12Hooks.java:73)... 35 more- Original Message From: robert lazarski [EMAIL PROTECTED]To: ANTHONY ZIOLKOWSKI [EMAIL PROTECTED]Sent: Wednesday, May 10, 2006 8:26:12 PMSubject: Re: REPOST FOR HELP: Axis client logging from web applet causes security
 errorPut it under WEB-INF/classes . Make sure you have the log4j.jar under WEB-INF/lib . If there is a commons-logging.properties file, make sure it has this property: org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLoggerThe file I posted, if you follow those instructions, should disable file logging. HTH,Roberthttp://www.braziloutsource.com/
On 5/10/06, ANTHONY ZIOLKOWSKI [EMAIL PROTECTED]  wrote:




Thanks for this. However, I don't know where to put log4j.properties file. I put it in the same folder as the web that runs the applet, but I still get the same error. Where do I put that file?- Original Message From: robert lazarski  [EMAIL PROTECTED]To: axis-user@ws.apache.org; ANTHONY ZIOLKOWSKI  [EMAIL PROTECTED]Sent: Monday, May 8, 2006 8:36:16 AMSubject: Re: REPOST FOR HELP: Axis client logging from web applet causes security errorI suspect this is primarily a log4j / commons-logging issue. Try editing the properties of each and comment out the file appenders. Or simply enable log4j based logging in the commons property file, and use your own
 log4j.properties file instead of the one that comes with axis. I'm

Scoped services.

2006-05-10 Thread Robert Nicholson

A few questions. I see too many files errors in tomcat with Axis 1.3 and I'm wondering if it's related to my scope settings. ie. request as the default.What is a session enabled client exactly?"Session" scope will create a new object for each session-enabled client who accesses your service. To specify the scope option, you add a parameter to your service like this (where "value" is request, session, or application):service name="MyService"...  parameter name="scope" value="value"/  .../serviceAre there known problems with axis opening up too many files on Tomcat.

Re: [Axis2 1.0] Data binding Error after WSDL2Java code generation

Anne, might you be able to take a look at the attached wsdl ? It
validates fine, but I see the same error, created a jira, and I'd like
to track it down. Don't think this wsdl has changed - I thought
it was working in previous axis2 versions. 

Thanks, 
Robert
http://www.braziloutsource.com/
On 5/10/06, Anne Thomas Manes [EMAIL PROTECTED] wrote:
Sebastian,There are errors in your WSDL. You must remove
the namespace attributes from the soap:body binding
descriptions. (The namespace attribute must be use only with RPC style.)Anne
On 5/10/06, Sebastian J. Schultheiss [EMAIL PROTECTED]
 wrote:
Hi there!We've used the attached WSDL to create a service  client by means ofthe WSDL2Java tool (xmlbeans databinding). After implementing thesimplest of business logics in the server, we deployed the service .aar
in the axis2 install inside a tomcat server. According to the statuspage, the service is running error free.The client was also created by WSDL2Java, where we wrote a simple main()class to test the client. We've pasted it below.
public static void main(String[] args) {try {PredictLocalizationRequestDocument pdoc =PredictLocalizationRequestDocument.Factory.newInstance();pdoc.addNewPredictLocalizationRequest
();
pdoc.getPredictLocalizationRequest().setSequence(ASDF);pdoc.getPredictLocalizationRequest().setOrganism(ANIMAL);TextLocServiceStub sender = newTextLocServiceStub(
http://localhost/axis2/services/TextLocService);PredictLocalizationResponseDocument res =
sender.predictLocalization(pdoc);
System.out.println(res.toString());} catch (Exception e) {e.printStackTrace();}}The client now runs up until the document is being sent, where it throwsan Exception. The stack trace is below. We think it is still a
client-side problem, although the client does complain if it is notconnected to the server and doesn't throw this exception.Please let us know if we should change anything about our clientgeneration procedure, or how we can use the test client jar that is also
generated by the WSDL2Java tool.Thanks a lot for your time!Greetings,-- Sebastianorg.apache.axis2.AxisFault: Data binding erroratorg.apache.axis2.description.OutInAxisOperationClient.execute

(OutInAxisOperation.java:287)atorg.apache.axis2.TextLocServiceStub.predictLocalization(TextLocServiceStub.java:133)at org.apache.axis2.runLoc.main(runLoc.java:26)Caused by: java.lang.Exception

: org.apache.axis2.AxisFault: Data bindingerror; nested exception is:java.lang.RuntimeException: Data binding errorat org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)at
org.apache.axis2.TextLocServiceMessageReceiverInOut.invokeBusinessLogic
(TextLocServiceMessageReceiverInOut.java:66)atorg.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)at org.apache.axis2.engine.AxisEngine.receive

(AxisEngine.java:454)atorg.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java

:136)at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter

(ApplicationFilterChain.java:252)atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)atorg.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java

:213)atorg.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)atorg.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)atorg.apache.catalina.valves.ErrorReportValve.invoke

(ErrorReportValve.java:105)atorg.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)atorg.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)

atorg.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)atorg.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)

atorg.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)atorg.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)at java.lang.Thread.run(Thread.java:595)Caused by: java.lang.RuntimeException: Data binding erroratorg.apache.axis2.TextLocServiceMessageReceiverInOut.fromOM

(TextLocServiceMessageReceiverInOut.java:158)atorg.apache.axis2.TextLocServiceMessageReceiverInOut.invokeBusinessLogic(TextLocServiceMessageReceiverInOut.java:50)... 20 moreCaused by: java.lang.NullPointerException

at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.attr(Cur.java:3041)at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.attr(Cur.java:3058)at org.apache.xmlbeans.impl.store.Locale.doNamespaces

(Locale.java:900)atorg.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1135)at

Re: [AXIS2] Replication For High Availability

I believe sandesha is what you're after - just hit a 1.0 version for axis2. 

http://ws.apache.org/sandesha/

HTH,
Robert
http://www.braziloutsource.com/On 5/10/06, kensky [EMAIL PROTECTED]
 wrote:Hie,In my application I want to provide high availability and fault tolerance of
web services deployed on axis2 and tomcat.Is it possible to have this featrue using Axis2 with Tomcat. if so how?Thanks and Regardskensky--View this message in context: 
http://www.nabble.com/-AXIS2-Replication-For-High-Availability-t1596410.html#a4331183Sent from the Axis - User forum at Nabble.com.

Re: Think I found a bug in wsdl2java handling reserved word Case - Where to go from here?

2006-05-10 Thread Dies Koper


Hello Joshua,

It is really a bug.
For element names that are reserved Java keywords (case, public, if, 
etc.) Axis should prefix the Java field names with underscores.
However, Case is not a reserved keyword: the class name should not get 
the underscore.

I have never seen this in the BugDB, I think you are the first to find it.

Where to go from here?: File a bug report:
http://issues.apache.org/jira/secure/CreateIssue!default.jspa

Regards,
Dies


[EMAIL PROTECTED] wrote:

All,

How can I get around this problem?  Axis is generating a class file named 
_case and using the instance name _case in my EligibilityProfile class. 
 Is there any way around this or is this really a bug?


Joshua




[EMAIL PROTECTED]

05/05/2006 10:44 PM
Please respond to axis-user

	   
To:axis-user@ws.apache.org
cc:
Subject:Think I found a bug in wsdl2java handling reserved word 
Case -Where to go from here?






Given the following simplified class:

public class EligibilityProfile {
   private mypackager.*Case* _case;
}


The WSDL file get created fine:

s0:complexType name=EligibilityProfile
   s0:complexContent
   s0:extension base=java:BaseDomainObject 
xmlns:java=java:mycompany.webservice.dto

   s0:sequence
   s0:element minOccurs=1 name=EligibilityProfileId 
nillable=true type=xs:long /
   s0:element minOccurs=1 name=Case nillable=true 
type=java:Case /

   /s0:sequence
   /s0:extension
   /s0:complexContent
/s0:complexType

When wsdl2java get run however, I get the following EligibilityProfile class 
created (Note the case of the _case class name):


public class EligibilityProfile {
   private mypackager.*_case* _case;
}

This class won't even compile.  If I refactor mypackager._class in the 
generated code to mypackager.Class it compiles, but I get a problem parsing a 
message:


   *org.xml.sax.SAXException: Invalid element in 
mycompany.webservice.dto.EligibilityProfile - case* *
   at 
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)* 
*
   at 
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)* 



How should I proceed?

Regards,

Joshua

Re: Use axis2 to call bpel

2006-05-10 Thread Deepal Jayasinghe

Hi Anne;

Can you please explain to me why do you use serviceGroupConetxtID?. If
this is the first request of given invocation , then no point of sending
that in fact you will be getting a SOAP fault as well. If the service is
deployed in SOAP session scope sever will send you the corresponding
servicegroup id , then you can send that from second message invocation
on ward.

Anne Thomas Manes wrote:

 What is the SOAPAction URI specified in the WSDL for initiateProcess
 operation? You should specify that URI in setAction method.

 Anne

 On 5/10/06, * nancy* [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED] wrote:

 Hi,
 I have not used that method. My code is:

 Public void invoke(){
 Options options = new Options();
 options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
 boolean exit = false;
 String serviceGroupContextId = null;
 EndpointReference EPR=new
 EndpointReference(webserviceURL);

 options.setTo(EPR);
 options.setTimeOutInMilliSeconds (5);

 ServiceClient serviceClient;
 serviceClient = new ServiceClient();
 serviceClient.setOptions(options);
 MessageContext requestMessageContext = new
 MessageContext();

 requestMessageContext.setEnvelope(getRequestEnvelope(messageName,
 parametersList,
 serviceGroupContextId));

 OperationClient opClient = serviceClient
 .createClient(
 ServiceClient.ANON_OUT_IN_OP);
 opClient.addMessageContext(requestMessageContext);
 opClient.setOptions(options);

 opClient.execute(true);
 }

 private SOAPEnvelope getRequestEnvelope(String operationName,
 HashMap param, String groupContextId) {
 String
 namespace1=http://services.oracle.com/bpel/Process;;

 SOAPFactory fac =
 OMAbstractFactory.getSOAP11Factory();
 SOAPEnvelope envelope = fac.getDefaultEnvelope();
 OMNamespace namespace = fac.createOMNamespace(

 namespace1, Process);

 OMElement params1 = fac.createOMElement(operationName,
 namespace);
 Set set=param.keySet();
 Iterator iter=set.iterator();

 while(iter.hasNext ()){
 String paramName=iter.next().toString();
 String
 paramValue=param.get(paramName).toString();
  OMElement paramOM =
 fac.createOMElement (paramName,namespace);
  paramOM.setText(paramValue);
  params1.addChild(paramOM);
 }
 envelope.getBody().setFirstChild(params1);


 return envelope;
 }

 Thanks
 Nancy

 -Original Message-
 From: Eran Chinthaka [mailto:[EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED]]
 Sent: Wednesday, May 10, 2006 2:34 PM
 To: axis-user@ws.apache.org mailto:axis-user@ws.apache.org
 Subject: Re: Use axis2 to call bpel

 Axis2 will never set a non-empty SOAPAction, if you have not called
 options.setAction(youraction).

 Are u sure you have not called that method.

 -- Chinthaka

 nancy wrote:
  Yah I understand that marking message with Urgent won't help in
 getting
  quick reply from others.Anyways,I want to send a SOAP Envelope
 in the way
  that I don't need to manipulate the requested parameter
 (OMELEMENT) there
 to
  get the parameters.
 
  I tried it but with no success. Exception is coming:
 
  Cannot find binding operation definition of soapAction
 '/orabpel' in
 
 http://daff06:9700/orabpel/default/ProcessManager/1.0/ProcessManager.wsdl
 
  My Request was:
 
 
  My request was:
 
  ?xml version='1.0' encoding='UTF-8'?
 
  soapenv:Envelope
  xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/
 http://schemas.xmlsoap.org/soap/envelope/soapenv:Header
 /
 
  soapenv:Body
 
  Process:initiateProcess
 
 xmlns:Process=http://services.oracle.com/bpel/Process
 http://services.oracle.com/bpel/ProcessProcess:primaryKeyV
 
 
 alue1/Process:primaryKeyValueProcess:businessProcessId1/Process:busine
 
 ssProcessId/Process:initiateProcess/soapenv:Body/soapenv:Envelope

 
 
  And my ProcessManager.wsdl has no defined SOAP BINDINGS.
 
  Is it necessary to define soap bindings with wsdl.
  Why axis2 is taking /orabpel as soapaction?
 
  Thanks
  Nancy
 
  -Original Message-
  From: Eran

Loosing bytes with MTOM

2006-05-10 Thread Patric Fornasier


Hi,

I'm sending a small png image from one server to another via MTOM. The
service and the client are both on the same machine.

The original size of the image is 6450 bytes. When the clients copies
the file to the file system however, the size of this copy is now 15083
bytes!

Funny enough, the received picture looks fine. It's just roughly 3 times
bigger.

Anybody got an idea what's going on here?

Here's the code for the server:
---
Image image = new ImageIO().loadImage(new FileInputStream(file));
DataSource dataSource = new ImageDataSource(image.png, image);
DataHandler dataHandler = new DataHandler(dataSource);
// create an optimized OMText node with the above DataHandler
OMText textData = factory.createOMText(dataHandler, true);
out.addChild(textData);

And for the client:
---
OMText out = (OMText) response.getFirstOMChild();   
DataHandler actualDH = (DataHandler) out.getDataHandler();
ImageIO io = new ImageIO();
Image img = io.loadImage(actualDH.getDataSource().getInputStream());
FileOutputStream imageOutStream = new
FileOutputStream(c:/dynamic-axis.png);
io.saveImage(image/png, img, imageOutStream);

Any hints are greatly appreciated!

Cheers,
patric

--
This email and any attachments may be confidential. They may contain legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment. This notice should not be removed.

Re: policy on web-methods!!!

2006-05-10 Thread Deepal Jayasinghe

Axis2 core dose not provide that facility , but by adding a handler you
can achieve the goal.

Wolfgang Schwarz wrote:

 Hi

 Is there any way in axis2 to impose restriction on webmethods i.e. who
 is allowed to access or make call to the particular method?

 Thanks
 schuller


-- 
Thanks,
Deepal

~Future is Open~

RE: Use axis2 to call bpel