Just got around to getting beta2. I get the following generating WSDL
from a class that works for beta1.
This takes about 15min at 100% CPU to get this error:
[java] javax.xml.rpc.JAXRPCException: unable to get serializer for class
org.apache.axis.encoding.ser.BeanSerializer
[java]
> "kevin" == kevin d <[EMAIL PROTECTED]> writes:
kevin> I'm a bit fuzzy about whether WSDL2Java is supposed to
kevin> support overloaded methods. I'm trying to generate proxies
kevin> for a Microsoft .Net web service that has overloaded method
kevin> signatures. In the .Net mo
The change in Java2WSDL that is wreaking havoc is that Java2WSDL is
now picking up non-public methods on the target class, by default.
Even if I specify the list of methods to use on the command line, if I
have an overloaded method, one private and one public they BOTH get
picked up. Then we run
This is against the CVS version, today May 07, 10am MST.
I'm trying to register a custom provider that know how to get EJB's
from our framework. I modeled the Provider from
org.apache.axis.providers.java.EJBProvider.
My wsdd looks like this:
...
But I keep getting
> "Naresh" == Naresh Bhatia <[EMAIL PROTECTED]> writes:
Naresh> I have some questions regarding the Java classes generated
Naresh> by WSDL2Java. My assumption is that WSDL2Java was written
Naresh> primarily to create a Web Service client. However it is
Naresh> making the maint
> "Naresh" == Naresh Bhatia <[EMAIL PROTECTED]> writes:
Naresh> Is there a way for Java2WSDL to generate method parameter
Naresh> names as specified in the Java classes instead of in0, in1
Naresh> etc?
I think you need debug information (javac -g) in you .class files
- Bob
--
> "Martin" == Martin Hubley <[EMAIL PROTECTED]> writes:
Martin> Hi, we have the following five overloaded method
Martin> signatures in a published SOAP object in Axis Beta 2
Martin> (don't ask why we have so many, that's out of my control
Martin> at the moment):
Overloaded me
> "Sam" == Sam Kapoor <[EMAIL PROTECTED]> writes:
Sam> Hi: what I want to do is write a custom exception class and
Sam> propagate it from one of the methods on my Web-Service to the
Sam> client. So I define a Java exception class:
Sam> public class EInvalidCustomer extends E
> "Geza" == Geza Szocs <[EMAIL PROTECTED]> writes:
Geza> Hi guys !
Geza> 1 easy question.
Geza> I happen to have a servlet which is also an Axis
Geza> client. I also have some client-side handlers. I wrote the
Geza> client_deploy.wsdd and deployed, getting a
Geza> c
> "Olivier" == Olivier Brand <[EMAIL PROTECTED]> writes:
Olivier> All,
Olivier> Has anyone implemented a Cstor Ser./Deser. for Axis ? I
Olivier> have done it for Apache Soap while ago (which allowed me
Olivier> to pass complex structures), but Axis is way more complex
Oli
> "olivier" == olivier brand <[EMAIL PROTECTED]> writes:
olivier> Axis developers, Following the emails I sent a few days
olivier> ago about Castor. I have implemented a set of
olivier> Serializers/Deserializers for Castor objects.
That's awesome!!
olivier> The advantage wit
> "Rey" == reynardine writes:
Rey> Hello, I am new to the list and have checked the Axis FAQ's
Rey> but cannot find an answer to this question.
Rey> Can Axis work on Tomcat 3 ?
We are using Axis with Tomcat 3.0.3 with no problems.
- Bob
--
SynXis Corporation | [EMAIL PR
> "Rajesh" == I V Rajesh writes:
Rajesh> Hi,
Rajesh> I have deployed my service in Axis engine. I have
Rajesh> written
Rajesh> serializer and deserializer for the class ObjectName which
Rajesh> is used for invoking the method in RemoteMBeanServerImpl.
> "Michael" == Michael Brennen <[EMAIL PROTECTED]> writes:
Michael> This is my first attempt to install axis. I've run
Michael> tomcat and jsps for some time, and now I would like to
Michael> get into soap. I think axis is finally close to working,
Michael> but I'm getting a
> "Rajesh" == I V Rajesh writes:
Rajesh> Hi Bob, Thanks for the help. The following is the content
Rajesh> in the wsdd file. ObjectNameSerFactory and
Rajesh> ObjectNameDeserFactory are the serializer and deserializer
Rajesh> factory classes for ObjectName. The serializer an
It seems with axis, when doing Java <-> Java development the easiest
thing is to use Java2WSDL then WSDL2Java to get your client stubs.
If I have access to the same data-holder classes on both sides, it
seems I loose functionality that may be in my Bean classes on the
server-side when I generate
ng data-holders.
All I want is an option to suppress the generation of the
data-holders. Leave everything else as it is.
- Bob
Russell> Bob Cotton <[EMAIL PROTECTED]>@synxis.com on 03/06/2002
Russell> 03:27:06 PM
Russell> Please respond to [EMAIL PROTECTED]
17 matches
Mail list logo