I am trying to create a custom Derserializer to successfully deserialize
a Map sent to me by a client who built his SOAP by using a stub
generated by WSDL and using the WSDL generated beans. The server code
that is trying to deserialize this is trying to deserialize directly
into a set of exter
How can we get Axis WSDL->Java to use our custom beans when generating
static stubs and skeletons.
When taking a completed server-side implementation, where the interface
accepts and returns types that are either base types or types that are
consistent with JavaBean or Enumeration conventions,
Adding something like the following to your log4j.properties file should
start doing the trick.
log4j.logger.org=ERROR
I believe the above configuration sends all org.* Loggers to the "ERROR"
log, which seems to have a verbosity to log nothing more trivial than an
error.
Rommel Sharma wrote:
LD_DIR}/wsdl/${ws.file}"
location="${ws.url}"
namespace="urn:${ws.name}">
Jim Stafford wrote:
I am also having a problem with custom beans which I think the sample
code within
I am also having a problem with custom beans which I think the sample
code within this e-mail will fix. However, I still want to ask if this
is the intended solution when the problem is encounteredt during
java2wsdl generation.
I have an interface that accepts a serializable bean (see my post
I believe you can use
http://ws.apache.org/axis/java/apiDocs/org/apache/axis/MessageContext.html#getCurrentContext()
to get the current MessageContext which will point you to just about
everything Axis knows about the message.
http://ws.apache.org/axis/java/apiDocs/org/apache/axis/MessageConte
I have done nearly the same with the alpha (and previous versions)
successfully. I would suggest you either
* add some debug statements to the Stub and/or Skeleton to determine
what is happening at the Call level,
* insert the monitor at the TCP level (see bottom of
http://ws.apache.org/axis/jav
I am getting a NullPointerException when I run Java2WSDL for an
interface (Event Handler) that passes a custom bean type (Event). I
haven't tried this with Axis1.1, but it happens with the current
(1/12/2004 ~11:30pm) CVS tree for 1.2alpha. The exception goes away if I
change the data type pass
