Hi Altin,
Yes -- makes sense:
(1) the method parameter (or return) type declaration:
(2) the (interface/abstract) type definition:
To me, this seems straightforward: interfaces (or abstract classes)
may be used as method parameters; and concrete objects (implementing
thos
I think this is a new problem. When I
ask for wsdl on the Version service (.../Version?WSDL) what I get is incomplete
-- there is no child of the element, and no
elements. I see the same thing with my own service, which
I created by starting with a WSDL file, and generating a skeleton
> 1). Does the latest Axis build support the attachement?
Yes.
> 2). If yes, does the attachement samples work with the latest build?
No. There seems to be a problem in RPCElement that does not pickup default
type serializer for the method call.
> 3). Is there any documentation for attachement in
The easiest thing to do is bring up tcpmon on anodd port (like 8181)
routing it to tomcat (8080).
-Dug
"Newman, Scott" <[EMAIL PROTECTED]> on 03/08/2002 03:09:16 PM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:RE: Bad namespace problems
Hi Dug
Running the tc
Hi Oliver,
It seems that at least on the JAX-RPC list, this question usually just gets
one a lecture on interfaces having no constructors and thus being
non-serializable; quite puzzling.
Well, I had to expose services whose interfaces rely heavily on abstract
data types, so (finally) I have some
Here it is attached.
Isn't ContentManagerServiceBindingStub for client side stuff?
I think my problem is at the server where it cannot find a class to
serialize "queryPropertyStruct"... Is the ContentManagerServiceBindingStub
used at the server end too?
Thanks for your help.
Sylvain.
---
Hi Dug
Running the tcpmon, the results I get, right off the bat (sounds like tomcat
is messing up to me) in the request box is:
Java.net.BindException: Address in use: JVM_Bind
I thought on the off-chance that it was something else using port 80, so I
changed both apache http and tomcat to use 7
Hi Mike
Just went through my machine and I had 3
instances of it. (using localhost). One in the jdk for the client,
one in \Apache Tomcat 4.0\common\lib (which I put there cause of sugestions
from the usergroup), and one in C:\Program Files\Apache Tomcat
4.0\webapps\axis\WEB-INF\lib.
run your stuff through tcpmon - whenever I've seen the client complain
about a bad namespace more often than not its because the server is
returning an error and the Axis client tries to parse it as xml. tcpmon
will show you the error the server is returning and then you'll know what's
wrong.
-Du
Do a search for 'axis.jar' on your machine to be
sure the old version is not getting picked up from somewhere else.
- Original Message -
From:
Newman,
Scott
To: [EMAIL PROTECTED]
Sent: Friday, March 08, 2002 1:26
PM
Subject: RE: bad envelope namespace
Hi
Hi June
Xerces is also in my classpath. This is
driving me nuts. The dang thing will just not work.
Newman
-Original Message-
From: Ma, June
[mailto:[EMAIL PROTECTED]]
Sent: Friday, March 08, 2002 2:25
PM
To: '[EMAIL PROTECTED]'
Subject: RE: bad envelope
namespace
Newman,
What
about xerces.jar ? I believe that should be in your classpath too.
Regards,
-June
-Original Message-From: Newman, Scott
[mailto:[EMAIL PROTECTED]]Sent: Friday, March 08, 2002 10:38
AMTo: [EMAIL PROTECTED]Subject: bad envelope
namespace
Hi all
G
Hi all
Getting a bit frustrated here. I've gone through
the list looking for answers to this, and although it's worked for
others, it will not go away for me. Every time I try to invoke the web
service, I get the sax exception 'bad envelope namespace'.
I have put axis.jar and logx
Will the APIs from SOAP 2.0 be fully compatible with Apache Axis? I'm trying
to decide whether I should start deploying services now in 2.0 or wait for
Axis.
Thanks for your assistance.
Wayne Salter
_
MSN Photos is the easiest wa
Russell,
I am equally stumped with this problem.
I am using IBM JDK 1.3 (shipped with websphere 4.0). Will try out March 8
nightly build.
Maneesh Sahu
interKeel, Inc.
www.interkeel.com
-Original Message-
From: Russell Butek [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 08, 2002 6:38 AM
Title: RE: [WSDL2Java] No deserializer defined for array type http://[.. .]/: QueryProperty
Can you also send me your ContentManagerServiceBindingStub.java? The one that axis generates for me from the wsdl looks good. It contains the propper mappings. If the binding stub is correct, perhaps wh
Have a look. Attached is the wsdl.
Here is the stack on the command line:
Exception in thread "main" org.xml.sax.SAXException: No deserializer defined
for array type http://developer.cognos.com/schemas/cm/1/:queryPropertyStruct
at org.apache.axis.message.SOAPFaultBuilder.endElement(Unkn
I receive the following error from many services I've
developed, using either the nightly build (from
8-3-2002) or the beta1-rc (7-3-2002).
I'm generating Stubs and Skeletons from hand-made WSDL
files and there isn't any problem either during
generation or deployment.
Is this a bug or am I doing
I apologize if this is a stupid question, but is there any way to tell
Axis to use the BeanSerializer by default for any Java class that hasn't
had a specific serializer registered for it ?
I'm trying to write a Java client-side for a generic server service
allowing SOAP clients to call methods o
Title: RE: [WSDL2Java] No deserializer defined for array type http://[.. .]/: QueryProperty
I'm sorry I misunderstood the problem. Could you send the stacktrace and the full wsdl of the error you're getting? This sounds like a bug, not a problem with the specification of the mapping.
Dave
-
Hello
all,
I am writting a
series of handlers to be invoke bevor the RPCProvider is being called and
eventually the method itself.
I did find out how
to retrieve the name of the service being intended but I couldn't find a way to
find out
what particular
method of this service will be in
Generating server-side bindings is normally only done when you're starting
with WSDL and don't have a service. You already have a service, so you
don't have to generate the server-side bindings. All you need is a
deploy.wsdd file (which you COULD get by generating the server-side
bindings, tweak
I'm stumped. If WSDL2Java now works, I don't understand why the runtime
wouldn't work as well. The exception means that it has the
resources.properties file but it can't find the key oddDigits00 in that
file. That key has been there since November 12 (resources.properties was
born on November 5
Hi,
To your question, "Why can't your code reference QueryProperty instead of
queryProperty"? I say because it is not my code! This is the Axis server
that fails to deserialize because it does not find a class to use to
deserialize queryProperty. It only has a class named QueryProperty.
I
Title: WELCOME to [EMAIL PROTECTED]
Heya,
I've deployed a simple service using the command
java org.apache.axis.client.AdminClient -llocal:///AdminService
deploy.wsdd
and it runs fine if i use the command
java com.bp.webService.ReportsDescriptionServiceClient -llocal://
(where ReportsDe
When I test an AXIS service via SOAP the elements in
the SOAP body are placed inside a multiRef element. Is
there any reason for this? I think this makes reading
harder.
Why not plain elements?
Many thanks,
Nuno Guerreiro
__
Do You Yahoo!?
Try
Hi,
I have also played with attachments with Axis for a couples of days and I
could also
not make it work. I got an exception that said that attachments are not
supported. If
you want to have an example of attachments download WSTK from IBM which
contains one example with attachments. The inte
I'm receiving a "ClassNotFoundException: byte"
exception when invoking a web service with two complex
type parameters, one of which contains an element
which is a restriction to the "byte" base type.
The service stubs and skeletons were generated with
the WSDL2JAVA tool and I can see that one of
I used the message example in the nightly build to create my own
message application (creating soap body elements and putting them in
the call.invoke method). To add attachments to it, I use the method
addAttachmentPart from the call function. I was wondering if this is
how SOAP messaging with att
the problem is that the deploy.wsdd
is exactly as you describe !
any more guess ?
Guido Di Maio.
-Original Message-
From: robert louis [mailto:[EMAIL PROTECTED]]
Sent: giovedì 7 marzo 2002 23.20
To: [EMAIL PROTECTED]
Subject: Re: samples.userguide.example5
There is a typo in the depl
30 matches
Mail list logo
