Hi
When i try to delploy a deploy.wsdd file, using the following command
(using Axis RC-1)
java org.apache.axis.client.AdminClient
-lhttp://localhost:8080/axis/services/AdminService deploy.wsdd
I got the following error (Tomcat is running at 8080) -
Title: Message
What
about non-axis (or for that matter non-java, ie .Net clients) and session
management ?
-Original Message-From: Volanis, Alexander
[mailto:[EMAIL PROTECTED]]Sent: 27. september 2002
16:48To: '[EMAIL PROTECTED]'Subject: RE:
Naresh,
In the source you can check the method that the JVM is not able to find.
When you are using AXIS RC1.0 then the method on that line is getLocalName()
on a org.w3c.dom.Element class.
What JVM XML parser are you using?
Sjaak
-Original Message-
From: Naresh Agarwal
On Monday 30 September 2002 09:58, Jan-Olav Eide wrote:
What about non-axis (or for that matter non-java, ie .Net clients)
and session management ?
When using HTTP cookies for session management the MS SOAP library
3.0 supports this automatically. As for .net clients I do not know
but I
When using HTTP cookies for session management the MS SOAP library
3.0 supports this automatically. As for .net clients I do not know
but I think they will do the same.
So what is the best way to gracefully detect and reject requests from (MS
SOAP or Java) clients that are not
Naresh,
The localName is part of DOM level 2.
It looks like a level 1 parser is used, but Xerces 1.4.4 is level 2.
I can't help you any further.
Sjaak
-Original Message-
From: Naresh Agarwal [mailto:[EMAIL PROTECTED]]
Sent: 30 September, 2002 10:30
To: [EMAIL PROTECTED]
Subject:
Hi,
I have a problem that looks like an Axis bug. If anybody
confirms this I'll file a bug, otherwise please tell me what
the solution is.
I'm using the following WSDL fragment:
xs:simpleType name=UserIdType
xs:restriction base=xs:string/
/xs:simpleType
xs:complexType
Hi!
Try deploying like this
java org.apache.axis.client.AdminClient -hlocalhost -p8080
-s/axis/services/AdminService deploy.wsdd
Best regards,
Kovi
At 13:25 30.9.2002 +0530, you wrote:
Hi
When i try to delploy a deploy.wsdd file, using the following
command
Hi Torsten,
I've had teh same problem.
currently the WSDL MIME binding is not implemented in AXIS.
There is some special support which will not lead to interoperable
solutions.
I've attached an earlier mail from Russel.
There is one example which does not use any WSDL tool in
I have a soap service that has a method of signature like:
public Folder[] logon (String configDir, String appName, String
serverName, String loginName, String passwd)
Where Folder is a Java bean representing a file directory.
This same interface works with SoapImplementation, but when
Hi,
I'm getting the same error. I'm running Axis in a IBM WebSphere 3.5 AppServer. The
beta 3 version worked without problems.
Does anybody know why this is happening?
Thanks!
org.apache.commons.discovery.DiscoveryException: No implementation defined for
Tuan,
I have a similar need but for a totally different reason. We have a services
framework and want to dynamically publish public 'service entry points' at
runtime through Axis SOAP. We only have a Java class file and an associated
interface as parameters so we have to make up the rest of the
Hi,
Please help as I really have to get something done for our evaluation of
AXIS.
I really appreciate your help and a quick reply.
Now the problem is that I register the bean mapping as follows:
deployment xmlns=http://xml.apache.org/axis/wsdd/;
Title: Message
AFAIK,
not natively. However, be creative: if the client passes its namespace uri,
local part, and end point to the server on the initial call, the server can use
this information at a later time to call the client.
I have
done this and it works.
-Original
This is exactly what I needs. I have my own object Folder (representing
file system folder), and I want to return array of it.
I define a bean map as:
deployment xmlns=http://xml.apache.org/axis/wsdd/;
xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
service
How does the handler detect the incoming request belongs to some existing
sessions ?? (is it assessible via MessageContext ?) And then throw a SOAP
Fault if not.
Rgds, Ricky
At 10:29 AM 9/30/2002 +0200, Matthias Brunner wrote:
On Monday 30 September 2002 10:23, Jan-Olav Eide wrote:
When
Jian Zhang wrote:
It seems to me that the Axis picks up the definition of type Folder, but not
Folder[].
How should I tell Axis about Folder[]?
I would suggest that to simplify your life, during the evaluation, use
java2wsdl and wsdl2java to create the files, as it can handle arrays of
I am quite new to Axis and have to finish something today.
I am afraid that I won't that much time to use java2wsd. or wsdl2java.
I have all the server code and client code, just stuck with passing
array of objects back to the client.
I found a number of emails asking about this. This should
Title: XML ACCEPTOR WEBSERVICE
Hi All!
I have to implement a webservice that must accept a XML. Obviously, the first approach is to say that the XML is a simple string. However, I am not sure that's the better option.
Have you got some ideas or experiences about how to do it?. If the XML
I don't know if this is a bug or not, but I've been trying to clear a
previously set username/password from a Call object and it seems to make no
difference. I'd like to essentially have the 'authentication' process done
with and over and have a 'session' established at which point I can quit
Title: WEBSERVICES SECURITY
Hi All!
Could you tell me what are the common practices while managing webservices authentication?. Is there something to do with certificates?
Thank you very much.
Carlos
I am trying to install and test RC1 of Axis, and am getting a
mysterious failure in step 5 Installation testing of the
installation instructions. The validation servlet complains about an
internal server error with root cause java.lang.NoClassDefFoundError:
org/w3c/dom/DOMErrorHandler. But I
In case you were wonder, adding xmlParserAPIs.jar to the WEB-INF/lib/ does
not solve the problem.
I repeated my test with the just-announced Axis RC2. That fails in
exactly the same way.
:-(
Mike
Hello,
Where would I find
org.apache.axis.encoding.ser.SimpleNonPrimitiveSerializerFactory?
You wouldn't, because that class has been removed from the package, as have all
references to it. Are you perhaps using old classes/code?
--Glen
-Original Message-
From: James Black [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 30, 2002 4:03 PM
To: [EMAIL PROTECTED]
Hi,
I have a given WSDL file and want to generate client stubs and server
skeletons for it. The problem is that for whatever reason wsdl2java does
not generate code for some types defined in the WSDL.
I've browsed the list and tried options without success. Esp. I have
specified -all.
- Original Message -
From: Mike Spreitzer [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 30, 2002 12:43 PM
Subject: Re: Validation fails due to NoClassDefFoundError:
org/w3c/dom/DOMErrorHandler, even though xercesImpl.jar is in
webapps/axis-rc1/WEB-INF/lib
In case you
I'm pleased to announce release candidate 2 of Axis release 1. All unit
and functional tests pass with this release. The SAAJ and JAX RPC TCK
tests pass. All bugs reported as of this morning targetted for the 1.0
release are resolved in this drop. Pending feedback from people like
Title: Message
Grant,
As the
name implies "scope"="session" is the way to enable session tracking in Axis
services. It is really up to the client to maintain the session by caching the
HTTP cookies returned by the server. Most clients would either do this by
default or require a flag to
Grant,
It's obviously your solution is a feasible work-around. However, as you stated, it's
really a big mess.
Now I consider switching to GLUE which supports dynamic publishing from the beginning.
If you're interested, take a look at http://www.themindelectric.com
However, I really
I agree that dynamic endpoints are handy; .net remoting does it BTW, though
that doesnt help.
why not look at what the Axis engine is up to and maybe call it directly?
Adding an API to do everything seamlessly would be nice.
-steve
- Original Message -
From: Tuan Le Viet [EMAIL
Title: Adding SOAP header in Axis client
I am trying to transmit a SOAP header from my Axis client, but it is not working. Below is the manually modified stub code that tries to add the header to the SOAP message:
Document doc = XMLUtils.newDocument();
Element root =
Title: RE: Adding SOAP header in Axis client
I am trying to transmit a SOAP header from my Axis client, but it is not working. Below is the manually modified stub code that tries to add the header to the SOAP message:
Document doc = XMLUtils.newDocument();
Element root =
Title: RE: org.xml.sax.SAXException: No deserializer, problem
Hi, Jian
How about a work around, define a class which holds your array, and make the new class a bean. Something like this
class Folders {
Folder[] folders;
getter/setter functions
}
In deployment file, also define
Hi all,
i see that we can register custom
serializer/deserializer mappings on client side using
the call object.. and on server side this can be done
through wsdd file. I am wondering if the type
registering on client side can also be done through
wsdd file ..something like client-deploy.wsdd
Sorry - missed that, but why would you really want to deploy one service
per account? That's going to be a scalability nightmare. Why not just
have the account number in a soap header, as a param on an rpc call or even
in the URL (ie.
I am currently trying to build a server specifically for Axis, with a
few extra features, in order to provide something of a complete Java web
services solution (see www.lombok.org.uk for details). I am, however,
stuck in that every time I try to access a service, including the
AdminService at
Dug,
My idea was to have a more OO approach. I'll have a manager which manages lifetime of
Account service. Each service will be published when necessary and unpublished when
it's no longer needed.
This would not be a nightmore for scalability right?
Cheers,
Tuan
Hi,
I am sorry...I could not find the .war for AXIS and not SOAP.
Thanks,
Shankar Shanmugam
-Original Message-
From: Shankar S [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 01, 2002 10:53 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Soap and JRun version 4.0
Hi,
Please let me know
SOAP is more an RPC mechanism than a remote Object mechanism. I doubt it
would be scalable. From the lesson we learnt in EJB, if we shouldn't
expose EntityBean, then expose a web service per object instance is even
much worse.
Rgds, Ricky
At 10:48 AM 10/1/2002 +0700, Tuan Le Viet wrote:
40 matches
Mail list logo
