Hello,
Anyone here every used the Axis-Admin servlet off an SSL connection?
I am getting:
server\build.xml [503] axis-admin failed with
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
java.lang.NumberFormatException: For input string: ""
Thanks for any help.
--
Lyndon Tiu
Filed under JIRA per your request as Axis-1698. -- Andy
>>> [EMAIL PROTECTED] 12/05/04 04:37AM >>>
JIRA please.
On Sun, 05 Dec 2004 01:00:22 -0700, ANDREW MICONE <[EMAIL PROTECTED]> wrote:
> Do you want it in an e-mail or do you want me to open a case in JIRA and
> attach it?
>
> >>> [EMAIL PR
I want wsdl2java to generate code that interoperates nicely with code
that already exists in my application. Thus, I don't want it to
generate specific classes, but rather bind to my existing ones,
possibly using custom deserializers.
I can achieve this goal partly by these steps
- types are d
I have a method that takes a complex type. When I
construct the Call object myself and set the
typeMapping everything is fine:
Call call= (Call) service.createCall();
QNameqn1 = new QName(
"urn:DigitalObjectServices", "ListObjectsSOAPRequest"
);
QNameqn2 = new QName(
"ur
Title: axis and list types...
why do i get FindResultMask and FindResultMaskNull types generated for the type belo?. also, i believe i should be able to OR these values together. i went as far as refactor FindResultMask as FindResultMaskNull and i was able to get data back but for only one
i've just downloaded the nightly build and i get an error with code that worked
under a previous build. here's my wsdl:
http://staging.mappoint.net/standard-30/MapPoint.wsdl
java.io.IOException: Non nillable element 'resultMask' is null.
at
org.apache.axis.encoding.ser.BeanSerializer
Could you please open a bug report with a "diff -u" against latest
XMLUtils.java?
thanks,
dims
On Mon, 06 Dec 2004 16:40:34 +0100, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> While doing performance tests on deserialization, I noticed that Axis
> scales very poorly when increasing th
I try to use the last version of axis : 1.2RC2 instead of the axis 1.1
I have a web service with a method of this type :
public Document execute(Document body)
when the web service receive the document, it has changed : all namespaces had
been moved to the root element !
The problem is that
I'm using custom deserializers on the client-side and found that I get
logged warning for missing serializers. Indeed, I don't have installed
corresponding serializers for these specific classes, because after all
they only need to be deserialized on the client-side. Or so I thought.
The stub
Hi,
While doing performance tests on deserialization, I noticed that Axis
scales very poorly when increasing the number of threads.
Here are the figures:
5 threads, 1000 messages: 15 seconds
10 threads, 1000 messages: 56 seconds
15 threads, 1000 messages: 93 seconds
The root of the problem is in XM
Kabaya,
You'll have to learn a bit about defining XML schema. Often just looking
at examples will teach you enough to get something working. There are also
some books on Web services, which include information on defining WSDL.
This is what I had to do, as I'd done no web services work up to a fe
I'm guessing that Axis is replacing any characters
that might be confused with XML markup, hence "<" is being
replaced with "<" and so on. I'm not sure why this wouldn't
get changed back again at the server side. Perhaps you can try defining
the parameter as a CDATA section, in your XML schema.
T
Madeleine,
The wrapped style only refers to the parameters
to the service, not the response. Consequently, your two WSDLs produce
the same input to the same service. However, the output from the service
is presumably sending back the following XML fragment:
the result
string
The first WSD
I don't think Axis can dispatch the call
for you. With message style, you've told Axis that you're effectively handling
the SOAP message yourself (though Axis allows you to use one of several
method signatures), consequently, you'll have to do the dispatching.
This is my reading of the situation,
Hi,
In SignedSOAPEnvelope.java in the security example, the actor and
mustUnderstand attributes are added to the envelope:
env.addAttribute(Constants.URI_SOAP11_ENV, "actor", "some-uri");
env.addAttribute(Constants.URI_SOAP11_ENV, "mustUnderstand", "1");
Shouldn't they be added to the head en
15 matches
Mail list logo