Unfortunately, that is unsatisfactory for migration.I wonder what is stopping there from being wrapping/unwrapping for the wrapped convention.- ScottOn 5/22/06,
Anne Thomas Manes [EMAIL PROTECTED] wrote:
No -- you just have to use a bean to wrap your parameters. AnneOn 5/20/06,
Scott McCoy
Okay, attached is a WSDL that worked fine for generating very simple to use wrapped document/literal services with WSDL2Java.Now, the code WSDL2Java generates is as though the wrapped document/literal convention is broken.
It accepts a Request bean for each argument, and expects a Response bean in
In Axis 1, use org.apache.axis.AxisFault.If you just want to wrap an exception, the easiest way is to:catch (Exception exception) { throw AxisFault.makeFault(exception);}Cheers, Scott S. McCoy
On 5/19/06, Venkat Gyambavantha [EMAIL PROTECTED] wrote:
Hi,
I used wsdl2java to generate
I see, so I'm basically married to axis 1.3 for the time being.- ScottOn 5/20/06, Anne Thomas Manes [EMAIL PROTECTED]
wrote:Axis 2 does not yet support automatic unwrapping of wrapped doc/literal ...
On 5/20/06, Scott McCoy
[EMAIL PROTECTED] wrote:
Okay, attached is a WSDL that worked fine
I'm really struggling here, after writing all of my service implementations using approaches discussed in previous threads in this list, I found I was not actually WS-I Compliant as my services were reliant upon the SOAPAction header, which the WS-I
1.1 Profile says I must not do. So, I tried
-- Forwarded message --From: Scott McCoy [EMAIL PROTECTED]Date: Mar 2, 2006 11:33 AMSubject: Re: WSDD2Java + Admin util for deployment = Undescribably strange error...
To: [EMAIL PROTECTED]I've discovered that relying on the SOAPAction header does not comply
with WS-I Standards
got it to check imported WSDL/XSD files.If you find a good all-in-one checking tool, please let me know.
Regards,DiesScott McCoy wrote: -- Forwarded message -- From: Scott McCoy [EMAIL PROTECTED] Date: Mar 2, 2006 11:33 AM
Subject: Re: WSDD2Java + Admin util for deployment
Hello, I previously was mapping the WSDL2Java classes to a local namespace for our project. We have determined using the default generated java namespaces for the generated code, and using our internal namespace for the implementation, would be the best course of action.
However, when I changed
After further review, this appears to be a bug between org.apache.axis.wsdl.toJava.JavaBindingWriter and org.apache.axis.wsdl.toJava.Utils (in Axis 1.3). Can someone verify this?Thanks,Scott S. McCoy
On 3/1/06, Scott McCoy [EMAIL PROTECTED] wrote:
Hello, I previously was mapping the WSDL2Java
wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation!-- Make comparable changes to the other bindings --
Regards,AnneOn 2/22/06, Scott McCoy
[EMAIL PROTECTED] wrote:
Okay, I have a hand-crafted WSDL I'm using to generate Java with WSDL2Java and I'm using the deployment descriptor generated
I have also noticed that the WSDL generated by the code generated by *my* WSDL seems to mostly conform to your suggestions.Thanks, - ScottOn 2/23/06,
Scott McCoy [EMAIL PROTECTED] wrote:You know, when I tried to make some of these changes, I ran into some trouble. For instance, if I define
Okay, I have a hand-crafted WSDL I'm using to generate Java with WSDL2Java and I'm using the deployment descriptor generated by WSDL2Java to generate a server-config.wsdd, which I package in a war and deploy to my tomcat server.
This has all been working fine and dandy, util today, when I added a
/ /wsdl:output /wsdl:operation!-- Make comparable changes to the other bindings --
Regards,AnneOn 2/22/06, Scott McCoy
[EMAIL PROTECTED] wrote:
Okay, I have a hand-crafted WSDL I'm using to generate Java with WSDL2Java and I'm using the deployment descriptor generated by WSDL2Java to generate a server
Hello, I am trying to build a mechanism for which authentication takes place in the header. I was able to easily write a lower-level component I can use in the requestFlow/ of my WSDD, the only problem exists in that I need a WSDL that can easily be used to generate a client interface. What are a
Store it in the MessageContext.MessageContext context = MessageContext.getCurrentContext();context.setProperty(..., object);- Scott S. McCoyOn 2/15/06,
Scott McCoy [EMAIL PROTECTED] wrote:
I am using Axis 1.3, I am having some trouble passing information between the requestFlow handler
I saw an IBM article about something similar with Rhino and Axis 1.2, it was geared for E4X, but I once rewrote it to use DOM instead at one point. I don't have the code on this workstation, but I'll dig around my box at home tonight and see if I can post it.
You can fetch the code yourself, and
The attached WSDL and XSD are giving me this method signature.public class AccountSOAPBindingImpl implements tufte.model.service.account.Account{ public void createAccount(tufte.model.service.account.holders.AccountHolder
account) throws java.rmi.RemoteException { } public void
I see why, WSDL2Java will not generate a 'wrapped' style service if my complexType has attributes.Does anyone know *why* that is? What is the difference between an attribute and an element that only may have a single occurance?
On 2/14/06, Scott McCoy [EMAIL PROTECTED] wrote:
The attached WSDL
Thanks Dies, That totally solved my problem. I have another problem though, after your suggested changes (and before, for that matter) AccountSOAPBindingImpl becomes a class that implements the Account class generated.
The obvious problem with that, is that you cannot implement a class in Java,
Actually I seem to have solved that too, I cannot have a port type and an element of the same name, otherwise one overwrites the other apparently.Thanks, Scott S. McCoy
On 2/14/06, Scott McCoy [EMAIL PROTECTED] wrote:
Thanks Dies, That totally solved my problem. I have another problem though
/m:UserName m:Passwordpassword/m:Password
/m:UserToken /m:AuthInfo /SOAP-ENV:Header .. /SOAP-ENV:Envelop Hope this helps.
-Original Message- From: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]]On Behalf Of Scott McCoy Sent: Friday
I didn't get a response to this, so I thought I'd re-post it.I just want a handler, before my handler, to get some values from the header and have the ability to stop the request.How does that happen?
On 2/8/06, Scott McCoy [EMAIL PROTECTED] wrote:
Hello All, I have a specification that demands I
want a handler, before my handler, to get some values from the header and have the ability to stop the request.How does that happen?
On 2/8/06, Scott McCoy [EMAIL PROTECTED] wrote:Hello All,I have a specification that demands I use a SOAP Header element for credential verification, and from
Hello All, I have a specification that demands I use a SOAP Header element for credential verification, and from a technical perspective it needs to be highly reusable, with a technical requirement that it preceeds and stops processing of the SOAP Body. I've found what seems to be just the ticket,
Hello All, I am trying to implement a message-style API (as opposed to the automagical RPC stuff I've seen). I'd like, however, to write my java service handlers in a more traditional fasion rather than accepting document fragments and handling them with a bunch of DOM code. So I was doing some
are generating code from WSDL, then you have to follow the wrapped convention in your WSDL. See my blog entry for instructions:
http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html
Anne
On 2/7/06, Scott McCoy [EMAIL PROTECTED] wrote:
Hello All, I am trying to implement a message-style
With the attached documents, I attempt to use WSDL2Java to build some empty classes for me, however, I get this error:java.lang.NullPointerException at org.apache.axis.wsdl.symbolTable.SymbolTable.populateServices
(SymbolTable.java:3069) at
Hello, I have run into a problem. I need to add some initialization code to my web service, since this is a simple daemon service I'm using org.apache.axis.transport.http.SimpleAxisServer, rather than normal servlet container. The approach I attempted to use to solve this issue was adding static {
/Version-- dimsOn 11/21/05, Scott McCoy
[EMAIL PROTECTED] wrote: Actually I'm not having any luck calling axis services with the SOAP client's I typically use, is there anything different about what Axis may be
anticipating? On 11/20/05, Scott McCoy [EMAIL PROTECTED] wrote: I've been trying to custom
I've been trying to custom-craft a provider for axis, and in testing it
I determined my test was broken...and in testing my test, I determined
there is something about calling Axis services I don't understand, so
I'm trying to figure out what I am missing about the transaction with
the HTTP
Actually I'm not having any luck calling axis services with the SOAP client's I typically use, is there anything different about what Axis may be anticipating?On 11/20/05,
Scott McCoy [EMAIL PROTECTED] wrote:
I've been trying to custom-craft a provider for axis, and in testing it
I determined my
31 matches
Mail list logo
