On the server side, using the standard J2EE authentication scheme, you just
set up a trust certificate store, with the accepted client certificates, and
configure your web application to use it for authentication. I did it with
Tomcat (alone) or Tomcat+Jonas without any problem for simple web
release of ant to check if the class not
found problem is present as well. Once you update the issue with your
comments, i will take a look at them again.
thanks,
dims
On Wed, 26 Jan 2005 19:34:44 +0100, Ephemeris Lappis
[EMAIL PROTECTED] wrote:
The issue number is 1734... I thought you
I have
not tested this feature, but i suppose it should work :
All my
current works are based on the J2EE 1.4 web services features, and more
precisely on the possibility to expose a stateless session bean as a web service
endpoint. Authentication, if you use a BASIC HTTP scheme, or SSL
I had a similar problem few weeks ago...
Somebody said that axis ant tasks don't take into account the inner
classpath elements. According to my tests, it does, but not for all classes
: it seems the main source java class is actually resolved from the nested
classpath element, but additional
prototyping projects, but i suppose it could be important for you to solve
them with the coming 1.2 release...
Waiting for news from you...
-Message d'origine-
De : Ephemeris Lappis [mailto:[EMAIL PROTECTED]
Envoye : mercredi 26 janvier 2005 18:59
A : [EMAIL PROTECTED]
Objet : RE: Noob : axis
update the issue with your
comments, i will take a look at them again.
thanks,
dims
On Wed, 26 Jan 2005 19:34:44 +0100, Ephemeris Lappis
[EMAIL PROTECTED] wrote:
The issue number is 1734... I thought you had forgotten it !!!
While we are getting out old things from the past : i had
wsdl2java.
Bill
-Message d'origine-
De : Michael Schuerig
[mailto:[EMAIL PROTECTED]]
Envoyé : mardi 11 janvier 2005 11:51
À :
[EMAIL PROTECTED]
Objet : Re: Document/Literal : bad part name in axis
server response
On Tuesday 11 January 2005 07:26, Ep
that...
if they do it !
Thanks anyway...
-Message d'origine-
De : Michael Schuerig [mailto:[EMAIL PROTECTED]
Envoyé : mardi 11 janvier 2005 11:51
À : [EMAIL PROTECTED]
Objet : Re: Document/Literal : bad part name in axis server response
On Tuesday 11 January 2005 07:26, Ephemeris
I don't use wsdl2java.
In Jonas, using the new (not so new) ejb 2.1 service endpoint features, i
just provide the wsdl (that is generated from the java endpoint interface),
and the ejb and webservices descriptors (for the ejb deployment). At
assembly time, Jonas produces the java stubs, the whole
have to put it in because that's the way
WSDL works):
wsdl:message name="reverseRequest"
wsdl:part name="parameters" element="impl:reverse"/
/wsdl:message
I'm not sure how to setup the WSDL with regard to responses.
If you look at http://www.n2soft.net/Services/HNDCA
/XMLSchema/
/operation
According to my reading of Emitter.getResponseMessage() that
should let you
control the name of the tag immediately below soap:Body.
Does that work?
Bill
Ephemeris Lappis wrote:
Hello.
I don't think the problem comes from the request format. First
PostScoreResult42/PostScoreResult
/PostScoreResponse
/soap:Body
It seems like a lot of overhead for one number but I've got a
feeling that the clients won't work unless you structure it
like that. I'm still experimenting though.
Bill
Ephemeris Lappis wrote:
Before i open
Before i open a bug, i'd like to have the opinion of experts !
All my last tests around document/literal style let me with troubles. To
start again with simple things, i have made a basic service to evaluate the
primary interoperability with my J2ME client. This simple service provides a
single
is nearly identical (Single java
Philippe object with getX()
Philippe methods instead of all unwrapped parameters directly).
Philippe
Philippe
Philippe Ephemeris Lappis a écrit :
Philippe
Philippe I'm not a SOAP expert ! I think i had understood
Philippe the difference between
Philippe
I have open a new bug report this morning (in France), with the a simple
example: AXIS-1734.
We will appreciate help...
Philippe -Message d'origine-
Philippe De : V D [mailto:[EMAIL PROTECTED]
Philippe Envoyé : lundi 20 décembre 2004 14:37
Philippe À : [EMAIL PROTECTED]
Philippe Objet :
Ephemeris Lappis a écrit :
Philippe
Philippe Thanks for your feedback. Bad news !...
Philippe I'd like to have a point of view from the Axis team
Philippe about this issue. I'm
Philippe not currently working a lot in web services
Philippe domains, but according to what
Philippe i've been reading
As i already said before, i'm not a soap expert, not at all.
Nevertheless, i think generating wsdl files from existing java code is an
easy way : wsdl syntax is not so friendly.
I known such a comparison is not always welcome : with CORBA we all first
write the services interface, using IDL,
As many people before i have the same problem with axis 1.2 to generate my
wsdl for javabeans or exceptions. I've been trying some of the solutions
that have been proposed on this list, such as adding complextype or mapping
tags, but the task failed with ClassNotFoundException, although the
Thanks for your feedback. Bad news !...
I'd like to have a point of view from the Axis team about this issue. I'm
not currently working a lot in web services domains, but according to what
i've been reading in this list and others, document/literal seems to be
often required (as in my case by one
19 matches
Mail list logo
