Could you try with a real implementain class on the client side . Just
mock up a class on the client side that represents person and try to
deserialize the respone to it. If it fails try using the beanserializer
and beandeserializer factories from axis with the mocked up class. This
way you wou
Yeah, that still fails with it on...
I just cant figure out why I cant seem to get this down on the client, plus
I would like to be able to receive it as its actual type - which in this
case is "Person" (interface). We use dynamicProxys for the actual class so
I dont really have a real implementa
Hi
Is there are a reason why you have commented out the call to
client.registerTypeMapping in your client program . This surely will
fail since there is no deserializerfactory registered for Person. Can
you run the code with the typemapping registered. You could also set the
return type to
Hello all,
I am having a super frustrating problem with deserializing an object in
Axis.
It says it cannot find the "deserializer for {xxx}YYY". I can see in the
TCPMonitor though that it seems to be working correctly. I have a custom
serializer and deserializer that I am using. I have tried s
Can anybody confirm this?
>From what I've been reading on the 'net and from what I'm experiencing,
Class-Path entry in the manifest.mf file inside of a WAR file doesn't work
correctly for Weblogic 6.1 (I'm using sp4), nor does it work for early
versions of 7.0 (I don't have 7.0, so I don't know).
hi:
I changed the sample code of Encoding, and added another class(DataNew) to
the class(Data).
It works fine - can serialize and deserialize correctly.
Class A{
Class B;
}
But after I changed the class(DataNew) to DataNew(array),
Class A{
Class B[];
}
Hi Folks,
I have a vague rememberance of somebody applying a patch for
ref="schema" and adding a new type called Schmea in the types of axis.
I remember seeing some thread in the dev list.
Please have a look at that.
Thanks
Kamesh
-Original Message-
From: Vidyanand Murunikkara
Sent:
It is becoz in the WSDL below there is a element that is a ref to schema
element. To my knowledge that is not supported in Axis.
Vidyanand.
-Original Message-
From: Marshall Greer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 12, 2002 2:13 PM
To: '[EMAIL PROTECTED]'
Subject: Having
Seems to me that since AxisServlet is such a key component, we would all
be best served by keeping it as thin and reliable as possible.
Since all config is stored in external repositories, seems like this
type of info would be better served up from a servlet like
AxisInfoServlet,
If we are concer
Hello Folks,
I would suggest an another alternative how about using XSL Stylesheets
and then doing a XSL Transformation. Thus we need not need extra stuff
other than the xalan stuff. SO that the Axis Servlets would just
generate the XML tags and then we pick up an xsl stylesheet that applies
the T
Possible Axis bug?
I have a class Parent with a method:
public Child[] getChildrenAsArray()
With a regular bean (de)serializer, I was always getting:
java.io.IOException: java.lang.ClassCastException:
[Ljava.lang.Object;
at
org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.ja
I believe that IBM WSTK provides a preliminary implementation of WS-Security
on Axis.
Anne
> -Original Message-
> From: Joshua Gramlich [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 13, 2002 10:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: WS-Security and Globus
>
>
> Yeah, that's pr
To work with session scope in a .NET client, the client must be able to
accept a cookie. All you need to do is to add a CookieContainer to your
service client class. Use the following code (C#) :
some.url.of.service.someService myService = new
some.url.of.service.someService() ;
myService.Coo
Hi Klaus,
maybe we can help each other
to configure the session on server-side is rather easy I think (I can just
think because actually I didnt get it working since now, because of the
client side): Just add the line
to the service-description in your server-config.wsdd. That should be
ever
Hi Sebastian,
i'm new to axis an i'm currently working at this problem too.
java org.apache.axis.wsdl.WSDL2Java --deployScope Session
writes
to deploy.wsdd - but it seems that it hasn't any effect.
in my client i do
MyServiceLocator sl = new MyServiceLocator();
sl.set
I don't know really - because I haven't implemented session handling yet.
Maybe this (other postings on this list) will help you:
http://marc.theaimsgroup.com/?l=axis-user&m=102881701000594&w=2
and
http://marc.theaimsgroup.com/?l=axis-user&m=102890135713613&w=2
and
http://marc.theaimsgroup.com/?
Yeah, that's pretty much what I'm looking for. That paper you
referenced...well, that's pretty much how I found out about WS-Security. I
found it a few days ago and was hoping that someone had done a cursory
implementation.
I may end up having to try to extend Axis, but I'm hoping to not have to
Hi Pascal,
thanks a lot and thousand times more and many greetings to Karlsruhe from
Hamburg! That was exactly that kind of explanation that I needed. Of course
I saw this code in the samples, but because of the missing decription I just
did not understand and did not know how to convert it to my
Cedric,
Thanks again. What I was doing wrong (orginally and then compounded the
problem because of it) was that my holder was not 'implementing holder' from
the axis classes. With this everything works fine.
Thanks for all you're help,
Brian
-Original Message-
From: Cédric Chabanois [ma
Hmmm... Uncle Bill bites me in the @ss again! |-) Who woulda thunk the Java
is not really Java when it comes to Windoze?! My problem is on a NT server machine.
I tried the same thing on a Linux machine, with the same .jar's (but a set of
JDK 1.3 jars for Linux, obviously) and things wor
> soapSrv.addParameter("userId",org.apache.axis.Constants.XSD_STRING,
> javax.xml.rpc.ParameterMode.IN);
> soapSrv.addParameter("requestContext",
> new QName("ta:RequestContext"),
> javax.xml.rpc.ParameterMode.INOUT);
>
Cedric,
Thanks for you're help,
This is my current scenario;
The WSDD has;
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";
xmlns:ta="http://www.fineos.com/XMLSchema/ta";>
http://www.fineos.com/XMLSchema/ta"; mode=
Yes, you need an Holder.
This is not axis specific : See JAX-RPC spec (4.3.5)
You will not need to provide a specific serializer or type mapping for the
holder.
Just provide serializer/deserializer and type mapping for your custom type.
You will also need to specify that your parameter is IN/O
I hadn't actually provided a holder. But let me get this straight. I need to
provide a holder in order that Axis understands that the type is OUT/INOUT.
If I provide this handler do I then need to provide a TypeMapping and
Serializer that will understand that it should use the 'value' of the holder
Hi Sebastian,
you don't need "deployment on the client-side".
If you want to access your webservice in a static way, you could use the
wsdl2java tool to generate a client-side "static invocation interface"
rather than your implementation of a "dynamic invocation interface". That's
a kind of "proxy
Hi there,
I'm using Axis 1.0 and I set up the server. It is running and a normal small
client is able to invoke the methods. Also Serialization/DeSerialization of
JavaBeans works perfectly.
I wrote the client, as it is described in the userguide:
Service service = new Service();
Call call = (Call
I use IN/OUT parameters for beans and arrays but I never tried with custom
serializer/deserializer.
But I thought providing a simple Holder class for the type and declaring the
parameter as OUT or INOUT in the wsdd would be enough.
What did you do exactly ?
Cédric
> Hi,
>
> I thougt I would r
Hi,
I thougt I would re-send this just in case someone that has used
serializers/de-serializers mised it.
Has anyone tried to use a custom serializer/deserializer with INOUT or OUT
parameters. I have it working fine for IN parameters but INOUT and OUT
parameters do not seem to be returned from th
If you use jdk 1.4 their might be a problem with loading javax.* classes.
May be you have to put them in a common dir of you server, or in the jre/lib/endorsed
dir.
Just a thought.
>>> [EMAIL PROTECTED] 13.12.2002 10.43 Uhr >>>
I use Axis as both a client and server.
As a web service engine
I see!
No ideas re WAR, EAR, classpath etc.
However, have you tried making your MDB a straight JAX-RPC client?
I've never used Axis on the client side, and (other than wrapping
your call for you to look a bit more business-like) I'm not sure
what value it adds. This is probably a reflection on my
I use Axis as both a client and server.
As a web service engine, I use Axis to basically map a web service to a
stateless session bean. This is where the Axis WAR has to be able to
access the EJB. If this is all I wanted to do, everything would be
fine... because that more or less works.
Howev
Hi Michael,
May I ask why the EJBs need to see Axis? We use Axis in WLS6.1sp4
with no problems, but we use it to provide a simple facade to a
Stateless Session Bean. That is, we expose our business methods
from the bean and have a thing POJO which Axis calls. This POJO
is responsible for understan
But I don't want the JARS in my classpath... that's the whole point of
trying to package them into the EAR file.
If I package the JARS as part of an AXIS WAR file, then AXIS can see my
EJBs however the EJBs can't see access. I assume I could somehow
reference these WAR JARS in the manifest file
33 matches
Mail list logo
