Hi,
I traced this exception back to the fact that the DocumentBuilderFactory
returned by org.apache.axis.utils.XMLUtils.InitDOMFactory() is
weblogic's version of xerces that does not seem to be compatible with
axis. I had to hardcode the factory to an instance of xerces2.0's
implementation class
this is a known bug in beta2. try one of the more recent nightly builds
Chaudhri Rohit-CRC037 wrote:
> As specified in the documentation, I used the name="allowedMethods" value= "method names" /> tag to specify the methods
> that I should be exposed in the Web Service. But still after I deploy
If you look at /webapps/axis/WEB-INF/web.xml , you can see
that any request to an url of the form axis/services/* is handled by the
class org.apache.axis.transport.http.AxisServlet. The AxisServlet in
turn gets info
about the deployed services from the file server-config.wsdd
Vikram
Nuno Guerrei
Hi,
I guess you are using alpha3. Try out with a recent nightly build. There
is improved support for arrays and Lists now.
All Lists are now deserialized as Object[]. Even if your sevice method
returns a Vector, on the client side you will receive it as an Object[].
So the client code should loo
Rich Scheuerle
> XML & Web Services Development
> 512-838-5115 (IBM TL 678-5115)
>
>
> Vikram Rayabhari
> com> cc:
>Su
Hi,
There seems to be a bug in ArraySerilizer when a list containing objects
of different classes is serialized. The arrayType attribute is being set
to the type of the first element in the list and not to xsd:anyType as
would be expected.
Could someone please clarify?
thanks
Vikram
oops... its BeanDeserializer that throws the exception. The serializer
seems to work fine.
Vikram Rayabhari wrote:
> I have a property in a bean that is declared as
>
> private MyInterface intf;
>
> This property is always null and will never change in my application.
I have a property in a bean that is declared as
private MyInterface intf;
This property is always null and will never change in my application.
Currently the BeanSerializer is very strict ie it expects a type mapping
for MyInterface even though the value is null. This means that I will have
to wr
me if this fixes your
> problem.
>
> Thanks,
>
> Rich Scheuerle
> XML & Web Services Development
> 512-838-5115 (IBM TL 678-5115)
>
>
> Vikram Rayabhari
> com>
Hi all,
Does SOAP support overloaded methods??
If yes, does the current version of AXIS support them?? if yes, how
does a client differentiate one from the other??
If no, what is the best way to tackle the issue?? I already have an
API that contains overloaded methods and I want to expos
Hi,
I have a wrapper service that has a session bean. The service
class declares a method
public java.util.List myMethod(java.util.List myList) {
return mySessionBean.myMethod(myList);
}
Calling this method resulted in a java.io.NotSerializableException..
The bean was deployed on WebSphere4.0
Hi Graham,
My first guess is you have a version mismatch in one of the jars - log4j
or wsdl4j.
Vikram
Graham Glass wrote:
Hi
guys,
Im
running AXIS alpha3 under tomcat 3.2 and cant seem to get a simple sample
working.
When
I start up tomcat and then try using any AXIS functionality, I g
12 matches
Mail list logo