hi,
I think you can do it by using the simple authorization handler provided
by axis. (I think it is sufficient for your problems, it deals with wsdd
and checks the authorization detail for a particular method, some time you
may need to change the code a bit).
Check it out...:)
Regards,
Jeyakumar
Hi,
Axis can handle in and out parameters as header elements. The service method
is implemented as usual but the parameters are passed in the header. Try:
Let me know, if Axis generates proper WSDL for the service.
Thomas
> -Ursprungliche Nachricht-
> Von: Christians
Hallo
Mark,
Axis
can't load the plugable Provider. Probably Axis can't find the file containing
the name of the factory. Make sure there is a file named
org.apache.axis.deployment.wsdd.Provider in a META-INF/services directory
reachable from the classpath. A good place for the file is
WE
Chris,
I've been trying to find a way to specified explicit headers in a WSDD.
I want these headers to appear in the WSDL document axis generates for
my web service.
Is there any way to do this? Can someone point me to an example?
I haven't found a Java2WSDL option for this, so what I do is manual
Hi Anne, Dimuthu,
I would like to try this.
Do you know what method do I need to call at Axis Client to set this QName?.
My method name is updateProfile and in my server-config.wsdd, I have this
entry for my service
http://xml.apache.org/xml-soap"; >
http://xml.apache.org/xml-soap"/>
I'll work something up this weekend.
Davanum Srinivas wrote:
Danch,
We'd REALLY appreciate a bug report with a complete WSDL. So that we can fix the
problem with
complex schema definitions. (http://ws.apache.org/axis/bugs.html)
Thanks,
dims
--- Dan Christopherson <[EMAIL PROTECTED]> wrote:
wsdl
Hi,
I've been trying to find a way to specified explicit headers in a WSDD.
I want these headers to appear in the WSDL document axis generates for
my web service.
Is there any way to do this? Can someone point me to an example?
Thank you very much,
Chris
Danch,
We'd REALLY appreciate a bug report with a complete WSDL. So that we can fix the
problem with
complex schema definitions. (http://ws.apache.org/axis/bugs.html)
Thanks,
dims
--- Dan Christopherson <[EMAIL PROTECTED]> wrote:
> wsdl2java doesn't seem to work very well with more complex sche
Hi
I wrote my provider. But when I list the deployed services thru the axis admin page I get this error
Exception - org.apache.axis.ConfigurationException: org.apache.axis.deployment.wsdd.WSDDException: No provider type matches QName '{http://xml.apache.org/axis/wsdd/providers/java}MyProviderClass
wsdl2java doesn't seem to work very well with more complex schema definitions (like xCIL from
oasis.org). You might also want to take a look at recent threads regarding doc/literal - people are
working on making this work better, but there is a way to go yet.
This isn't necesarily a weakness spe
Thompson, Eugene wrote:
Is it that Axis provides a communication style (message) that isn't part of
the specs?
Yes, the Axis Message style is not part of JAX-RPC. However, there is a lot of
confusion about exactly what "message-style" means.
The WSDL spec defines "document-style" operations as
http://www-106.ibm.com/developerworks/webservices/wsdk/
http://www-106.ibm.com/developerworks/webservices
-Original Message-
From: Leo de Blaauw [mailto:[EMAIL PROTECTED]
Sent: Fri, November 14, 2003 4:43 PM
To: [EMAIL PROTECTED]
Subject: Re: WebSphere reading materials
Well,
I am sure
Title: wsdl2java returns invalid characters in wsdd and .java
I observed that whenever I do wsdl2java, the wsdd and .java files generated have invalid '>' character at different places. Am I the only one experiencing it? I didn't see any discussion around this issue. Is there a better way to g
in client-config.wsdd
You may have to rebuild axis with CommonsHTTPClient in order for CommonsHTTPSender to be built - I
had to, anyway.
Make sure you use the lates release of CommonsHTTPClient
-danch
[EMAIL PROTECTED] wrote:
I was wonder how to configure Axis to use CommonsHTTPSender, and
Keith Bohnenberger wrote:
Is this different than the "wrapper" element convention. It sounds like
the same thing.
I agree. We might not call it a wrapper, but it serves the same purpose. So if I
have two operations named process and validate, and they both take a
PurchaseOrder input message, my
Hi All,
Is it ok for a client to reuse a stub for many invocations
and in what scope(request[single thread], session,
application)?
If any, what are the implications?
My client/server both send and receive attachments by hand, be it that the service does not expose DataHandlers
Chris,
Thanks for your reply!
I found out why it went wrong: I did set up a client-config.wsdd and dropped it in the
same
directory as my client jar. Apparently, this is not enough. I need to explicitly
load the file
as EngineConfig and set it in my service. After that, my code works!
This
Hi, Dimuthu.
No it's not less sleep, or more coffee, or anything else :-).
Correct me if I am wrong, but I am under the impression that axis does not
use SOAP action at all when invoking a service.
If someone wants to use doc\literal service to have multiple operations he
has to explicity map the
Stuart,
I ran into the same problem yesterday. It seemed to happen when a service
implement method declares that it throws a service-specific exception (e.g.,
public void process(PO po) throws PoException). A Java2WSDL bug, apparently.
Workaround (simple, but not practical): remove service-speci
The article that you mention uses the axis "wrapped" programming style
with the Axis CVS version which supports castor serialization. They are
using document/literal web services. Keep in mind that "message",
"document", and "wrapped" are program styles not communication styles or
WSLD styles. A
Well,
I am sure there will be documents related to that, but since we use axis
with websphere/wsad 5
i havent found many of interest. I just posted the links I did because a lot
of questions are popping
up here later for help on how to deploy this and that on websphere etc..
greetz
Leo
- Ori
> One of the reasons standards exist is to avoid vendor lock-in.
> It is a good architecture goal to avoid vendor lock-in and
> write code to
> the specs/standard apis.
Absolutely. For the implementation, I would agree whole-heartedly. I guess
where I'm missing the point is where you say ...
Keith,
You can write a JAX-RPC/Axis handlers to enforce this. For example, you can extend
SimpleAuthorizationHandler. Patches are welcome as well
(http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/SubmitPatches).
-- dims
--- Keith Bohnenberger <[EMAIL PROTECTED]> wrote:
> One of the
Axis doesn't contain anything out of the box to enforce method level
security.
You would need to look at vendor products or roll your own solution.
/Chris
-Original Message-
From: Pablo [mailto:[EMAIL PROTECTED]
Sent: Friday, November 14, 2003 7:27 AM
To: [EMAIL PROTECTED]
Subject: Met
One of the reasons standards exist is to avoid vendor lock-in.
It is a good architecture goal to avoid vendor lock-in and write code to
the specs/standard apis.
Lets say you didnt know about axis and you implemented a bunch of web
services in Java using some other SAAJ/JAX-RPC implementation. A f
Is this different than the "wrapper" element convention. It sounds like
the same thing.
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Friday, November 14, 2003 8:42 AM
To: [EMAIL PROTECTED]
Subject: Re: How to define document/literal service with multiple
ope
You need to write a handler to do this.
At 07:27 AM 11/14/2003, you wrote:
Hi
Suppose my web service has some methods:
methodA
methodB
methodC
How can I do authorization by methods?
For instance:
methodA and methodB can be called just if the user is in an administrator
role, methodC just for
Leo,
Thanks for the link. Can you provide some more pointers to Web
services-specific information? Most of these links were focused on
traditional J2EE stuff, and not on Web services.
Thanks,
Anne
At 03:34 AM 11/14/2003, you wrote:
To all interested,
Below is a link to all sorts of IBM websph
Per the SOAP spec (SOAP 1.2 is clearer than SOAP 1.1), and intermediary is
a full SOAP node, not a handler.
You can use WS-Addressing or WS-Routing to indicate the routing path in
SOAP headers. WS-Addressing supercedes WS-Routing.
Anne
At 10:26 PM 11/13/2003, you wrote:
Hi Bob,
I would like t
According to the WS-I Basic Profile, a Doc/Literal service is required to
have a unique wire signature for each operation. What that means is that
the child element of the soap:Body must have a unique QName. This
uniqueness should be sufficient information for dispatching purposes. The
QName do
Title: Message
in the
client-config.wsdd :
your
class extends org.apache.axis.transport.http.HTTPSender
see the
example in the attached file.
-Message d'origine-De :
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 14 novembre 2003 13:54À :
[EMAIL PROTECT
Hello,
the problem we have detected is as follows:
In the WSDL a field is described as
which means that null is not allowed for that value. But 0 certainly is.
If somesome send a soap message with the value of this field set to null, i.e.
an empty element value then Axis
implicitly tr
I was wonder how to configure Axis to use CommonsHTTPSender, and also how can I
configure the HTTPClient from Axis?
I need to do the following connection: Client --(http)--> Proxy --(https)--> WebService
The HTTPSender doesn't seem to support this, but the commons HTTP client seems to do.
wbr
> Also, I'd like to keep my web services portable to different JAX-RPC
> implementations, so I try to avoid Axis-specific features
> (e.g., Message-style
> services.)
>
Just curious, but why? Are you constructing a service that you are planning
to sell or that will need to be installed in man
Hi
Suppose my web service has some methods:
methodA
methodB
methodC
How can I do authorization by methods?
For instance:
methodA and methodB can be called just if the user is in an administrator role,
methodC just for users with a manager role.
Is it possible to do so? Authorization by method
Gloria - At what step are you attempting to capture the message context?
MessageContext is *only* present and valid while the client is
processing the SOAP method call. Until the call method is triggered by
ClientMain, a message context doesn't exist. By the time control is
returned to ClientMai
Gloria -
Without looking at both your client and server side configuration, it is
hard to tell exactly where the example went awry. It seems like you
have not followed the configuration steps for the SimpleSessionHandler.
I didn't post the full example. The e-mail thread assumed that the user
w
Hi,
I have searched in this mail list and tried to apply the possible solutions, however,
I failed to
find session id in the client side soap message.
What I did:
(01) set scope to be session in the wsdd file
(02) set setMaintainSession to be true
(03) include SimpleSessionHandler at both serve
Hi,
I'm new to AXIS and I tried Example6 for a stateful service (i.e. using session). It
worked fine.
Then, I expanded the example to contain 2 stateful services, i.e. now I have:
ServiceA with method a() and b()
ServiceB with method c() and d()
I have configured them in the same way (both in
Hello Dimuthu,
On Friday, Nov 14, 2003, at 04:26 Europe/Ljubljana, Dimuthu Leelarathne
wrote:
Hi Bob,
I would like to comment on the following line.
CLIENT ---> INTERMEDIARY ---> ENDPOINT
Are you talking about the "INTERMEDIARY" mentioned in the SOAP
specification?
Yes, as the theory says,
Hello Wolfgang,
On Thursday, Nov 13, 2003, at 13:29 Europe/Ljubljana, Wolfgang
Vullhorst wrote:
Hi,
am a bit confused by some of your statements. Perhaps you can help
me with
that...
Of course, I will try to.
Wolfgang
Borut Bolcina [mailto:[EMAIL PROTECTED] wrote:
Hi, again
since I had no
Title: WebSphere reading materials
To all interested,
Below is a link to all sorts of IBM websphere documentation reachable from this one link, for those interested.
As i see a lot of technical websphere questions pop up lately on this list, and this is not really the list to ask those:
htt
I have created a service and successfully deployed. At client side, I
created a ClientMain.java
which only contains a "main" method for the purpose of testing. I tried to
use
"MessageContext.getCurrentContext()", but I always get
NullPointerException.
Does MessageContext only exist with the
Title: RE: Install/Deploy Axis 1.1 under WebSphere 5
Hi,
I have just confirmed my requirement,
we wanted to have SOAP server at web server side, which will be using IBM HTTP Server,
I remembered when we deployod Axis into Apache Tomcat, we only need to modify one configuration file, server
44 matches
Mail list logo
