Re: [axis2] Re: broken nightly build
Please report a JIRA .. Size of the nightly is less than 3MB which means lot of stuff are missing from it... ~Thilina On 3/14/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: The error arises when I hit http://localhost:8080/axis2. Any clue? Michele On Tue, 2007-03-13 at 18:10 +, Michele Mazzucco wrote: > Hi all, > > the last nightly build (13 mar 2007) is broken. > > org.apache.jasper.JasperException: Exception in > JSP: /axis2-web/index.jsp:23 > > 20: */ > 21: %> > 22: > 23: > 24: Axis 2 - Home > 25: > 26: > > > Stacktrace: > org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:506) > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377) > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > > root cause > > org.apache.jasper.JasperException > org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:512) > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:395) > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) > org.apache.jsp.axis2_002dweb.index_jsp._jspService(index_jsp.java:67) > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334) > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > > root cause > > java.lang.NullPointerException > org.apache.jsp.axis2_002dweb.include.httpbase_jsp.jspInit(httpbase_jsp.java:22) > org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:78) > org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:155) > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:317) > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) > org.apache.jsp.axis2_002dweb.index_jsp._jspService(index_jsp.java:67) > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334) > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis 2] problem running 3/16/2007 nightly build
Please check the size of your axis2.war.. If it's less than 10MB then it might be missing the axis2 dependency jars.. There was an similar issue some time back ... May be it has resurfaced again :(.. Yes.. You can try building from the source.. ~Thilina On 3/16/07, Tammy Dugan <[EMAIL PROTECTED]> wrote: I downloaded and expanded the war file. I went to localhost:8080/axis2/ to test the installation and got the following errors: org.apache.jasper.JasperException at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:207) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:240) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:187) at javax.servlet.http.HttpServlet.service(HttpServlet.java:809) ... ... ... *root cause* java.lang.NullPointerException at org.apache.jsp.httpbase_jsp.jspInit(httpbase_jsp.java:22) at org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:74) at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:110) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:147) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:240) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:187) at javax.servlet.http.HttpServlet.service(HttpServlet.java:809) I tried building the war from the binary distribution using ant and that war file resulted in the same error. Do I need to build from source? Tammy -- Tammy Dugan Computer Programmer Regenstrief Institute, Inc. 1050 Wishard Blvd., RG5 Indianapolis, IN 46202 (317) 630 - 7346 Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose. If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to deploy services without using axis2-web
Axis2 binary distribution comes together with a standalone simple
server, which you can use for testing purposes. The scripts
(axis2server.{sh|bat}) that can be used to start this server can be
found at the axis2Distro/bin folder...
Default startup of this uses the axis2Distro/repository as the
repository folder and the axis2Distor/conf/axis2.xml as the
axis2.xml...
Thilina
[1] http://ws.apache.org/axis2/1_1_1/installationguide.html#standalone
On 3/17/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
Josh,
if I will understand what you're asking, you'll need the war file. Once
the war file has been exploded (i.e. drop it into $CATALINA_HOME/webapps
and start tomcat), copy you services into
$CATALINA_HOME/webapps/axis2/WEB-INF/services.
Hope this helps,
Michele
On Fri, 2007-03-16 at 14:33 -0400, Josh wrote:
> Hello,
>
> I am looking for some instructions on how to develop/deploy services
> with out needing the axis2-web war. I have not found instructions on
> how to do this. Could someone point me in the right direction?
>
> Thanks,
>
> Josh
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Axis2: soap/jms question
I am trying to get an understanding of the soap/jms using the quickstart sample as a start and modifying it to try to run it as soap/jms. I am running Axis2 1.1.1 war on JBoss4.0.5 and am trying to use the messaging that comes with jboss as the jms implementation. I have followed the JMS transport doc (http://people.apache.org/~thilina/axis2/docs/jms-transport.html) and modified the services.xml of the stockquoteservice as follows ... jms class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/> class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> http://quickstart.samples/xsd"/> samples.quickstart.service.pojo.StockQuoteService queue/requestQ QueueConnectionFactory ... I have also modified axis2.xml with the relevant JBoss configurations: === ... org.jnp.interfaces.NamingContextFactory jnp://localhost:1099 ConnectionFactory .. === Firstly, once I deployed this I did not see any indication that the JMSListener has been started. I saw that there was an issue with starting of non-http transports for the embedded axis as described in https://issues.apache.org/jira/browse/AXIS2-1488, which is now resolved. Did this fix make it's way to the 1.1.1 version? If the above bug is still not resolved in the 1.1.1 version, are there any workarounds to start the JMSListener for an embedded axis2 instance? Secondly, once I deployed the service (stockquoteservice.aar), I obtained a strange WSDL from http://localhost:8080/axis2/services/StockQuoteService?wsdl. A part of the WSDL is shown below. Note that the transport is still http and the service ports are not generated. Note that in the services.xml I have specifically mentioned only the jms transport. So, why are the soap bindings still generated in the wsdl? Looks like a bug to me. === - + - - - Thirdly, the WSDL that the jms client will be using - do we need to generate is manually? I understand the jms destination URLwill need to be added manually to the stub, but I was hoping to get a partial WSDL generated. When I try to do a wsdl2java on the generated wsdl from the above service, it throws an NPE. Any pointers regarding the basic steps of running soap/jms on an embedded axis2 installation will be of great help. Thanks, Shantanu Sen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[AXIS 2] Namespace optimization
Does AXIS 2 support disabling/enabling namespace optimization ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axi2] Can't get MTOM attachments by reference to work
Are the MIME boundaries present? That is one way of telling whether or not MTOM
is being used.
Something like:
--MIME...---
all the data
MIME...---
If not, then MTOM is not being used. Then you can up the root logger to DEBUG
and see what it actually is, and where the axis conf is coming from. (I believe)
Roshan
From: Tammy Dugan [mailto:[EMAIL PROTECTED]
Sent: Fri 3/16/2007 1:26 PM
To: axis-user@ws.apache.org
Subject: [Axi2] Can't get MTOM attachments by reference to work
I use the following code to add attachments to an outgoing soap message:
//add an attachment if needed
if (this.attachmentContent != null)
{
for (int i = 0; i < this.attachmentContent.length; i++)
{
DataSource ds = new
ByteArrayDataSource(this.attachmentContent[i].toByteArray(),
this.attachmentContentType[i]);
OMText data = fac.createOMText(new DataHandler(ds), true);
OMElement parent = fac.createOMElement("pdf",null);
parent.addChild(data);
resp.addChild(parent); ;
}
}
I have the following test client that sends and receives a message from
a URLConnection:
charCnt = 0;
in = new BufferedReader( new InputStreamReader(
conn.getInputStream() ) );
out = new BufferedWriter( new FileWriter( OUTPUT_FILE ) );
while ( (response = in.readLine()) != null)
{
out.write( response );
out.write( "\n" );
charCnt += response.length();
}
in.close();
out.flush();
out.close();
When I look at the response output, the attachments in base64 encoded in
the body of the xml. I have true in axis2.xml and am not overriding it in
the services.xml file so why isn't the attachment being sent by
reference? Here is my services.xml file entry for the service I am testing:
org.regenstrief.queryposer.QueryStatisticsReturnServlet
Thanks,
Tammy Dugan
--
Tammy Dugan
Computer Programmer
Regenstrief Institute, Inc.
1050 Wishard Blvd., RG5
Indianapolis, IN 46202
(317) 630 - 7346
Confidentiality Notice: The contents of this message and any files transmitted
with it may contain confidential and/or privileged information and are intended
solely for the use of the named addressee(s). Additionally, the information
contained herein may have been disclosed to you from medical records with
confidentiality protected by federal and state laws. Federal regulations and
State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information
pertains or as otherwise permitted by such regulations. A general authorization
for the release of medical or other information is not sufficient for this
purpose.
If you have received this message in error, please notify the sender by return
e-mail and delete the original message. Any retention, disclosure, copying,
distribution or use of this information by anyone other than the intended
recipient is strictly prohibited.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<>-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] axiom exception
Hi all, sometimes I see this exception into the server logs org.apache.axiom.om.OMException at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:118) at org.apache.axiom.om.impl.llom.OMNodeImpl.build(OMNodeImpl.java:318) INFO [20:29:42,506] JmxQueueHandlerOne$AllocatorManager:run - Handler [Service2]: set new threshold to 20 at org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:632) at org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:599) at org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:117) at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:249) at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:202) at org.apache.axis2.client.ServiceClient.fillSOAPEnvelope(ServiceClient.java:584) at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:435) at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:414) but with no information. Any clue? Thanks, Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to deploy services without using axis2-web
Josh, if I will understand what you're asking, you'll need the war file. Once the war file has been exploded (i.e. drop it into $CATALINA_HOME/webapps and start tomcat), copy you services into $CATALINA_HOME/webapps/axis2/WEB-INF/services. Hope this helps, Michele On Fri, 2007-03-16 at 14:33 -0400, Josh wrote: > Hello, > > I am looking for some instructions on how to develop/deploy services > with out needing the axis2-web war. I have not found instructions on > how to do this. Could someone point me in the right direction? > > Thanks, > > Josh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
An unsupported token was provided (Problem with SKI information: Support for RSA key only)
Hello, As you can see I'm new to Axis2, with rampart to Encrypt a
Service.
I'm trying to use the Axis2, with rampart Im getting the following
error:
WSHandler: Signature: error during message
procesingorg.apache.ws.security.WSSecurityException: An unsupported
token was provided (Problem with SKI information: Support for RSA key
only) , does any one has a clue on it or a better way to generate a key
and/or Encrypt a Service?
This is a link to a sample im doing sample to Encrypt
(http://www-128.ibm.com/developerworks/edu/ws-dw-ws-understand-web-servi
ces4.html?S_TACT=105AGX52&S_CMP=cn-t-ws)
My key was generated as follows
keytool -genkey -keystore mykeys.jks -alias gene
--
C:\sign>keytool -genkey -keystore mykeys.jks -alias gene
Enter keystore password: password
What is your first and last name?
[Unknown]: Gene Telluride
What is the name of your organizational unit?
[Unknown]: Information technologies
What is the name of your organization?
[Unknown]: The Daily Moon
What is the name of your City or Locality?
[Unknown]: NY
What is the name of your State or Province?
[Unknown]: US
What is the two-letter country code for this unit?
[Unknown]: US
Is CN=Gene Telluride, OU=Information technologies, O=The Daily Moon,
L=NY, ST=US, C=US correct?
[no]: yes
Enter key password for
(RETURN if same as keystore password):password
--
The following is my security properties file:
org.apache.ws.security.crypto.provider=org.apache.ws.security.components
.crypto.Merlin
org.apache.ws.security.crypto.merlin.keystore.type=jks
org.apache.ws.security.crypto.merlin.keystore.password=password
org.apache.ws.security.crypto.merlin.file=mykeys.jks
This is part of my axis code Client code: (Axis2.xml)
Timestamp Signature
gene
PWCallback
security.properties
SKIKeyIdentifier
{Element}{http://docs.oasis-open.org/wss/2004/01/oasis-2
00401-wss-wssecurity-utility-1.0.xsd}Timestamp
Timestamp Signature Encrypt
gene
PWCallback
security.properties
SKIKeyIdentifier
SKIKeyIdentifier
gene
{Element}{http://schemas.xmlsoap.org/soap/envelope/}Body
//xenc:EncryptedData/xenc:CipherValue/xenc:CipherData
Server: (Services.xml)
Timestamp Signature
PWCallback
security.properties
Timestamp Signature Encrypt
gene
PWCallback
security.properties
SKIKeyIdentifier
SKIKeyIdentifier
bob
{Element}{http://schemas.xmlsoap.org/soap/envelope/}Body
//xenc:EncryptedData/xenc:CipherValue/xenc:CipherData
question on wsdl2java generated client
Hi,
I met the following error while compiling client code generated from
wsdl2java,
[javac] \client\StopServiceStub.java:26070: getClass() in
cient.StopServiceStub.Class31 cannot override getClass() in
java.lang.Object; overridden method is final
[javac] public Class getClass(){
[javac] ^
It seems to be the same described in this post:
http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=next_topic
&f=51&t=004144&go=older
Any suggestions are appreciated!
eric
RE: [AXIS2] Codegen question regarding "local"
Thanks Amila. I appreciate your trying this out. Could you tell me what
the parameters you used to run wsdl2java? I downloaded the SNAPSHOT and
tried it but I am still getting AXIS2 errors (Unsupported content Simple
Type List...). It would be great for me to get this working. (-:
_
From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 15, 2007 11:30 PM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: [AXIS2] Codegen question regarding "local"
I generated the code with wsdl2java in axis2 trunk. So if you use the
wsdl2java tool in an axis2 nightly build you should be able to generate the
code correctly.
Eclipse plugin uses the Axis2 1.1.1 jars. So you can get a axis2 SNAPSHOT
nightly build and use those jars by editing the plugin.xml file and putting
them to plugin lib folder.
On 3/16/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Carlos,
Please log a JIRA bug so that we can track and ensure that the bug is
fixed before the next release.
thanks,
dims
On 3/15/07, Carlos S. Zamudio <[EMAIL PROTECTED]> wrote:
> Sure. It's the Search WSDL located at:
> http://soap.search.msn.com/webservices.asmx?wsdl. There have already been
> posting on some modifications to the WSDL that needs to be performed to
make
> it work under AXIS2, and after removing some of the offending SimpleTypes,
> it went through the generation process (don't know why AXIS didn't like
some
> of these types, but I tried Xfire as well and it too didn't like them -
> prefer to use AXIS for this).
>
> An example of accessing the unresolved variable:
>
> /**
>* databinding method to get an XML representation of this object
>*
>*/
>public javax.xml.stream.XMLStreamReader
> getPullParser(javax.xml.namespace.QName qName){
>
>
>
>
> //We can safely assume an element has only one type
> associated with it
> return new
> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl(MY_QNAME,
> new java.lang.Object[]{
>
> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReader.ELEMENT_TEXT
,
>
> org.apache.axis2.databinding.utils.ConverterUtil.convertToString(local)
> },
> null);
>
> }
>
>
> -Original Message-
> From: Ajith Ranabahu [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 15, 2007 12:06 PM
> To: axis-user@ws.apache.org
> Subject: Re: [AXIS2] Codegen question regarding "local"
>
> Hi,
> Is it possible to post the WSDL ?
>
> On 3/15/07, Carlos S. Zamudio <
[EMAIL PROTECTED]> wrote:
> >
> >
> > Hi,
> > I'm using the AXIS2 codegen Eclipse plugin to generate the Java
> > classes for a WSDL I am attempting to use. When I generate the
> > classes, and integrate them into my Eclipse project, I find a variable
> > called "local" that does not get resolved. It's not clear from the
> > code what to do about this. This must be obvious, but anyone interested
> in giving me a clue? Thanks.
> > Carlos S. Zamudio
>
>
> --
> Ajith Ranabahu
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Amila Suriarachchi,
WSO2 Inc.
WSDL URL for AXIS2 codegenerator
Is it possible to provide a WSDL URL to the AXIS2 code generator? I would like to generate a client (only) for a remote webservice. I have tried it unsuccessfully both in the Eclipse plugin version as well as the ANT version and I get "unexpected error occurred". Not sure if I missed some configuration step. It works from a local file though. -Srinivas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to deploy services without using axis2-web
Hello, I am looking for some instructions on how to develop/deploy services with out needing the axis2-web war. I have not found instructions on how to do this. Could someone point me in the right direction? Thanks, Josh
[Axis 2] problem running 3/16/2007 nightly build
I downloaded and expanded the war file. I went to localhost:8080/axis2/ to test the installation and got the following errors: org.apache.jasper.JasperException at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:207) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:240) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:187) at javax.servlet.http.HttpServlet.service(HttpServlet.java:809) ... ... ... *root cause* java.lang.NullPointerException at org.apache.jsp.httpbase_jsp.jspInit(httpbase_jsp.java:22) at org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:74) at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:110) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:147) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:240) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:187) at javax.servlet.http.HttpServlet.service(HttpServlet.java:809) I tried building the war from the binary distribution using ant and that war file resulted in the same error. Do I need to build from source? Tammy -- Tammy Dugan Computer Programmer Regenstrief Institute, Inc. 1050 Wishard Blvd., RG5 Indianapolis, IN 46202 (317) 630 - 7346 Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose. If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis 1.4 client get cookies
I believe that I've finally cracked this though I am highly suspicious of its
complexity -- you'd think that it would be trivial retrieving a cookie, and
maybe it is but how you do it is not at all obvious.
Here's what I did:
MyServiceLocator locator = new MyServiceLocator();
locator.setMaintainSession(true);
MyService service = locator.getMyService();
service.login("fred", "fredpass"); // server sends me some cookies here
// I want to get those cookies here
MessageContext ctx = locator.getCall().getMessageContext();
Message rsp = ctx.getResponseMessage();
MimeHeaders mhd = rsp.getMimeHeaders();
String [] cookies = mhd.getHeader("set-cookie");
if (cookies != null)
{
// parse value of JSESSIONID from cookies[0]
}
service.dosomethingelse();
service.logout();
jarmod wrote:
>
> I've read about 14 million internet posts (OK, it was just 13 million) on
> the topic of how an Axis (1.4 in this case) client might retrieve cookies
> and, quite surprisingly, I have yet to find a solution that actually
> works.
>
> My Axis client uses the highest-level abstraction so looks something like
> this:
>
> MyServiceLocator locator = new MyServiceLocator();
> locator.setMaintainSession(true);
> MyService service = locator.getMyService();
>
> service.login("fred", "fredpass"); // server sends me some cookies here
> // I want to get those cookies here
> service.dosomethingelse();
> service.logout();
>
> The code works fine and uses JSESSIONID cookie-based session management
> automatically. However, I want more thanthat -- I want to be able to
> retrieve the cookies in the HTTP response associated with the login.
>
> I've tried to retrieve the cookies using
> stub._getProperty(HTTPConstants.HEADER_COOKIE) but that returns NULL.
> I've also enumerated all properties of the stub *after* the login call and
> there are none. Can you even do what I want at this interface level?
>
> Appreciate any help.
>
--
View this message in context:
http://www.nabble.com/Axis-1.4-client-get-cookies-tf3409630.html#a9519062
Sent from the Axis - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axi2] Can't get MTOM attachments by reference to work
I use the following code to add attachments to an outgoing soap message:
//add an attachment if needed
if (this.attachmentContent != null)
{
for (int i = 0; i < this.attachmentContent.length; i++)
{
DataSource ds = new
ByteArrayDataSource(this.attachmentContent[i].toByteArray(),
this.attachmentContentType[i]);
OMText data = fac.createOMText(new DataHandler(ds), true);
OMElement parent = fac.createOMElement("pdf",null);
parent.addChild(data);
resp.addChild(parent); ;
}
}
I have the following test client that sends and receives a message from
a URLConnection:
charCnt = 0;
in = new BufferedReader( new InputStreamReader(
conn.getInputStream() ) );
out = new BufferedWriter( new FileWriter( OUTPUT_FILE ) );
while ( (response = in.readLine()) != null)
{
out.write( response );
out.write( "\n" );
charCnt += response.length();
}
in.close();
out.flush();
out.close();
When I look at the response output, the attachments in base64 encoded in
the body of the xml. I have locked="false">true in axis2.xml and am not overriding it in
the services.xml file so why isn't the attachment being sent by
reference? Here is my services.xml file entry for the service I am testing:
name="ServiceClass">org.regenstrief.queryposer.QueryStatisticsReturnServlet
class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
Thanks,
Tammy Dugan
--
Tammy Dugan
Computer Programmer
Regenstrief Institute, Inc.
1050 Wishard Blvd., RG5
Indianapolis, IN 46202
(317) 630 - 7346
Confidentiality Notice: The contents of this message and any files transmitted
with it may contain confidential and/or privileged information and are intended
solely for the use of the named addressee(s). Additionally, the information
contained herein may have been disclosed to you from medical records with
confidentiality protected by federal and state laws. Federal regulations and
State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information
pertains or as otherwise permitted by such regulations. A general authorization
for the release of medical or other information is not sufficient for this
purpose.
If you have received this message in error, please notify the sender by return
e-mail and delete the original message. Any retention, disclosure, copying,
distribution or use of this information by anyone other than the intended
recipient is strictly prohibited.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Embedding XML into SOAP
h I don't see anything obviously wrong in what you are doing. Have you tried upping your log4j debug level. Paul On 3/16/07, Rich Adili <[EMAIL PROTECTED]> wrote: OKEEDOKEE. http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:tns="http://www.xatanet.net/XataNetWebService/DispatchImportServic e" xmlns:s="http://www.w3.org/2001/XMLSchema"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; targetNamespace="http://www.xatanet.net/XataNetWebService/DispatchImport Service" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> http://www.xatanet.net/XataNetWebService/DispatchImport Service"> http://schemas.xmlsoap.org/wsdl/";>Adds a single trip plan to the XataNet system.
The input parameter, plan, must be an XmlDocument conforming to the XataNet TripPlan.xsd
http://schemas.xmlsoap.org/soap/http"; /> http://www.xatanet.net/XataNetWebService/DispatchImportServi ce/ImportTripPlan" style="document" /> http://schemas.xmlsoap.org/soap/http"; /> http://www.xatanet.net/XataNetWebService/DispatchImportServi ce/ImportTripPlan" style="document" /> http://alpha.xata.com/xatanetwebservice/DispatchImportService. asmx" /> http://alpha.xata.com/xatanetwebservice/DispatchImportService. asmx" /> -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Friday, March 16, 2007 11:38 AM To: axis-user@ws.apache.org Subject: Re: Embedding XML into SOAP Rich Can you let us see the WSDL? I don't understand the usecase. Paul On 3/16/07, Rich Adili <[EMAIL PROTECTED]> wrote: > Thanks for the suggestions, Paul. I tried the nodatabinding approach and > it got me past my original problem. Unfortunately, both suggested > approaches return an OMElement and I have 48 web methods to implement. > I'm not keen on writing that much unwrapping code. > > So, can someone tell me what I did wrong in the first place? > > -Original Message- > From: Paul Fremantle [mailto:[EMAIL PROTECTED] > Sent: Friday, March 16, 2007 8:57 AM > To: axis-user@ws.apache.org > Subject: Re: Embedding XML into SOAP > > Rich > > Is the XML the whole of the SOAP body? Because its much simpler to use > the ServiceClient API which takes an OMElement directly. > > ServiceClient sc = new ServiceClient(url); > // if the service needs an action: > sc.getOptions().setAction("http://whatever";); > OMElement response = sc.sendReceive(omElement); > > The other option is to generate the stub using the nodatabinding > approach which will mean you don't have all those classes. > > Try wsdl2java -d none > > Paul > > On 3/16/07, Rich Adili <[EMAIL PROTECTED]> wrote: > > > > > > > > I'm writing a client for a service that takes an XML document as > input. I'm > > using WSDL2Java-generated code for my client. The generated code wants > an > > OMElement for the XML data. This snippet attempts to supply that. > Clearly, > > it ain't right as the send throws an exception. What am I doing wrong? > > > > > > > > public void testme(final InputStream xmlStream) throws > Exception > > > > { > > > > DispatchImportServiceStub stub = new > > DispatchImportServiceStub(); > > > > DispatchImportServiceStub.ImportTripPlan > > dataObject = > > > > new > > DispatchImportServiceStub.ImportTripPlan(); > > > > DispatchImportServiceStub.Plan_type0 Plan = > > new DispatchImportServiceStub.Plan_type0(); > > > > XMLStreamReader parser = > > XMLInputFactory.newInstance().createXMLStreamReader(xmlStream); > > > > StAXOMBuilder builder = new StAXOMBuilder(parser); > > > > OMElement documentElement = > builder.getDocumentElement(); > > > > Plan.setExtraElement(documentElement); > > > > dataObject.setPlan(Plan); > > > > stub.ImportTripPlan(dataObject); > > > > } > > > > > > > > org.apache.axis2.AxisFault: Error in extracting message properties; > nested > > exception is: > > > > org.apache.rampart.RampartException: Error in > > extracting message properties > > > > at > > org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65) > > > > at > > org.apache.axis2.
RE: Embedding XML into SOAP
OKEEDOKEE. http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:tns="http://www.xatanet.net/XataNetWebService/DispatchImportServic e" xmlns:s="http://www.w3.org/2001/XMLSchema"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; targetNamespace="http://www.xatanet.net/XataNetWebService/DispatchImport Service" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> http://www.xatanet.net/XataNetWebService/DispatchImport Service"> http://schemas.xmlsoap.org/wsdl/";>Adds a single trip plan to the XataNet system.
The input parameter, plan, must be an XmlDocument conforming to the XataNet TripPlan.xsd
http://schemas.xmlsoap.org/soap/http"; /> http://www.xatanet.net/XataNetWebService/DispatchImportServi ce/ImportTripPlan" style="document" /> http://schemas.xmlsoap.org/soap/http"; /> http://www.xatanet.net/XataNetWebService/DispatchImportServi ce/ImportTripPlan" style="document" /> http://alpha.xata.com/xatanetwebservice/DispatchImportService. asmx" /> http://alpha.xata.com/xatanetwebservice/DispatchImportService. asmx" /> -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Friday, March 16, 2007 11:38 AM To: axis-user@ws.apache.org Subject: Re: Embedding XML into SOAP Rich Can you let us see the WSDL? I don't understand the usecase. Paul On 3/16/07, Rich Adili <[EMAIL PROTECTED]> wrote: > Thanks for the suggestions, Paul. I tried the nodatabinding approach and > it got me past my original problem. Unfortunately, both suggested > approaches return an OMElement and I have 48 web methods to implement. > I'm not keen on writing that much unwrapping code. > > So, can someone tell me what I did wrong in the first place? > > -Original Message- > From: Paul Fremantle [mailto:[EMAIL PROTECTED] > Sent: Friday, March 16, 2007 8:57 AM > To: axis-user@ws.apache.org > Subject: Re: Embedding XML into SOAP > > Rich > > Is the XML the whole of the SOAP body? Because its much simpler to use > the ServiceClient API which takes an OMElement directly. > > ServiceClient sc = new ServiceClient(url); > // if the service needs an action: > sc.getOptions().setAction("http://whatever";); > OMElement response = sc.sendReceive(omElement); > > The other option is to generate the stub using the nodatabinding > approach which will mean you don't have all those classes. > > Try wsdl2java -d none > > Paul > > On 3/16/07, Rich Adili <[EMAIL PROTECTED]> wrote: > > > > > > > > I'm writing a client for a service that takes an XML document as > input. I'm > > using WSDL2Java-generated code for my client. The generated code wants > an > > OMElement for the XML data. This snippet attempts to supply that. > Clearly, > > it ain't right as the send throws an exception. What am I doing wrong? > > > > > > > > public void testme(final InputStream xmlStream) throws > Exception > > > > { > > > > DispatchImportServiceStub stub = new > > DispatchImportServiceStub(); > > > > DispatchImportServiceStub.ImportTripPlan > > dataObject = > > > > new > > DispatchImportServiceStub.ImportTripPlan(); > > > > DispatchImportServiceStub.Plan_type0 Plan = > > new DispatchImportServiceStub.Plan_type0(); > > > > XMLStreamReader parser = > > XMLInputFactory.newInstance().createXMLStreamReader(xmlStream); > > > > StAXOMBuilder builder = new StAXOMBuilder(parser); > > > > OMElement documentElement = > builder.getDocumentElement(); > > > > Plan.setExtraElement(documentElement); > > > > dataObject.setPlan(Plan); > > > > stub.ImportTripPlan(dataObject); > > > > } > > > > > > > > org.apache.axis2.AxisFault: Error in extracting message properties; > nested > > exception is: > > > > org.apache.rampart.RampartException: Error in > > extracting message properties > > > > at > > org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65) > > > > at > > org.apache.axis2.engine.Phase.invoke(Phase.java:382) > > > > at > > org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:522) > > > > at > > org.apache.axis2.engine.Ax
Re: Minimal Axis2 JARs for simple RPC client
- xbean-2.2.0.jar is not needed. - axis2-tools-1.1.1.jar is not needed at runtime - axis2-codegen-1.1.1.jar is not needed at runtime - axis2-adb-codegen-1.1.1.jar is not needed at runtime - try taking out mail jar (not sure) thanks, dims On 3/16/07, Marc Nädele <[EMAIL PROTECTED]> wrote: I have a very simple RPC client which uses Axis2 to access an Axis2 WS (it is similar to the POJO RPC client example in the Axis2 documentation). My main problem now is that the client should have a very small footprint. So just including all Axis2 JARs is not an option. I have already searched the Archiv and the Web and found some discussions (like "[axis2] jars for ADB client" in this mailing list) on the minimal footprint of Axis2 for some client configurations. Client VM is SUN 1.4.2. I was already been able to strip down the JARs using the information I found. But I don't know if I can further reduce them: XmlSchema-1.2.jar activation-1.1.jar annogen-0.1.0.jar axiom-api-1.2.2.jar axiom-impl-1.2.2.jar axis2-adb-1.1.1.jar axis2-adb-codegen-1.1.1.jar axis2-codegen-1.1.1.jar axis2-java2wsdl-1.1.1.jar axis2-kernel-1.1.1.jar axis2-tools-1.1.1.jar backport-util-concurrent-2.2.jar commons-codec-1.3.jar commons-httpclient-3.0.1.jar commons-logging-1.1.jar mail-1.4.jar neethi-2.0.jar stax-api-1.0.1.jar wsdl4j-1.6.2.jar wstx-asl-3.2.0.jar xbean-2.2.0.jar Does anyone have information which JARs are needed for a simple RPC client like the POJO RPC client from the Axis2 docs? _ Haben Spinnen Ohren? Finden Sie es heraus – mit dem MSN Suche Superquiz via http://www.msn-superquiz.de Jetzt mitmachen und gewinnen! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Embedding XML into SOAP
Rich
Can you let us see the WSDL? I don't understand the usecase.
Paul
On 3/16/07, Rich Adili <[EMAIL PROTECTED]> wrote:
Thanks for the suggestions, Paul. I tried the nodatabinding approach and
it got me past my original problem. Unfortunately, both suggested
approaches return an OMElement and I have 48 web methods to implement.
I'm not keen on writing that much unwrapping code.
So, can someone tell me what I did wrong in the first place?
-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED]
Sent: Friday, March 16, 2007 8:57 AM
To: axis-user@ws.apache.org
Subject: Re: Embedding XML into SOAP
Rich
Is the XML the whole of the SOAP body? Because its much simpler to use
the ServiceClient API which takes an OMElement directly.
ServiceClient sc = new ServiceClient(url);
// if the service needs an action:
sc.getOptions().setAction("http://whatever";);
OMElement response = sc.sendReceive(omElement);
The other option is to generate the stub using the nodatabinding
approach which will mean you don't have all those classes.
Try wsdl2java -d none
Paul
On 3/16/07, Rich Adili <[EMAIL PROTECTED]> wrote:
>
>
>
> I'm writing a client for a service that takes an XML document as
input. I'm
> using WSDL2Java-generated code for my client. The generated code wants
an
> OMElement for the XML data. This snippet attempts to supply that.
Clearly,
> it ain't right as the send throws an exception. What am I doing wrong?
>
>
>
> public void testme(final InputStream xmlStream) throws
Exception
>
> {
>
> DispatchImportServiceStub stub = new
> DispatchImportServiceStub();
>
> DispatchImportServiceStub.ImportTripPlan
> dataObject =
>
> new
> DispatchImportServiceStub.ImportTripPlan();
>
> DispatchImportServiceStub.Plan_type0 Plan =
> new DispatchImportServiceStub.Plan_type0();
>
> XMLStreamReader parser =
> XMLInputFactory.newInstance().createXMLStreamReader(xmlStream);
>
> StAXOMBuilder builder = new StAXOMBuilder(parser);
>
> OMElement documentElement =
builder.getDocumentElement();
>
> Plan.setExtraElement(documentElement);
>
> dataObject.setPlan(Plan);
>
> stub.ImportTripPlan(dataObject);
>
> }
>
>
>
> org.apache.axis2.AxisFault: Error in extracting message properties;
nested
> exception is:
>
> org.apache.rampart.RampartException: Error in
> extracting message properties
>
> at
> org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
>
> at
> org.apache.axis2.engine.Phase.invoke(Phase.java:382)
>
> at
> org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:522)
>
> at
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:655)
>
> at
>
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:237)
>
> at
>
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:202)
>
> at
>
net.xatanet.axisstubs.DispatchImportServiceStub.ImportTripPlan(DispatchI
mportServiceStub.java:141)
>
> at
>
net.xatanet.services.DispatchImportService.ImportTripPlan(DispatchImport
Service.java:82)
>
> at test.TestImportTripPlan.run(TestImportTripPlan.java:33)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
>
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:597)
>
> at test.GUI$2$1.run(GUI.java:97)
>
> at java.lang.Thread.run(Thread.java:619)
>
> Caused by: org.apache.rampart.RampartException: Error in
> extracting message properties
>
> at
>
org.apache.rampart.RampartMessageData.(RampartMessageData.java:294
)
>
> at
> org.apache.rampart.MessageBuilder.build(MessageBuilder.java:56)
>
> at
> org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:59)
>
> ... 14 more
>
> Caused by: org.apache.ws.security.WSSecurityException:
> Error in converting SOAP Envelope to Document; nested exception is:
>
> org.apache.axiom.om.OMException:
> javax.xml.stream.XMLStreamException:
> org.apache.axiom.om.OMException: Parser has already reached end of the
> document. No siblings found
>
> at
>
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.
java:121)
>
> at
>
org.apache.rampart.RampartMessageData.(RampartMessageData.java:146
)
>
> ... 16 more
>
> Caused by: org.apache.axiom.om.OMException:
> javax.xml.stream.XMLStreamException:
> org.apache.axiom.om.OMException: Parser has already reached end of the
> document. No siblings found
>
> at
>
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:1
99)
>
> at
> org.apach
[Axis2 & Rampart] Working combination ...anyone? URGENT
Hi everybody, does anybody use Axis2 with ADB, MTOM and Rampart 1.1? It seems like I am really stuck here: - after getting Rampart 1.1 to work with Axis2 1.1.1, I had to face an "unexpected subelement xyz" error that was noted to be fixed in one of the recent nightly builds of Axis2. - but using a recent nightly build (from 03/13/07 on to 03/15/07), Rampart 1.1 does not work anymore. Find the error attached below. The unexpected subelement error turned up with Axis2 1.1.1, when I tried to submit some binary data (xmime:Base64Binary) from the client to the server. This used to work fine with the nightly builds, but in combination with Rampart - it doesn't. Doing some research I only found this mail: http://marc.theaimsgroup.com/?l=axis-user&m=117211779120993&w=2 I checked the WSDL-file and the request for errors described in the post, without success. Is there a way to get Rampart to work with a recent version of Axis2? Otherwise: is there a way to merge only the recent changes in ADB into the source code of Axis2 1.1.1 to get a working version? I will greatly appreciate your help! Sven Error when engaging module Rampart 1.1: -- java.lang.AbstractMethodError: org.apache.rampart.handler.WSDoAllSender.flowComplete(Lorg/apache/axis2/cont ext/MessageContext;)V at org.apache.axis2.engine.Phase.flowComplete(Phase.java:428) at org.apache.axis2.engine.AxisEngine.flowComplete(AxisEngine.java:281) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:495) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperatio n.java:331) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOpera tion.java:295) at herbie.core.desktop.handler.HerbieWSStub.getHome(HerbieWSStub.java:1905) at herbie.core.handler.HomeHandler.receiveHome(HomeHandler.java:39) at herbie.views.HomeView.fill(HomeView.java:203) at herbie.views.HomeView.createPartControl(HomeView.java:195) at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:33 2) at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:197) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReferenc e.java:566) at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290) at org.eclipse.ui.internal.ViewPane.setVisible(ViewPane.java:525) at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(Presentable Part.java:140) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(Pres entablePartFolder.java:268) at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftTo RightTabOrder.java:65) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPar t(TabbedStackPresentation.java:394) at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.jav a:1144) at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1097) at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1311) at org.eclipse.ui.internal.PartStack.createControl(PartStack.java:601) at org.eclipse.ui.internal.PartStack.createControl(PartStack.java:532) at org.eclipse.ui.internal.PartSashContainer.createControl(PartSashContainer.ja va:562) at org.eclipse.ui.internal.PerspectiveHelper.activate(PerspectiveHelper.java:24 4) at org.eclipse.ui.internal.Perspective.onActivate(Perspective.java:815) at org.eclipse.ui.internal.WorkbenchPage.onActivate(WorkbenchPage.java:2436) at org.eclipse.ui.internal.WorkbenchWindow$6.run(WorkbenchWindow.java:2616) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ui.internal.WorkbenchWindow.setActivePage(WorkbenchWindow.java:2 597) at org.eclipse.ui.internal.WorkbenchWindow.busyOpenPage(WorkbenchWindow.java:65 8) at org.eclipse.ui.internal.Workbench.busyOpenWorkbenchWindow(Workbench.java:795 ) at org.eclipse.ui.internal.Workbench.doOpenFirstTimeWindow(Workbench.java:1437) at org.eclipse.ui.internal.Workbench.access$10(Workbench.java:1435) at org.eclipse.ui.internal.Workbench$16.run(Workbench.java:1399) at org.eclipse.ui.internal.Workbench.runStartupWithProgress(Workbench.java:1421 ) at org.eclipse.ui.internal.Workbench.openFirstTimeWindow(Workbench.java:1397) at org.eclipse.ui.internal.WorkbenchConfigurer.openFirstTimeWindow(WorkbenchCon figurer.java:190) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.jav a:708) at org.eclipse.ui.internal.Workbench.init(Workbench.java:1085) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1847) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.cr
Minimal Axis2 JARs for simple RPC client
I have a very simple RPC client which uses Axis2 to access an Axis2 WS (it is similar to the POJO RPC client example in the Axis2 documentation). My main problem now is that the client should have a very small footprint. So just including all Axis2 JARs is not an option. I have already searched the Archiv and the Web and found some discussions (like "[axis2] jars for ADB client" in this mailing list) on the minimal footprint of Axis2 for some client configurations. Client VM is SUN 1.4.2. I was already been able to strip down the JARs using the information I found. But I don't know if I can further reduce them: XmlSchema-1.2.jar activation-1.1.jar annogen-0.1.0.jar axiom-api-1.2.2.jar axiom-impl-1.2.2.jar axis2-adb-1.1.1.jar axis2-adb-codegen-1.1.1.jar axis2-codegen-1.1.1.jar axis2-java2wsdl-1.1.1.jar axis2-kernel-1.1.1.jar axis2-tools-1.1.1.jar backport-util-concurrent-2.2.jar commons-codec-1.3.jar commons-httpclient-3.0.1.jar commons-logging-1.1.jar mail-1.4.jar neethi-2.0.jar stax-api-1.0.1.jar wsdl4j-1.6.2.jar wstx-asl-3.2.0.jar xbean-2.2.0.jar Does anyone have information which JARs are needed for a simple RPC client like the POJO RPC client from the Axis2 docs? _ Haben Spinnen Ohren? Finden Sie es heraus mit dem MSN Suche Superquiz via http://www.msn-superquiz.de Jetzt mitmachen und gewinnen! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2 1.1.1] [AXIS1.4] HTTP Get/post binding support.
Giuseppe, There is not much support in those versions. Please try latest nightly. thanks, dims On 3/16/07, Giuseppe Sarno <[EMAIL PROTECTED]> wrote: Hi, What is the level of support for those binding in Axis and Axis 2 ? I have a wsdl which I'm compiling using both libraries. Axis pars it but fails on a wsdl:fault . [wsdl2java] java.io.IOException: ERROR: Missing element inFault "FaultName" in operation "FaultName", in binding requestInfo [wsdl2java] at org.apache.axis.wsdl.symbolTable.SymbolTable.faultsFromSOAPFault(SymbolT able.java:2858) [wsdl2java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populateBindings(SymbolTabl e.java:2549) [wsdl2java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:7 44) [wsdl2java] at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543) [wsdl2java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:5 18) [wsdl2java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:4 95) [wsdl2java] at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) [wsdl2java] at java.lang.Thread.run(Thread.java:595) It fails at the wsdl:fault but as you can see it is not a soap:fault Axis 2 seem to parse them but if a change details (to make them wrong) it doesn't seem to bother. Regards. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Embedding XML into SOAP
Thanks for the suggestions, Paul. I tried the nodatabinding approach and
it got me past my original problem. Unfortunately, both suggested
approaches return an OMElement and I have 48 web methods to implement.
I'm not keen on writing that much unwrapping code.
So, can someone tell me what I did wrong in the first place?
-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED]
Sent: Friday, March 16, 2007 8:57 AM
To: axis-user@ws.apache.org
Subject: Re: Embedding XML into SOAP
Rich
Is the XML the whole of the SOAP body? Because its much simpler to use
the ServiceClient API which takes an OMElement directly.
ServiceClient sc = new ServiceClient(url);
// if the service needs an action:
sc.getOptions().setAction("http://whatever";);
OMElement response = sc.sendReceive(omElement);
The other option is to generate the stub using the nodatabinding
approach which will mean you don't have all those classes.
Try wsdl2java -d none
Paul
On 3/16/07, Rich Adili <[EMAIL PROTECTED]> wrote:
>
>
>
> I'm writing a client for a service that takes an XML document as
input. I'm
> using WSDL2Java-generated code for my client. The generated code wants
an
> OMElement for the XML data. This snippet attempts to supply that.
Clearly,
> it ain't right as the send throws an exception. What am I doing wrong?
>
>
>
> public void testme(final InputStream xmlStream) throws
Exception
>
> {
>
> DispatchImportServiceStub stub = new
> DispatchImportServiceStub();
>
> DispatchImportServiceStub.ImportTripPlan
> dataObject =
>
> new
> DispatchImportServiceStub.ImportTripPlan();
>
> DispatchImportServiceStub.Plan_type0 Plan =
> new DispatchImportServiceStub.Plan_type0();
>
> XMLStreamReader parser =
> XMLInputFactory.newInstance().createXMLStreamReader(xmlStream);
>
> StAXOMBuilder builder = new StAXOMBuilder(parser);
>
> OMElement documentElement =
builder.getDocumentElement();
>
> Plan.setExtraElement(documentElement);
>
> dataObject.setPlan(Plan);
>
> stub.ImportTripPlan(dataObject);
>
> }
>
>
>
> org.apache.axis2.AxisFault: Error in extracting message properties;
nested
> exception is:
>
> org.apache.rampart.RampartException: Error in
> extracting message properties
>
> at
> org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
>
> at
> org.apache.axis2.engine.Phase.invoke(Phase.java:382)
>
> at
> org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:522)
>
> at
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:655)
>
> at
>
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:237)
>
> at
>
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:202)
>
> at
>
net.xatanet.axisstubs.DispatchImportServiceStub.ImportTripPlan(DispatchI
mportServiceStub.java:141)
>
> at
>
net.xatanet.services.DispatchImportService.ImportTripPlan(DispatchImport
Service.java:82)
>
> at test.TestImportTripPlan.run(TestImportTripPlan.java:33)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
>
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:597)
>
> at test.GUI$2$1.run(GUI.java:97)
>
> at java.lang.Thread.run(Thread.java:619)
>
> Caused by: org.apache.rampart.RampartException: Error in
> extracting message properties
>
> at
>
org.apache.rampart.RampartMessageData.(RampartMessageData.java:294
)
>
> at
> org.apache.rampart.MessageBuilder.build(MessageBuilder.java:56)
>
> at
> org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:59)
>
> ... 14 more
>
> Caused by: org.apache.ws.security.WSSecurityException:
> Error in converting SOAP Envelope to Document; nested exception is:
>
> org.apache.axiom.om.OMException:
> javax.xml.stream.XMLStreamException:
> org.apache.axiom.om.OMException: Parser has already reached end of the
> document. No siblings found
>
> at
>
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.
java:121)
>
> at
>
org.apache.rampart.RampartMessageData.(RampartMessageData.java:146
)
>
> ... 16 more
>
> Caused by: org.apache.axiom.om.OMException:
> javax.xml.stream.XMLStreamException:
> org.apache.axiom.om.OMException: Parser has already reached end of the
> document. No siblings found
>
> at
>
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:1
99)
>
> at
> org.apache.axiom.om.impl.dom.NodeImpl.build(NodeImpl.java:469)
>
> at
> org.apache.axiom.om.impl.dom.DocumentImpl.build(Docume
[AXIS2 1.1.1] [AXIS1.4] HTTP Get/post binding support.
Hi, What is the level of support for those binding in Axis and Axis 2 ? I have a wsdl which I'm compiling using both libraries. Axis pars it but fails on a wsdl:fault . [wsdl2java] java.io.IOException: ERROR: Missing element inFault "FaultName" in operation "FaultName", in binding requestInfo [wsdl2java] at org.apache.axis.wsdl.symbolTable.SymbolTable.faultsFromSOAPFault(SymbolT able.java:2858) [wsdl2java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populateBindings(SymbolTabl e.java:2549) [wsdl2java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:7 44) [wsdl2java] at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543) [wsdl2java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:5 18) [wsdl2java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:4 95) [wsdl2java] at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) [wsdl2java] at java.lang.Thread.run(Thread.java:595) It fails at the wsdl:fault but as you can see it is not a soap:fault Axis 2 seem to parse them but if a change details (to make them wrong) it doesn't seem to bother. Regards. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd
in META-INF/TestService.wsdl: targetNamespace="uk:ac:ox:oucs:ask:repo:ws:collectionmanager" xmlns:rt="uk:ac:ox:oucs:ask:repo:ws:types" axis2-admin listing the service: targetNamespace="http://collectionmanager.ws.repo.ask.oucs.ox.ac.uk"; and xmlns:rt has been removed xmlns:rt has been imported from an external xsd into the wsdl all these changes cause the service to break. How can I stop Axis2 rewriting the wsdl? thanks, Alistair -- mov eax,1 mov ebx,0 int 80h
Re: Embedding XML into SOAP
Rich
Is the XML the whole of the SOAP body? Because its much simpler to use
the ServiceClient API which takes an OMElement directly.
ServiceClient sc = new ServiceClient(url);
// if the service needs an action:
sc.getOptions().setAction("http://whatever";);
OMElement response = sc.sendReceive(omElement);
The other option is to generate the stub using the nodatabinding
approach which will mean you don't have all those classes.
Try wsdl2java -d none
Paul
On 3/16/07, Rich Adili <[EMAIL PROTECTED]> wrote:
I'm writing a client for a service that takes an XML document as input. I'm
using WSDL2Java-generated code for my client. The generated code wants an
OMElement for the XML data. This snippet attempts to supply that. Clearly,
it ain't right as the send throws an exception. What am I doing wrong?
public void testme(final InputStream xmlStream) throws Exception
{
DispatchImportServiceStub stub = new
DispatchImportServiceStub();
DispatchImportServiceStub.ImportTripPlan
dataObject =
new
DispatchImportServiceStub.ImportTripPlan();
DispatchImportServiceStub.Plan_type0 Plan =
new DispatchImportServiceStub.Plan_type0();
XMLStreamReader parser =
XMLInputFactory.newInstance().createXMLStreamReader(xmlStream);
StAXOMBuilder builder = new StAXOMBuilder(parser);
OMElement documentElement = builder.getDocumentElement();
Plan.setExtraElement(documentElement);
dataObject.setPlan(Plan);
stub.ImportTripPlan(dataObject);
}
org.apache.axis2.AxisFault: Error in extracting message properties; nested
exception is:
org.apache.rampart.RampartException: Error in
extracting message properties
at
org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
at
org.apache.axis2.engine.Phase.invoke(Phase.java:382)
at
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:522)
at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:655)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:237)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
at
net.xatanet.axisstubs.DispatchImportServiceStub.ImportTripPlan(DispatchImportServiceStub.java:141)
at
net.xatanet.services.DispatchImportService.ImportTripPlan(DispatchImportService.java:82)
at test.TestImportTripPlan.run(TestImportTripPlan.java:33)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at test.GUI$2$1.run(GUI.java:97)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.rampart.RampartException: Error in
extracting message properties
at
org.apache.rampart.RampartMessageData.(RampartMessageData.java:294)
at
org.apache.rampart.MessageBuilder.build(MessageBuilder.java:56)
at
org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:59)
... 14 more
Caused by: org.apache.ws.security.WSSecurityException:
Error in converting SOAP Envelope to Document; nested exception is:
org.apache.axiom.om.OMException:
javax.xml.stream.XMLStreamException:
org.apache.axiom.om.OMException: Parser has already reached end of the
document. No siblings found
at
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:121)
at
org.apache.rampart.RampartMessageData.(RampartMessageData.java:146)
... 16 more
Caused by: org.apache.axiom.om.OMException:
javax.xml.stream.XMLStreamException:
org.apache.axiom.om.OMException: Parser has already reached end of the
document. No siblings found
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:199)
at
org.apache.axiom.om.impl.dom.NodeImpl.build(NodeImpl.java:469)
at
org.apache.axiom.om.impl.dom.DocumentImpl.build(DocumentImpl.java:476)
at
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:107)
... 17 more
Caused by: javax.xml.stream.XMLStreamException:
org.apache.axiom.om.OMException: Parser has already reached end of the
document. No siblings found
at
org.apache.axiom.om.impl.llom.OMStAXWrapper.updateLastNode(OMStAXWrapper.java:952)
at
org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:913)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:116)
... 20 more
Caused by: org.apache.axiom.om.OMException: Parser has already reached end
of the document. No siblings found
at
org.apache.axiom.om.impl.llom.OME
Embedding XML into SOAP
I'm writing a client for a service that takes an XML document as input.
I'm using WSDL2Java-generated code for my client. The generated code
wants an OMElement for the XML data. This snippet attempts to supply
that. Clearly, it ain't right as the send throws an exception. What am I
doing wrong?
public void testme(final InputStream xmlStream) throws Exception
{
DispatchImportServiceStub stub = new
DispatchImportServiceStub();
DispatchImportServiceStub.ImportTripPlan dataObject =
new
DispatchImportServiceStub.ImportTripPlan();
DispatchImportServiceStub.Plan_type0 Plan = new
DispatchImportServiceStub.Plan_type0();
XMLStreamReader parser =
XMLInputFactory.newInstance().createXMLStreamReader(xmlStream);
StAXOMBuilder builder = new StAXOMBuilder(parser);
OMElement documentElement =
builder.getDocumentElement();
Plan.setExtraElement(documentElement);
dataObject.setPlan(Plan);
stub.ImportTripPlan(dataObject);
}
org.apache.axis2.AxisFault: Error in extracting message properties;
nested exception is:
org.apache.rampart.RampartException: Error in extracting message
properties
at
org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
at org.apache.axis2.engine.Phase.invoke(Phase.java:382)
at
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:522)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:655)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:237)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:202)
at
net.xatanet.axisstubs.DispatchImportServiceStub.ImportTripPlan(DispatchI
mportServiceStub.java:141)
at
net.xatanet.services.DispatchImportService.ImportTripPlan(DispatchImport
Service.java:82)
at test.TestImportTripPlan.run(TestImportTripPlan.java:33)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at test.GUI$2$1.run(GUI.java:97)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.rampart.RampartException: Error in extracting
message properties
at
org.apache.rampart.RampartMessageData.(RampartMessageData.java:294
)
at
org.apache.rampart.MessageBuilder.build(MessageBuilder.java:56)
at
org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:59)
... 14 more
Caused by: org.apache.ws.security.WSSecurityException: Error in
converting SOAP Envelope to Document; nested exception is:
org.apache.axiom.om.OMException:
javax.xml.stream.XMLStreamException: org.apache.axiom.om.OMException:
Parser has already reached end of the document. No siblings found
at
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.
java:121)
at
org.apache.rampart.RampartMessageData.(RampartMessageData.java:146
)
... 16 more
Caused by: org.apache.axiom.om.OMException:
javax.xml.stream.XMLStreamException: org.apache.axiom.om.OMException:
Parser has already reached end of the document. No siblings found
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:1
99)
at
org.apache.axiom.om.impl.dom.NodeImpl.build(NodeImpl.java:469)
at
org.apache.axiom.om.impl.dom.DocumentImpl.build(DocumentImpl.java:476)
at
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.
java:107)
... 17 more
Caused by: javax.xml.stream.XMLStreamException:
org.apache.axiom.om.OMException: Parser has already reached end of the
document. No siblings found
at
org.apache.axiom.om.impl.llom.OMStAXWrapper.updateLastNode(OMStAXWrapper
.java:952)
at
org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:913)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:1
16)
... 20 more
Caused by: org.apache.axiom.om.OMException: Parser has already reached
end of the document. No siblings found
at
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementIm
pl.java:269)
at
org.apache.axiom.om.impl.llom.OMNavigator._getFirstChild(OMNavigator.jav
a:159)
at
org.apache.axiom.om.impl.llom.OMNavigator.updateNextNode(OMNavigator.jav
a:128)
at
org.apache.axiom.om.impl.llom.OMNavigator.next(OMNavigator.java:109)
at
org.apache.axiom.om.impl.llom.OMStAXWrapper.updateNextNode(OMStAXWrapper
.java:961)
at
org.apache.axiom.om.impl.llom.OMStAXWrapper.updateLastNode(OMStAXWrapper
.java:950)
... 22 more
Strategy for running multiple versions of web services concurrently
Hello, It is inevitable that your services will need to change. What are the best practices for running multiple versions of the same axis service concurrently? -Joshua
Re: [Axis2] Generated client stub causes Null Pointer Exception in UTF8OutputStreamWriter.write
Please don't use sun's stax parser, please use the one in axis2 dist
which is the woodstox parser.
thanks,
dims
On 3/16/07, D <[EMAIL PROTECTED]> wrote:
Hi Folks,
Please can you helpI have generated a webservice client from a wsdl
using wsdl2java.
When the stub is used to invoke the webservice the following exception
occurs:
java.lang.NullPointerException
at
com.sun.xml.stream.writers.UTF8OutputStreamWriter.write(UTF8OutputStreamWriter.java:128)
at
com.sun.xml.stream.writers.XMLStreamWriterImpl.writeDefaultNamespace(XMLStreamWriterImpl.java:728)
at
com.sun.xml.stream.writers.XMLStreamWriterImpl.writeNamespace(XMLStreamWriterImpl.java:914)
at
org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace(MTOMXMLStreamWriter.java:146)
at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement
(StreamingOMSerializer.java:243)
at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(StreamingOMSerializer.java:76)
at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize
(StreamingOMSerializer.java:59)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(OMSerializerUtil.java:473)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java
:823)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:848)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:819)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:180)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:848)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume
(OMNodeImpl.java:419)
at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.handleOMOutput(SOAPOverHTTPSender.java:190)
at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.writeRequest
(SOAPOverHTTPSender.java:232)
at
org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495)
at
org.apache.commons.httpclient.HttpMethodBase.writeRequest
(HttpMethodBase.java:1973)
at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java
:397)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at
org.apache.commons.httpclient.HttpClient.executeMethod
(HttpClient.java:346)
at
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:541)
at
org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java
:119)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:335)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java
:204)
at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:674)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:237)
at
org.apache.axis2.description.OutInAxisOperationClient.execute
(OutInAxisOperation.java:202)
at
com.madeupnamexyz.appproviders.generated.wssms.send.SmsSendServiceStub.SendSms(SmsSendServiceStub.java:171)
However, if I modify the stub by adding
System.out.println ("ENVELOPESTARTS:");
try
{
env.serialize(System.out);
}
catch(javax.xml.stream.XMLStreamException ex)
{
System.out.println(ex.toString ());
}
System.out.println(":ENVELOPEENDS:");
(i.e. I serialize the envelope to stdout) before the OperationClient
execute method is called by the stub, the operation completes successfully.
The WSDL and associated XSDs validate and wsdl2java gives no errors, so it
looks like env.serialize() is fixing something in the envelope!
The code using the client stub does not set anything to null and the output
from env.serialize() shows a valid soap envelope with all the expected
fields populated with valid values.
Has anyone else experienced this?
Is this a known issue?
Many Thanks,
Darren
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2-1.1.1] - Server- Error- mix webmethods name and its arguments
Please log a JIRA issue/upload your zip and add stack traces from the error as well. thanks, dims On 3/16/07, Olivier DUGAST <[EMAIL PROTECTED]> wrote: Hi everybody, I bench an application which uses Axis2 to call services. It works very well. But sometimes, when i call many webservices, at the same time(10 Threads on client), i've errors ( less than 1% ) : On server, Axis2 mix - webmethods name - and its arguments As you can see below What can i do to solve my problem? Best Regards, Olivier. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: No request found in SOAP envelope
oops [1] http://ws.apache.org/commons/tcpmon/
-- dims
On 3/16/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Paul,
Please try to use tcpmon [1]. Basically you will have to run tcpmon
listen on a port, forward the requests to your actual web service. And
in your code you will have to use the other constructor for
ExampleService_ServiceLocator which takes a url. this url should point
to your tcpmon ip address/port. I believe, your web service is
returning your a html page with some error information and not a soap
fault for whatever reason.
-- dims
On 3/16/07, Paul Miller <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> One more desperate plea:
>
>
>
> I submitted this question early in week, but received no reply. Perhaps my
> question was one I should have found answered in docs or archives or google
> – but I simply have not yet. I hate to give up on Axis – I feel I am 99%
> there and need only a little hint, but I'm stating to think I should try
> another path, another package. Is there anybody out there who could take a
> quick peek at my dozen lines of code and maybe the first few lines of stack
> trace and throw this starving hacker a few crumbs? J
>
>
>
> Thank You O Merciful Axis-Gurus! (I'm not worthy! I'm not worthy!)
>
>
>
>
> Paul Miller
>
>
>
>
> I'm new to Axis – 'bout a week – I'm attempting to connect to a 3rd-party
> webservice running on my localhost. I've gen'd the files using wsdl2java,
> and everything compiles and runs up to the actual "response =
> portType.calculateSquareRoot(request);" call, when I get the "No request
> found in SOAP envelope". I know the webservice is OK because same basic C#
> program works. My project links to all the axis jars in axis_1_4 + xerces
> -2_9_0. I'll include the simple code snippet and pertinent stack trace.
> (I've been googling on this for days + looked thru archives but couldn't
> find the right clue). Can anybody help? Or give me pointers to how I might
> track this down in debugger?
>
>
>
> Thanks!
>
> Paul Miller
>
>
>
>
> Code:
>
>
>
> try {
>
>
>
> // inputNum comes from user-entered value in TextField
>
> double inputNum = Double.parseDouble(inputTextField.getText());
>
>
>
> // default value until webservice caclulates it
>
> double outputNum = 0;
>
>
>
> // create the webservice obj with the ServiceLocator
>
> ExampleService_Service theService = new
> ExampleService_ServiceLocator();
>
>
>
> // get the port-type obj from theService - we make the calls to
> this obj
>
> ExampleService_PortType portType = theService.
> getExampleService();
>
>
>
> // create a request obj to hold all input and in/out params
>
> CalculateSquareRootRequest request = new
> CalculateSquareRootRequest();
>
>
>
> // response obj will hold results of service invocation
>
> CalculateSquareRootResponse response = null;
>
>
>
> request.setTheNumber(inputNum); // set in/out param "TheNumber"
>
>
>
>
>
> // this makes the call with the request obj as in params and we
> get response obj back
>
> response = portType.calculateSquareRoot(request);
>
>
>
> // extract output value of inout param "TheNumber" from response
>
> outputNum = response.getTheNumber();
>
>
>
> // just display it
>
> outputTextField.setText("" + outputNum);
>
>
>
> } catch (Exception e) {
>
> System.err.println("Execution failed. Exception: " + e );
>
> e.printStackTrace();
>
> }
>
>
>
>
> Stack Trace
>
> Execution failed. Exception: No request found in SOAP envelope
>
> AxisFault
>
> faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server
>
> faultSubcode:
>
> faultString: No request found in SOAP envelope
>
> faultActor:
>
> faultNode:
>
> faultDetail:
>
> {http://xml.apache.org/axis/}stackTrace:No request
> found in SOAP envelope
>
> at
>
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>
> at
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>
> at
>
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>
> at
> org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
> Source)
>
> at
> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
> Source)
>
> at
>
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
> Source)
>
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
>
> at
> org.apache.xerces.parsers.XML11Configuration.parse(Unknown
> Source)
>
> at
> org.apache.xerces.parsers.XML11Configuration.parse(Unknown
> Source)
>
> at
> org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>
> at
> org.apache.
Re: No request found in SOAP envelope
Paul,
Please try to use tcpmon [1]. Basically you will have to run tcpmon
listen on a port, forward the requests to your actual web service. And
in your code you will have to use the other constructor for
ExampleService_ServiceLocator which takes a url. this url should point
to your tcpmon ip address/port. I believe, your web service is
returning your a html page with some error information and not a soap
fault for whatever reason.
-- dims
On 3/16/07, Paul Miller <[EMAIL PROTECTED]> wrote:
One more desperate plea:
I submitted this question early in week, but received no reply. Perhaps my
question was one I should have found answered in docs or archives or google
– but I simply have not yet. I hate to give up on Axis – I feel I am 99%
there and need only a little hint, but I'm stating to think I should try
another path, another package. Is there anybody out there who could take a
quick peek at my dozen lines of code and maybe the first few lines of stack
trace and throw this starving hacker a few crumbs? J
Thank You O Merciful Axis-Gurus! (I'm not worthy! I'm not worthy!)
Paul Miller
I'm new to Axis – 'bout a week – I'm attempting to connect to a 3rd-party
webservice running on my localhost. I've gen'd the files using wsdl2java,
and everything compiles and runs up to the actual "response =
portType.calculateSquareRoot(request);" call, when I get the "No request
found in SOAP envelope". I know the webservice is OK because same basic C#
program works. My project links to all the axis jars in axis_1_4 + xerces
-2_9_0. I'll include the simple code snippet and pertinent stack trace.
(I've been googling on this for days + looked thru archives but couldn't
find the right clue). Can anybody help? Or give me pointers to how I might
track this down in debugger?
Thanks!
Paul Miller
Code:
try {
// inputNum comes from user-entered value in TextField
double inputNum = Double.parseDouble(inputTextField.getText());
// default value until webservice caclulates it
double outputNum = 0;
// create the webservice obj with the ServiceLocator
ExampleService_Service theService = new
ExampleService_ServiceLocator();
// get the port-type obj from theService - we make the calls to
this obj
ExampleService_PortType portType = theService.
getExampleService();
// create a request obj to hold all input and in/out params
CalculateSquareRootRequest request = new
CalculateSquareRootRequest();
// response obj will hold results of service invocation
CalculateSquareRootResponse response = null;
request.setTheNumber(inputNum); // set in/out param "TheNumber"
// this makes the call with the request obj as in params and we
get response obj back
response = portType.calculateSquareRoot(request);
// extract output value of inout param "TheNumber" from response
outputNum = response.getTheNumber();
// just display it
outputTextField.setText("" + outputNum);
} catch (Exception e) {
System.err.println("Execution failed. Exception: " + e );
e.printStackTrace();
}
Stack Trace
Execution failed. Exception: No request found in SOAP envelope
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: No request found in SOAP envelope
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:No request
found in SOAP envelope
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at
org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at
org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at
org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at
org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at
org.
Re: No request found in SOAP envelope
Since you are new to axis and this is new code, might I suggest moving
to axis2 ? The stable release is 1.1.1 with 1.2 coming shortly.
HTH,
Robert
On 3/16/07, Paul Miller <[EMAIL PROTECTED]> wrote:
One more desperate plea:
I submitted this question early in week, but received no reply. Perhaps my
question was one I should have found answered in docs or archives or google
– but I simply have not yet. I hate to give up on Axis – I feel I am 99%
there and need only a little hint, but I'm stating to think I should try
another path, another package. Is there anybody out there who could take a
quick peek at my dozen lines of code and maybe the first few lines of stack
trace and throw this starving hacker a few crumbs? J
Thank You O Merciful Axis-Gurus! (I'm not worthy! I'm not worthy!)
Paul Miller
I'm new to Axis – 'bout a week – I'm attempting to connect to a 3rd-party
webservice running on my localhost. I've gen'd the files using wsdl2java,
and everything compiles and runs up to the actual "response =
portType.calculateSquareRoot(request);" call, when I get the "No request
found in SOAP envelope". I know the webservice is OK because same basic C#
program works. My project links to all the axis jars in axis_1_4 + xerces
-2_9_0. I'll include the simple code snippet and pertinent stack trace.
(I've been googling on this for days + looked thru archives but couldn't
find the right clue). Can anybody help? Or give me pointers to how I might
track this down in debugger?
Thanks!
Paul Miller
Code:
try {
// inputNum comes from user-entered value in TextField
double inputNum = Double.parseDouble(inputTextField.getText());
// default value until webservice caclulates it
double outputNum = 0;
// create the webservice obj with the ServiceLocator
ExampleService_Service theService = new
ExampleService_ServiceLocator();
// get the port-type obj from theService - we make the calls to
this obj
ExampleService_PortType portType = theService.
getExampleService();
// create a request obj to hold all input and in/out params
CalculateSquareRootRequest request = new
CalculateSquareRootRequest();
// response obj will hold results of service invocation
CalculateSquareRootResponse response = null;
request.setTheNumber(inputNum); // set in/out param "TheNumber"
// this makes the call with the request obj as in params and we
get response obj back
response = portType.calculateSquareRoot(request);
// extract output value of inout param "TheNumber" from response
outputNum = response.getTheNumber();
// just display it
outputTextField.setText("" + outputNum);
} catch (Exception e) {
System.err.println("Execution failed. Exception: " + e );
e.printStackTrace();
}
Stack Trace
Execution failed. Exception: No request found in SOAP envelope
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: No request found in SOAP envelope
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:No request
found in SOAP envelope
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at
org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at
org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at
org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at
org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at
org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at
org.apache.axis.client.Call.invokeEngine(Call.java:2784)
RE: No request found in SOAP envelope
One more desperate plea:
I submitted this question early in week, but received no reply. Perhaps my
question was one I should have found answered in docs or archives or google
- but I simply have not yet. I hate to give up on Axis - I feel I am 99%
there and need only a little hint, but I'm stating to think I should try
another path, another package. Is there anybody out there who could take a
quick peek at my dozen lines of code and maybe the first few lines of stack
trace and throw this starving hacker a few crumbs? :-)
Thank You O Merciful Axis-Gurus! (I'm not worthy! I'm not worthy!)
Paul Miller
I'm new to Axis - 'bout a week - I'm attempting to connect to a 3rd-party
webservice running on my localhost. I've gen'd the files using wsdl2java,
and everything compiles and runs up to the actual "response =
portType.calculateSquareRoot(request);" call, when I get the "No request
found in SOAP envelope". I know the webservice is OK because same basic C#
program works. My project links to all the axis jars in axis_1_4 + xerces
-2_9_0. I'll include the simple code snippet and pertinent stack trace.
(I've been googling on this for days + looked thru archives but couldn't
find the right clue). Can anybody help? Or give me pointers to how I might
track this down in debugger?
Thanks!
Paul Miller
Code:
try {
// inputNum comes from user-entered value in TextField
double inputNum = Double.parseDouble(inputTextField.getText());
// default value until webservice caclulates it
double outputNum = 0;
// create the webservice obj with the ServiceLocator
ExampleService_Service theService = new
ExampleService_ServiceLocator();
// get the port-type obj from theService - we make the calls to
this obj
ExampleService_PortType portType = theService.
getExampleService();
// create a request obj to hold all input and in/out params
CalculateSquareRootRequest request = new
CalculateSquareRootRequest();
// response obj will hold results of service invocation
CalculateSquareRootResponse response = null;
request.setTheNumber(inputNum); // set in/out param "TheNumber"
// this makes the call with the request obj as in params and we
get response obj back
response = portType.calculateSquareRoot(request);
// extract output value of inout param "TheNumber" from response
outputNum = response.getTheNumber();
// just display it
outputTextField.setText("" + outputNum);
} catch (Exception e) {
System.err.println("Execution failed. Exception: " + e );
e.printStackTrace();
}
Stack Trace
Execution failed. Exception: No request found in SOAP envelope
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: No request found in SOAP envelope
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:No request found in SOAP
envelope
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:2
22)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:12
9)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationCo
ntext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc
her.dispatch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext
.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChe
cker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.in
[Axis2] Generated client stub causes Null Pointer Exception in UTF8OutputStreamWriter.write
Hi Folks,
Please can you helpI have generated a webservice client from a wsdl
using wsdl2java.
When the stub is used to invoke the webservice the following exception
occurs:
java.lang.NullPointerException
at com.sun.xml.stream.writers.UTF8OutputStreamWriter.write(
UTF8OutputStreamWriter.java:128)
at
com.sun.xml.stream.writers.XMLStreamWriterImpl.writeDefaultNamespace(
XMLStreamWriterImpl.java:728)
at com.sun.xml.stream.writers.XMLStreamWriterImpl.writeNamespace(
XMLStreamWriterImpl.java:914)
at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace(
MTOMXMLStreamWriter.java:146)
at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(
StreamingOMSerializer.java:243)
at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(
StreamingOMSerializer.java:76)
at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(
StreamingOMSerializer.java:59)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(
OMSerializerUtil.java:473)
at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
OMElementImpl.java:823)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(
OMElementImpl.java:848)
at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
OMElementImpl.java:819)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(
SOAPEnvelopeImpl.java:180)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(
OMElementImpl.java:848)
at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(
OMNodeImpl.java:419)
at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.handleOMOutput
(SOAPOverHTTPSender.java:190)
at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.writeRequest
(SOAPOverHTTPSender.java:232)
at
org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody
(EntityEnclosingMethod.java:495)
at org.apache.commons.httpclient.HttpMethodBase.writeRequest(
HttpMethodBase.java:1973)
at org.apache.commons.httpclient.HttpMethodBase.execute(
HttpMethodBase.java:993)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry
(HttpMethodDirector.java:397)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(
HttpMethodDirector.java:170)
at org.apache.commons.httpclient.HttpClient.executeMethod(
HttpClient.java:396)
at org.apache.commons.httpclient.HttpClient.executeMethod(
HttpClient.java:346)
at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(
AbstractHTTPSender.java:541)
at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(
SOAPOverHTTPSender.java:119)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons
(CommonsHTTPTransportSender.java:335)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke
(CommonsHTTPTransportSender.java:204)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:674)
at org.apache.axis2.description.OutInAxisOperationClient.send(
OutInAxisOperation.java:237)
at org.apache.axis2.description.OutInAxisOperationClient.execute(
OutInAxisOperation.java:202)
at
com.madeupnamexyz.appproviders.generated.wssms.send.SmsSendServiceStub.SendSms
(SmsSendServiceStub.java:171)
However, if I modify the stub by adding
System.out.println("ENVELOPESTARTS:");
try
{
env.serialize(System.out);
}
catch(javax.xml.stream.XMLStreamException ex)
{
System.out.println(ex.toString());
}
System.out.println(":ENVELOPEENDS:");
(i.e. I serialize the envelope to stdout) before the OperationClient
execute method is called by the stub, the operation completes successfully.
The WSDL and associated XSDs validate and wsdl2java gives no errors, so it
looks like env.serialize() is fixing something in the envelope!
The code using the client stub does not set anything to null and the output
from env.serialize() shows a valid soap envelope with all the expected
fields populated with valid values.
Has anyone else experienced this?
Is this a known issue?
Many Thanks,
Darren
Re: Which are minimal componets list
Hi Vikas, Please visit the following URL http://ws.apache.org/axis2/1_1_1/installationguide.html regards Charitha Vikas wrote: Hi friends, I want to develop web services with the help Apache axis. Which are the minimal components are required to build normal and simple web services? Thanks With best regards From Vikas R. Khengare - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Better way to map from axis generated objects to domain?
Yes I believe JiBX is the right way of using your existing domian objects with the Web Service. This would take care of the mapping required. I believe having your own custom mapping layer would not be a good idea. This is because it would require you to update the layer if and when there are any changes to the domain objects. Please correct me if I am wrong. Regards Niles Dennis Sosnoski <[EMAIL PROTECTED]> wrote: JiBX data binding allows you to map XML directly to your domain objects, while maintaining a fairly loose coupling between the XML and the objects. A binding definition is used to specify how the XML relates to the objects. - Dennis Dennis M. Sosnoski SOA and Web Services in Java Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Robert Monical wrote: > Transfer objects. I create a class for each required transfer. In some > cases, more than one domain class maps to a Web class. > > At 04:02 PM 3/15/2007 -0400, Josh wrote: >> Robert, >> >> My application has an existing domain/service layer that does not map >> 1:1 with the entities that will be used on the wire. My process thus >> far has been to create a schema for the web service input/output and >> generate the java objects that map to them. What I am left with is >> still two different object models. Just like we use Hibernate/Ibatis >> to map between objects and tables, I would like to map between these >> two layers of objects. This way, the web service layer can change >> independently from my existing domain/service layer. What are you >> using for your mapping layer? >> >> Joshua >> >> >> On 15 Mar 2007 17:48:58 -, *Robert Monical* >> > wrote: >> >> >> I use a mapping layer to go from WSDL generated to Domain >> Objects. Since this is a legacy system and the domain objects >> are reversed out of a database with Hibernate we have information >> in the domain objects that is not relevent to the Web service >> interface. >> >> If you have the ability/desire to tightly couple the Web service >> to your domain, then maybe you don't need to do a mapping. I'ld >> be nervous. >> >> >> >-Original Message- >> >From: axis-user@ws.apache.org >> >Sent: 03/15/07 - 12:18 >> >To: axis-user@ws.apache.org >> >Subject: RE: Better way to map from axis generated objects to >> domain? >> > >> >Hello, >> > >> >Starting from a wsdl/schema, Axis will generate some plumbing >> >code/objects >> >to marshal/unmarshal xml. Is there an easier way to map to/from >> these >> >generated object to my corresponding domain objects? Is anyone >> using >> >any >> >mapping layer to do this? What are the best practices for >> insulating >> >your >> >existing java code from changes to the code generated by Axis? >> > >> >Thanks, >> > >> >Joshua >> >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > Robert Monical > [EMAIL PROTECTED] > Cell: 402-203-6533 > Fax 509-461-5317 > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list.
AW: [Axis2] UsernameToken Authentication in Rampart
Thanks Ruchith, now it works with PasswordDigest! Best Regards, Sven -Ursprüngliche Nachricht- Von: Ruchith Fernando [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 16. März 2007 09:01 An: axis-user@ws.apache.org Betreff: Re: [Axis2] UsernameToken Authentication in Rampart Hi Sven, When using password digest mechanism the authentication is carried out by Rampart. At the callback handler you are expected to set the password in the WSPasswordCallback instance passed into the callback handler. This password value will be used by Rampart to generate the digest value and compare with the value in the incoming username token. Thanks, Ruchith On 3/14/07, Sven Schroebler <[EMAIL PROTECTED]> wrote: > Hello everybody, > > how can I access the password that was submitted in the PasswordDigest from > a UsernameToken to authenticate a username/password? > > I am using UsernameToken authentication to secure my webservice (Axis2 1.1.1 > with Rampart 1.1). I configured the client for Outflow-Security and the > server for Inflow-Security. After calling the webservice from the client, > when the callbackhandler of the service on the server is called, the > WSPasswordCallback-Instance only contains the username of the Token, not the > password (although present in the SOAP-Header). > > In contrast to that I can access the password in the service's > callbackhandler if I switch the PasswordType to "PasswordText" on the client > side (in plain text of course). > > Is it possible at all to authenticate against the submitted password digest? > Why does the WSPasswordCallback not cotain the value of "PasswordDigest", > nor the password? I would prefer using PasswordDigest authentication rather > than using PasswordText. > > I would greatly appreciate, if someone could give me a hint or a pointer to > more detailed information. The only information I found is this: > > [1] - http://wso2.org/library/240 > [2] - http://wso2.org/library/234 > > > > Best Regards, > Sven > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- www.ruchith.org www.wso2.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Which are minimal componets list
Hi friends, I want to develop web services with the help Apache axis. Which are the minimal components are required to build normal and simple web services? Thanks With best regards From Vikas R. Khengare
AW: [Axis2] Securing webservice
I am not using the aar-deployment for my service, but "exploded" deployment in my webapp. The directory "myService" (under WEB-INF\services) also contains the WSDL-file. But since I have put the parameter, Axis2 does not return a WSDL file anymore. A blank wsdl-file would be fine as well. Best Regards, Sven -Ursprüngliche Nachricht- Von: Grimshaw, Jeffrey [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 15. März 2007 23:11 An: axis-user@ws.apache.org Betreff: RE: [Axis2] Securing webservice But this will only work if you don't have a wsdl file in the aar? I'm using that parameter to return _my_ wsdl rather than the generated one. Cheers, Jeff Grimshaw Sr. Programmer/Analyst Green Point Mortgage -Original Message- From: Sven Schroebler [mailto:[EMAIL PROTECTED] Sent: Thursday, March 15, 2007 2:50 PM To: axis-user@ws.apache.org Subject: AW: [Axis2] Securing webservice Just found it. Simply add the following in the service.xml: true Sven -Ursprüngliche Nachricht- Von: Sven Schroebler [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 15. März 2007 22:37 An: axis-user@ws.apache.org Betreff: [Axis2] Securing webservice Hi Axis-Users & -Developers, is there a way to prevent Axis2 from returning the WSDL-File when requesting the service's URL with "?wsdl"? I only found information on this for Axis1. Thanks & Best Regards, Sven - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: rampart-1.0.mar and Axis2
Hi, Seems like you are using axis2-1.1 Please use Rampart-1.1 with Axis2-1.1. You have used wss4j axis-1.x type configuration and rampart configuration is different from that. Have a look at the samples of Rampart on sample configuration. Also there are some articles available on different configs of Rampart : http://www.wso2.org/library/240 http://www.wso2.org/library/255 Thanks, Ruchith p.s. Please post rampart related questions to rampart-dev@ws.apache.org On 3/16/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: rampart-1.0.mar and Axis2 I've added a rampart-1.0.mar module, also some lines have added to service.xml: into my ... but it completely doesn't work. First of all, it's returned (to be honest I've no idea how can I fix it?]: 09:25:40,328 INFO [TomcatDeployer] deploy, ctxPath=/axis2, warUrl=.../deploy/axis2.war/ 09:25:41,140 INFO [DeploymentEngine] Deploying module : addressing-1.1 09:25:41,765 ERROR [DeploymentEngine] Invalid module : rampart-1.0.mar caused org.apache.axis2.description.HandlerDescription.(Ljavax/ xml/namespace/QName;)V java.lang.NoSuchMethodError: org.apache.axis2.description.HandlerDescription.(Ljavax/xml/namespace/QName;)V at org.apache.axis2.security.handler.WSDoAllHandler.(WSDoAllHandler.java:38) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at java.lang.Class.newInstance0(Class.java:350) at java.lang.Class.newInstance(Class.java:303) at org.apache.axis2.deployment.util.Utils.addFlowHandlers(Utils.java:69) at org.apache.axis2.deployment.DeploymentEngine.addNewModule(DeploymentEngine.java:326) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:598) at org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:184) at org.apache.axis2.deployment.RepositoryListener.(RepositoryListener.java:54) at org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:104) at org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:199) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:61) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:373) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:317) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3857) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4118) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5005) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:280) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:88) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:357) at org.jboss.web.WebModule.startModule(WebModule.java:68) at org.jboss.web.WebModule.startService(WebModule.java:46) at org.jboss.
rampart-1.0.mar and Axis2
rampart-1.0.mar and Axis2 I've added a rampart-1.0.mar module, also some lines have added to service.xml: into my ... but it completely doesn't work. First of all, it's returned (to be honest I've no idea how can I fix it?]: 09:25:40,328 INFO [TomcatDeployer] deploy, ctxPath=/axis2, warUrl=.../deploy/axis2.war/ 09:25:41,140 INFO [DeploymentEngine] Deploying module : addressing-1.1 09:25:41,765 ERROR [DeploymentEngine] Invalid module : rampart-1.0.mar caused org.apache.axis2.description.HandlerDescription.(Ljavax/ xml/namespace/QName;)V java.lang.NoSuchMethodError: org.apache.axis2.description.HandlerDescription.(Ljavax/xml/namespace/QName;)V at org.apache.axis2.security.handler.WSDoAllHandler.(WSDoAllHandler.java:38) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at java.lang.Class.newInstance0(Class.java:350) at java.lang.Class.newInstance(Class.java:303) at org.apache.axis2.deployment.util.Utils.addFlowHandlers(Utils.java:69) at org.apache.axis2.deployment.DeploymentEngine.addNewModule(DeploymentEngine.java:326) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:598) at org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:184) at org.apache.axis2.deployment.RepositoryListener.(RepositoryListener.java:54) at org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:104) at org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:199) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:61) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:373) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:317) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3857) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4118) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5005) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:280) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:88) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:357) at org.jboss.web.WebModule.startModule(WebModule.java:68) at org.jboss.web.WebModule.startService(WebModule.java:46) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.serv
Re: [Axis2] UsernameToken Authentication in Rampart
Hi Sven, When using password digest mechanism the authentication is carried out by Rampart. At the callback handler you are expected to set the password in the WSPasswordCallback instance passed into the callback handler. This password value will be used by Rampart to generate the digest value and compare with the value in the incoming username token. Thanks, Ruchith On 3/14/07, Sven Schroebler <[EMAIL PROTECTED]> wrote: Hello everybody, how can I access the password that was submitted in the PasswordDigest from a UsernameToken to authenticate a username/password? I am using UsernameToken authentication to secure my webservice (Axis2 1.1.1 with Rampart 1.1). I configured the client for Outflow-Security and the server for Inflow-Security. After calling the webservice from the client, when the callbackhandler of the service on the server is called, the WSPasswordCallback-Instance only contains the username of the Token, not the password (although present in the SOAP-Header). In contrast to that I can access the password in the service's callbackhandler if I switch the PasswordType to "PasswordText" on the client side (in plain text of course). Is it possible at all to authenticate against the submitted password digest? Why does the WSPasswordCallback not cotain the value of "PasswordDigest", nor the password? I would prefer using PasswordDigest authentication rather than using PasswordText. I would greatly appreciate, if someone could give me a hint or a pointer to more detailed information. The only information I found is this: [1] - http://wso2.org/library/240 [2] - http://wso2.org/library/234 Best Regards, Sven - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.ruchith.org www.wso2.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
