Hi
I was using this method and it so happened that I had 2 WS-Security
headers for one actor.
I thought this method will catch this . It is not doing it.
- ravi
Hi Robert,
If you go to the bottom of the page of "Bug list" at apache and query for
bug 23012 you'll find sample doc\literal service that doesn't use wsdl.
The sample is removed from the bug list but it is still in the database.
I am yet to find time and do it again using wsdl :-).
I have also
yap; even the JSR109 (Webservice's for J2EE) spec allow espose only the
stateless EJB as web services.
Does axis supporting statefull beans as well.
Srinath
On Thu, 2003-12-04 at 21:24, Ekbote, Niranjan wrote:
> Has Axis started supporting "Stateful" session beans? I thought for the EJB
> prov
Can someone point me to the source code for a document/wrapped style
service?
Thanks.,
Somebody can tell me how can I change the default
timout a web service has? I tried the following but didn't work:
YAESystemServiceLocator locator = new
YAESystemServiceLocator();
YAESystem system =
locator.getYAESystem(myURL);
((org.apache.axis.client.Stub)
system).setTimeout(myTimeout);
Hello Group,
I am using axis as web service client with the following ...
Tomcat : 3.3.1a
JDK: 1.3
I am able to call web service properly and also getting the response from the
service. I can see the response xml in axis.log file since I have turned debug on for
Hi, I stumbled upon this problem just now, and instead of creating a
serializer and deserilazer, I switched the variable to int, worked
alright. Since the original message is more than 1 year old, anybody
knows if a Character serializer has been implemented?
Francisco Areas Guimaraes
-Origin
Please try 1.2 Alpha. www.apache.org/dist/ws/axis/1_2alpha/ if you can replicate the
problem with
this, open up a bug report with your sample code.
thanks,
dims
--- "Fernandez Martinez, Alejandro" <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> I am having a problem with a service. It throws an exce
Title: Non-RemoteException serialization
Hi guys,
I am having a problem with a service. It throws an exception -- which does *not* extend AxisFault or RemoteException -- and I want to receive it on the other end. In my understanding, all I have to do is call AxisFault.getCause() to get it.
Hi!
There are two ways how you can deploy a JAX-RPC handler.
1) use in the service definition
2) wrap it using JAXRPCHandler
What's the difference?
It seems that all handlers that were deployed using handlerInfoChain
are called between the global chain and the SOAPService (on the server
side),
On Thu, 2003-12-04 at 16:59, Rodrigo Ruiz wrote:
> Here it is my little proposal (I'm not saying it is easy or fast to
> implement ;-) )
>
> For each stateful EJB, create two services:
[snip]
>
> My two cents ;-)
> Rodrigo Ruiz
>
Very interesting, indeed.
Since I'm not aware about the spec fo
Guys,
I'm trying to use axis with castor.The way i do it is
1. Define a wsdl which imports the schema of data packets which go back and
forth(All files are included as attachment in this mail).
2. Generate java stubs and server side code out of it.
3. Generate castor classes out of sc
Keith Hatton wrote:
Thanks for your ideas, Rodrigo. I am going to sleep on it.
I like the idea as it forms a design pattern and as you say, allows the client to take a more standard approach to the service, and also because over the past few days I have discovered some of the delights of working
Thanks for your ideas, Rodrigo. I am going to sleep on it.
I like the idea as it forms a design pattern and as you say, allows the client to take
a more standard approach to the service, and also because over the past few days I
have discovered some of the delights of working with stateful EJBs
If you look at the providers source code, you will see that RPCProvider
is a subclass of BasicHandler, and so, it implements the Handler interface.
This means that you should be able to add your custom provider to the
end of your service chain, and get the desired behaviour. Can someone
confirm
Keith, have you considered a refactoring on your web service interface?
You could extract some ideas from OGSA (Open Grid Services Arquitecture).
Here it is my little proposal (I'm not saying it is easy or fast to
implement ;-) )
For each stateful EJB, create two services:
- A "Factory" service
Title: RE: Using handlers to look at method parameter values
Thanks a LOT!.
I think I can use this, maybe extend the RPCProvider class and override the invokeMethod
method, and I will have access to the method and all the method Parms.
Now I am trying to figure out how to let my service use
Howdy all-
Apache SOAP supported Stateful EJB providers via namespace re-writing. Recall
that the SOAP operation can be namespace prefixed. What Apache SOAP does is
it changes the URL associated with the operation so that it is unique for
each session. Some say it's sleezy but hey it works
I have a first config which works correctly :
TOMCAT_HOME/webbaps/myservlet/WEB-INF/classes/client-config.wsdd
TOMCAT_HOME/webbaps/myservlet/WEB-INF/lib/axis.jar (without
client-config.wsdd)
But next, I need to use the axis.jar elsewhere in tomcat so I need to put
the axis.jar in TOMCAT_HO
Hi Rodrigo,
I have to admit, I haven't tried two clients, but can't see any reason why that
shouldn't work.
The EJB in question does a search on a database and pages the result set to the
client, that is how I know that the statefulness of the EJB is exposed successfully
through Axis.
>> perh
>From Axis User Guide
Standard mappings from WSDL to Java
xsd:base64Binary byte[]
xsd:boolean boolean
xsd:byte byte
xsd:dateTime java.util.Calendar
xsd:decimal java.math.BigDecimal
xsd:double double
xsd:float float
xsd:hexBinary byte[]
xsd:int int
xsd:integer java.math.BigInteger
If your service uses RPC style, you may find something in the code of
RPCProvider. It should contain the code to obtain the argument values array
HTH,
Rodrigo Ruiz
Saravanan Markandeyan wrote:
Thanks for your response.
I tried looking into the MessageContext, I am able to get the method
name,
Where can I find a list of all the Java classes
(String, Integer, etc.) that are "natively" supported
by Axis (no bean or custom deserialization required)?
Gary
__
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
Title: RE: Using handlers to look at method parameter values
Thanks for your response.
I tried looking into the MessageContext, I am able to get the method name, the parameter types and names,
but looks like I won't be able to get the actual value. I am going to try the deserializer route,
sorry!!!
of cause i meen http!!
Harry
Am Don, den 04.12.2003 schrieb Christer Holmér um 16:21:
I guess you mean HTTP, not HTML. Thank god for three and four letter acronyms...
Regards,
Christer
-Original Message-
From: Harald Pollak [mailto:[EM
Hi Keith, some time ago I did some tests on maintaining more than one
session from the same client, but I was unsuccessful. How do you manage
to maintain two instances of your EJB web service? I only managed to
maintain one instance, as I couldn't get two separate sessions :-(
BTW, perhaps inva
Hi all,
I have another issue with stateful session EJBs.
In order to manage resources on the server, I want my client to have more fine-grained
control on the lifecycle of stateful EJBs. I thought I would be able to do this by
exposing the remove() method as a Web Service, but Axis cannot find
Is there any performance to be gained by opening a Service object in my web service client code and then keeping it shared in JNDI?
Alternatively each time my client threads need to access a web service they would create the service and then create the stub binding class on each invocation.
most time ( i think mor than 80 % ) webservice communication is through html and html also produces a header ( you can also see the servlet as a spezal kind of handler ).
So i think handler things not needed to descriped in WSDL.
Am Don, den 04.12.2003 schrieb Yogesh Pant um 14:31:
How does html header come into picture of web service communication?
Harald Pollak <[EMAIL PROTECTED]> wrote:
as you said:Handlers providing a addinal layer to the webservice, you also don't descripe the HTML-Header in the wsdlAm Don, den 04.12.2003 schrieb Yogesh Pant um 14:12:
The header
Well, IMHO if Axis allows session scope for its web services, it should
also allow some session lifecycle support. Otherwise, what is the point
in allowing this scope?
Just an opinion ;-)
Rodrigo Ruiz
Harald Pollak wrote:
as much as I have understood:
Webservice are from ground stateless and d
as much as I have understood:
Webservice are from ground stateless and don't support stateful session beans and i think this is independent from the framework and produkt.
Maybe there are some produkts with support for this, but i think there is no point in spec. about it.
regards
Harry
A
Well, I didn't see anything saying that only stateless EJBs were supported ... and
stateful beans do work if the client maintains a session, and the server scope is set
to session.
Keith
-Original Message-
From: Ekbote, Niranjan [mailto:[EMAIL PROTECTED]
Sent: 04 December 2003 15:25
To:
Has Axis started supporting "Stateful" session beans? I thought for the EJB
provider, you can only work with "Stateless" session beans.
-Original Message-
From: Keith Hatton [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2003 10:21 AM
To: Axis-User (E-mail)
Subject: Bug? Stateful
I
guess you mean HTTP, not HTML. Thank god for three and four letter acronyms...
Regards,
Christer
-Original Message-From: Harald Pollak
[mailto:[EMAIL PROTECTED]Sent: den 4 december 2003
14:37To: [EMAIL PROTECTED]Subject: Re:
Authentication - Could anyone h
There's an implementation of WS-Security's UserNameToken Profile and X509Profile at
http://wss4j.sf.net/ (get the code using anoncvs access)
-- dims
--- Aaron Hamid <[EMAIL PROTECTED]> wrote:
> You'll have to get some real developers to answer on that, but the
> only support I've seen is for bas
You'll have to get some real developers to answer on that, but the
only support I've seen is for basic auth. That's not the fault of
Axis - the last I checked WS-Security was far from done and in general
security for web services has not been finalized. You can of course
build security at the
Thanks for the help Aaron. Would it be correct to say that the only form
of supported security for web applications that is part of the axis
implementation is for servlet container security of the type that I have
described in my original message?
-Original Message-
From: Aaron Hamid [mail
The session timeout is set as ...
30
>
> From: Harald Pollak <[EMAIL PROTECTED]>
> Date: 2003/12/04 Thu AM 07:33:39 EST
> To: [EMAIL PROTECTED]
> Subject: Re: Operation Time Out Issue !!
>
> is there a sessionTime out set in Tomcat Servlet Container?
>
>
> Am Mit, den 03.12.2003 schrieb [EMAI
I had a similar problem before. The reason
for my problem was that, while returning the date from my web method I was
actually returning an instance of java.sql.Date and not an actual instance of java.util.Date.
So if you are returning dates, just make sure that you are not just casting jav
Hi
How can I workaround the following problem?
The WSDL of my Java service defines an entryDate as follows:The entryDates Java representation is java.util.Date.Axis sends a SOAP response containing the entryDate as follows: 2003-12-01Thanks,
Silvano
Gesendet von http://mail.yahoo.de
Schnel
I can't answer why the admin app would be failing. But if you want
application-level security you are basically on your own. You can try
to use the ws-security package, or simply build client and server
handlers which know how to generate and decode your form of
authentication (in my case, I
as you said:
Handlers providing a addinal layer to the webservice, you also don't descripe the HTML-Header in the wsdl
Am Don, den 04.12.2003 schrieb Yogesh Pant um 14:12:
The header element is a part of SOAP message. As per web services specification, message description should be inclu
a handler on the clientside written by you and used by the client programmer - It's allso usefull for hiding password encryption ...
and its a thing of reuseable code.
Harry
Am Don, den 04.12.2003 schrieb Tony Vieitez um 14:08:
OK, so if you have a container managed username and pass
OK, so if you have a container managed username
and password protected web service, and the client classes are generated from
the wsdl, if the person implementing the client code
knows the usernmame and password, what would be the
code for implementing access to the web service?
Also,
The header element is a part of SOAP message. As per web services specification, message description should be included in the wsdl document.
Handler is a mechanism used by Axis to provide an additional layer for processing incoming/outgoing message. In any case wsdl should be a complete descrip
I was not aware of the "special" client-config.wsdd that people
replied about, but here are two equivalent (I believe) ways to
programmatically deploy a client handler:
1) register handler chain directly:
Class clazz = MyHandler.class;
Map config = new HashMap();
QName[] headers = null;
Handler
as i have understood:
The handler is a thing befor the WS ( not part of it ) and the WSDL describe the WS - so elements only used in handler shouldn't and couldn't be described in Webservice, so you can only tell your opposit what to do in document the webservice in hardware ways ( email, lett
Do you have placed the Client-Config.wssd file in the right directory?
it should be in the root dir of your application.
Harry
Am Don, den 04.12.2003 schrieb [EMAIL PROTECTED] um 12:13:
I've tried your solution and I get this error :
org.apache.axis.ConfigurationException: No engine configu
Hello ppl,
I have got a custom authentication handler. It authenticates the incoming message very well.
My problem is that the generated wsdl has no mention of header elements at all. HOW DO I ACHIEVE THIS?
Do I need to configure the deployment descriptor a little bit more?
Please help.
Tha
Ok, client-config.wsdd was not in the rigth place !
Everything works fine now : it's so simple !
Thanks a lot for your help !
Valerie
Harald Pollak <[EMAIL PROTECTED]> sur 04/12/2003 13:24:37
Veuillez répondre à [EMAIL PROTECTED]
Pour : [EMAIL PROTECTED]
cc :
Objet : Re: Réf. : RE: Clie
is there a sessionTime out set in Tomcat Servlet Container?
Am Mit, den 03.12.2003 schrieb [EMAIL PROTECTED] um 23:39:
Hi Group,
I am using axis 1.0 production releas for publishing web services as well as consuming them at the client side. All works well when I am using JBOSS 3.0.4 and
Hi folks,
I have been facing a problem while using soap RPC attachment. Let me
summarize as follows:
1) Create a header
2) Create a body that contains information about an operation. The operation
or method takes javax.activation.DataHandler as an input
3) Create envelope by combining header and
Hi
How can I workaround the following problem?
The WSDL of my Java service defines an entryDate as follows:The entryDates Java representation is java.util.Date.Axis sends a SOAP response containing the entryDate as follows: 2003-12-01Thanks,
SilvanoGesendet von http://mail.yahoo.de
Schneller al
Hi Tony,
If you wanted to use application level security, maybe try using
ws-security (encryption and signatures) using handlers in axis. You will
find quite a few links on
this in the axis mailing list.
You may have to design the authentication protocol and then implement this
using ws-security.
H
Did you add a handler to your classpath?
My example handler is:
package com.jankester.axis.handler;
import org.apache.axis.*;
import org.apache.axis.handlers.BasicHandler;
import org.apache.log4j.Logger;
public class SOAPMonitor extends BasicHandler {
private static Logger logger =
I've tried your solution and I get this error :
org.apache.axis.ConfigurationException: No engine configuration file - aborting!
Which file is missing ?
Valerie
"Jan Kester" <[EMAIL PROTECTED]> sur 04/12/2003 11:38:55
Veuillez répondre à [EMAIL PROTECTED]
Pour : <[EMAIL PROTECTED]>
cc :
Hi
I asked a question on this subject recently, but I don’t
think I asked it clearly enough, because the answers I got back, although
helpful, didn’t quite give me the answer I was after. Now I understand a
bit more about authentication I can (hopefully) formulate my question a bit
more
The client-config.wsdd has to be in the client's execute classpath.
In here you can define a handler. There are plenty of examples on internet.
My client-config.wsdd has:
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd
Hello
I have a simple servlet (not a web service) deployed on tomcat, it works
like a normal servlet : receveiving http request and sending http response.
But this servlet also have to invoke an axis webservice to get some
information : no problem with that : it works !
The problem start here : I
Hi
the client-config.wsdd is located in your axis.jar.
You have to change it inside the jar (on the client side).
it looks like this:
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
here you can register a handler, like the
you can write own handlers and put it into the chain for the webservice.
This handler kann check the authentication and give access to the WS or rize a AxisFault
this is the simplest way to do such things.
Harry
Am Don, den 04.12.2003 schrieb Tony Vieitez um 11:08:
Hi
Hi all,
I met a problem using uddi4j to access jUDDI. The error message is as
following.
Save Biz Example ***
1. Get an authorization token ---
TransportFactory: Using transport
name:org.uddi4j.transport.ApacheAxisT
63 matches
Mail list logo
