The AxisServlet tells me that my service is available, and my test case
uses the ServiceLocator that was generated, which appears to have the
correct URL, but my client test case keeps getting a SOAP fault of:
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.NoService
faultSubcode:
faul
I may be doing something wrong here.
I have an existing set of schemas from which I use Castor to generate
JavaBeans. I then specify a typeMapping in the WSDD to use Castor
serializers.
I need these schemas available to the WSDL for message definition, however,
I do not want WSDL2Java to try and
Well, if you are plugging in your own serializers, then you certainly won't
be interested in the data types generated by the WSDL2Java process. Those
are designed to work with the BeanSerializer.
David,
I'm about to do this myself, with the exception of using my own set of
CastorSerializer classes so that it will look for my custom mapping. So
I'm very interested in this topic. I wonder if the encodingStyle should be
somthing else?
Have you confirmed that the (un)marshalling process is
Hmm. Well, I'd recommend starting with the following:
SOAP specs
WSDL specs
JAX-RPC spec
These documents will answer about 90% of the questions about web services
that you will ever have. The other 10% will come from the Apache Axis
documentation and this list.
Good luck.
Good question. I know that the JAX-RPC spec defines how the WSDL <-> Java
mapping should take place. However, I can't really tell if the WSDL2Java
process in Axis uses the serialization framework and could be configured to
use a different set of factories. My guess would be no. Source code
gene
In JAXB, you can specify that your bindings are either written in your XSD,
in another namespace, or placed in an external binding file. I would
certainly opt for the later. However, the current JAXB requires that you
specify your global bindings in your XSD if you want to use the extensions
that
Yes, you could write a JAXBSerializer, JAXBDeserializer,
JAXBSerializerFactory, and JAXBDeserializerFactory. Then, map your QNAME
to your Java class, specifying these factories, in the typemapping section
of your WSDD.
However, you might want to consider using Castor or JiBX instead, and write
se
Axis is an implementation of JAX-RPC, so the JAX-RPC specification is where
you will learn about how this type mapping is to take place. I seem to
recall that the underscore prefix had something to do with not explicitly
defining a name for a complexType, but I could be wrong.
Steve Maring
Writing a Castor mapping.xml is not the problem. Doing that externally is
fairly trivial. The problem seems to be that the current CastorSerializer
and CastorDeserializer do not look for any kind of mapping file in the
classpath to allow for custom mappings. The process of registering
factories
Thanks for the envite Dims. If I can figure out how to write a
JiBXSerializer, JiBXSerializerFactory, JiBXDeserializer, and
JiBXDeserializerFactory, then I will certainly do that. The Castor ones
look to be pretty straight forward and don't seem to ask for any SOAP
message context data. However,
1) unjar the Axis.jar
2) remove the log4j.properties in the root
3) jar up Axis.jar again
4) put YOUR log4j.properties in the classpath
Cheers
Steve Maring
More specifically, my JavaBean uses the BeanSerializer. It is dying on
line 143 of BeanSerializer with a NullPointerException:
143>String encodingStyle = context.getMessageContext().getEncodingStyle
();
Which would certainly imply that the serialization framework cannot be used
outside of th
I'm trying to manually serialize a JavaBean with the serialize method in
org.apache.axis.encoding.Serializer. The does anyone know anything about
the attributes parameter? It does not like me passing it null.
serialize(QName name, org.xml.sax.Attributes attributes,
java.lang.Object value, Serial
I've already let out a few primal screams over this one! I cannot find ANY
good references for how to use the Axis type mapping features in the form
of Serializers and Deserializers external to what automatically happens
when calling a web service.
Before I began implementing my service as a web
Any thoughts on why the WSDL generated from this target is lacking a
Service element entry? I get a PortType and a Binding, but no Service.
Cheers
Steve Maring
http://localhost:8080/axis/services/FirmDirectoryService"/>
16 matches
Mail list logo
