It sounds to be a connection issue
I have a innocent question :
Did you start and deploy axis with Tomcat before executing the Adminclient command ? ;-)
herve
* Herve Attia
Cell (650) 922-1973
Home (650) 992-3997
http://www.chez.com/attia/resume/
I can't use the AdminClient ... here's what I get:
-
[drt@viking axis]$ java
org.apache.axis.client.AdminClient deploy.wsdd
- Processing file deploy.wsdd
- AxisFault: AxisFault
faultCode:
http://xml.apache.org/axis/:Server.userException
faultString: ja
I have got too much problems running Axis Beta 1/Tomcat4.0!
For instance, Axis doesn't create anymore a default server-config.wsdd in the WEB-INF directory
Also, when I try to deploy some services, it complains about Engine configuration is not present ?!!!
thanks
- Could not write engine c
The problem is not yours. The user's manual wasn't cleaned up before the
beta candidate, but I worked on it this weekend. The latest drop - AND the
real beta, when it comes out - has example5 (and others) fixed.
Russell Butek
[EMAIL PROTECTED]
robert woodley <[EMAIL PROTECTED]> on 03/11/2002
Maybe I'm wrong but actually the org.apache.axis.encoding.ser.JAFDataHandlerSerializer is not provided in the given binary installation (axis.jar)
Send and receive Hotmail on your mobile device: Click Here--- Begin Message ---
concerning my previous mail. see below
As the NamespaceURI is null wh
Note that the notorious Example 5 still doesn't work
in the beta-release candidate. To make it work, you
need to declare the return type by inserting this
line:
call.setReturnType( XMLType.XSD_STRING);
I guess the examples are not tested prior to release,
or maybe I've done something wrong (alwa
I moved to Axis Beta 1.
How to generate method within the Stub implementation with MessageContext as input Parameter ?
Does this features has been removed ? (option WSDL2Java "-m" )
I need my stubImplementation to access MessageContext to do the following :
HttpServlet servlet =
(HttpServlet)ctx.g
Title: RE: Array deserializer (was: [WSDL2Java] No deserializer defined for array type http://[.. .]/: QueryProperty)
I know my assumption was wrong -- this problem has nothing to do with WSDL2Java since the exception is coming from the server. I would need to see how you set up your service,
I think that your assumption is wrong... or it is mine that is ;-)
I believe the problem is on the server, it looks to me that the server does
not find the class to instantiate when it sees "queryPropertyStruct" (The
closest match is a class named QueryPropertyStruct).
Look at the message bel
Corbett,
For 2)
Not sure what you're using for a server, but if you're using Tomcat you can
implement the LifecycleListener interface by doing something like this:
package mycompany.mypackage;
import org.apache.catalina.LifecycleListener;
import org.apache.catalina.LifecycleEvent;
public clas
Hello all...pardon if my question(s) are naive; I just have been playing
around with this as of today (I like what I see though!).
What I'm trying to figure out is:
1) How to pass arbitrary properties to a service; WSDD doesn't seem
too documented (or are there docs around WSDD that I don'
Simon:
Are you using the current CVS code? Some recent work has been done in this area and
I'd like to know if you're still seeing the problem. If so, we'll nail it.
--G
> -Original Message-
> From: Simon McClenahan [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 11, 2002 12:01 PM
Title: RE: [WSDL2Java] No deserializer defined for array type http://[.. .]/: QueryProperty
The WSDL2Java tool is used to generate the client stubs, so I assumed the problems you were having were on the client side. Could you please tell me exactly the steps you went through to set up your ser
I use attachments in a message example, by creating a soap envelope
and adding attachments to the call object. The attachments arrive at
the service side together with my soapenvelope. Is this way to add
attachments in a message oriented environment? If so, in the latest
beta release I can not fin
In a previous message
http://marc.theaimsgroup.com/?l=axis-user&m=101430720610385&w=2 no-one
replied about my query regarding primitive transmission types mentioned
in the WSDL spec. I am more interested in HTTP transport, but the
"one-way" and "notification" transmission types seems to acknowledg
Very curious! I don't have an explanation for you. The JAF classes SHOULD
be in the beta. I don't know why they weren't in the candidate.
Russell Butek
[EMAIL PROTECTED]
Karna Harsha <[EMAIL PROTECTED]> on 03/10/2002 11:45:07 PM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
I seem to be having difficulty generating the correct tag-name for the
status type element in our response. Here is the WSDL fragment:
WSDL2Java generates:
public samurai.ws.Status runTransform(samurai.ws.IoSpec source,
samurai.ws.IoSpec sink, java.lang.String
Thanks. Fixed. It may take a few hours (no more than 6) for the update to
make it to the official web page.
Russell Butek
[EMAIL PROTECTED]
"Di Toudi" <[EMAIL PROTECTED]> on 03/11/2002 08:18:47 AM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:Axis home page :
Do you mean the namespace of the body element? If so, you
can pass it in on the setOperationName() method:
call.setOperationName( new QName( ns, opName ) );
Or, one of the call.invoke()'s itself takes a QName as the 1st param.
Unfortunately, Axis has changed so much since the book came
out tha
Hi Dug
Yeah, it confused the heck out of me for a while. Kinda makes you think you
know what is going wrong. One question I do have about the new beta
candidate, is where do you define your namespace? I had downloaded it, and
was testing it out, and I found that the call.NAMESPACE field was no
btw - in the latest version the Axis client should throw a much more
meaningful exception - hopefully, we've seen the last of those "bad
envelope" error messages. Although, you'll have to look inside the
AxisFault itself (or do a dumpToString()) - doing a toString() on it won't
be enough to see t
The link to the beta-rc1 on the main page
(http://xml.apache.org/axis/) is break :
http://xml.apache.org/axis/dist/beta-rc1
should be
http://xml.apache.org/axis/dist/beta1-rc1/
didier
_
MSN Photos est le moyen le plus simple de part
Just got over this myself.
Try putting axis.jar and logxx.jar into tomcat's commom/lib folder.
Also, use tcpmon to forward your soap calls to port 8080 (if that is your
tomcat port) and see what your request/response looks like. In my case, the
reason I was getting the bad envelope namespace
Hi!
I'm using the new beta version of Axis. I try to make a simple call to a
simple service just to try it out, but nothing happens and on the client I
get "Moved Temporarily".
I have copied code from the user-guide, Basics - Getting Started, and
modified it slightly to fit my login application.
Hellu,
I can get the Axis example to work. Everytime I try the wsdd Calculator
example With Axis alpha 3 and try to deploy it, I do get the following
error:
---
C:\Ed_soft\Develop\Manual\xml-axis-alpha3\samples\ed>java -cp .;./a
xis.jar;./log4j-core.jar;./jaxp.jar;./crimson.jar org.
Hi,
I want to know whether the Beta candidate has support
for attachments?
Because, when I downloaded the Beta candidate
(07-march-02), I could not find JAFSerializer and
JAFDeserializer classes in axis.jar. Which means that
I cant send attachments.
But when I downloaded nightly build (10-marc
Hi
I am trying to access a AXIS service over HTTPS.
I created all the required client and server side
keystores and trust stores using keytool(Followed all
the steps specified in Builidnig Web Services with
Java book). I also imported the certificates in
cacerts located at jre\lib\security. I als
Hellu,
I can get the Axis example to work. Everytime I try the wsdd Calculator
example With Axis alpha 3 and try to deploy it, I do get the following
error:
---
C:\Ed_soft\Develop\Manual\xml-axis-alpha3\samples\ed>java -cp .;./a
xis.jar;./log4j-core.jar;./jaxp.jar;./crimson.jar org.
Im now working with the beta rc and have ported my app from alpha3 without
too much difficulty.
However, since I am deploying to weblogic6.1, I encountered a slight problem
with configuration initialisation.
If I dont define the axis.attachments.Directory init param in web.xml for
the AxisServl
Hi Oliver,
Indeed I am not sure how the specs cover this topic.
As for (de)serializers, I am not using custom ones; I simply register a
(which uses the default Axis BeanSerializer and its
Deser..Factory) for every concrete type [or rather, because my concrete
types are obtained via a factory
30 matches
Mail list logo
