I've got some custom modifications to Axis 1.1 that I'd like to merge into a
local copy of 1.2 RC1. Presumably, I can do something like "cvs update -r
Version1_2RC1" - except that I can't identify any tag for RC1. I only see the
tag for RC2. What am I missing?
Thanks,
Mark
p://www.w3.org/2001/XMLSchema";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
...
http://schemas.myserver/po.xsd"/>
...
> -----Original Message-
> From: Mark D. Hansen [mailto:[EMAIL PROTECTED]
> Sent: Thursday, J
I'm trying to use org.apache.axis.client.Call to invoke a doc/lit service, and I would
like it to send the xsi:type attributes of the parameters (I'm using WRAPPED style).
Using TCPMonitor, I notice that Axis doesn't send the xsi:type attributes. So, I dug
into the org.apache.axis.client.Call
Is it possible for me to get the ?WSDL generated by a deployed service to include a
schema (in the section) that is imported from an external file or URL? I
notice that Java2WSDL has an "importSchema" option, but I can't seem to figure out how
to use it in a WSDD.
Thanks.
I was reviewing this old post from Anne Thomas Manes (which - as usual has tons of
useful information), and I'm wondering where the conventions described for naming the
SOAP body child element in a doc/lit request comes from?? SOAP 1.1 and WSDL 1.1 both
seem to be less specific. I can't even s
Does Axis do anything with the SOAPAction HTTP header? I know it is required, but
seems like it always has value "". Doesn't WSDL 1.1 specify use of this to specify
the operation when doing doc/lit?
Thanks,
Mark
Can I pass parameters to a service (for initialization) using the WSDD file? If so
how?
Here is my WSDD:
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
/GetAddrFromPO.wsdl
I'd like to pass initialization parameters to the
loyment on Axis 1.2beta
>
>
> org.apache.axis.message.SOAPBodyElement. Right?
>
> On Thu, 10 Jun 2004 14:04:39 -0400, Mark D. Hansen
> <[EMAIL PROTECTED]> wrote:
> >
> >
> > I can't seem to get Message-style services with this signature
> &
I can't seem to get Message-style services with this signature
public SOAPBodyElement [] method (SOAPBodyElement [] bodies);
to deploy on Axis 1.2beta. The deploy.WSDD gets processed OK, but when =
I try to use the service, I get the exception:
"does not match any of the valid signatures for m
Did you ever get an answer to this? I'm having a similar issue. Where is the schema
for things like apachesoap:DataHandler, apachesoap:Element? Are we supposed to
generate these ourselves using tools like JAXB and the java interface definitions?
Thanks,
Mark
> -Original Message-
> F
Sorry if this is a dumb question, but I'm having trouble finding an XML Schema
definition for type="apachesoap:Element"
xmlns:apachesoap="http://www.apache.org/xml-soap";
Does Apache publish this schema somewhere?
Can anyone point me to a good description of how Axis peforms [de]serialization
between Java instances and XML?
I have some custom [de]serialization tools that I'd like to plug into Axis, but my
head is spinning trying to figure out how this is accomplished.
TIA!
-- Mark
I've got a SOAP service that takes a long time to initialize because it is creating a
instance of a relational dabatase, opening a JDBC connection, etc.
This initialization gets done in a static initialization block in the service - so it
only happens once. But, it seems like Axis doesn't insta
on the client side), resp. Furthermore, they
> are always
> service specific.
>
> Using JAXRPCHandler may have some drawbacks, since this class
> seems to need
> some fixes, but nevertheless you'll have the opportunity to
> plug JAX-RPC
> style handlers into any ch
Does anybody know what JAXRPCHandler is supposed to be used for? After digging around
in the source code, I finally figured out how to deploy services using JAX-RPC
handlers via WSDD and the element. So, if is
the intended method for deployment of JAX-RPC handlers, what is the class
JAXRPCH
[EMAIL PROTECTED]
> Sent: Tuesday, December 09, 2003 6:30 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Handler question
>
>
> Please try Axis 1.2 Alpha. If that does not work as expected,
> then log a bug report.
>
> -- dims
>
> --- "Mark D. Hansen" <[EMAI
TECTED]
> Subject: AW: Handler question
>
>
> Use a JAXRPCHandler and return false if you want to stop processing.
>
> > -Ursprüngliche Nachricht-
> > Von: Mark D. Hansen [mailto:[EMAIL PROTECTED]
> > Gesendet: Montag, 8. Dezember 2003 23:43
> &g
I need to write a handler (server side) that, under certain conditions in the
SOAPMessage being processed, prevents the target SOAP service from getting executed.
But, I don't want to throw an exception. Can anyone provide some insight as to how
this is done with Axis?
Thanks,
Mark
Does org.apache.axis.JAXRPCHandler handle SOAP faults the way that the JAX-RPC 1.0
specification intends?
My understanding is that this class should feed responses that are SOAP faults (i.e.,
SOAP messages containing element in the body) to the implementation
class's handleFault(Context) metho
Is there any way to put .jar files on an Axis endpoint application's classpath other
than placing the .jar files into the axis\WEB-INF\lib directory?
I've got a lot of applications that I want to deploy on Axis, and they sometimes have
conflicting classpath requirements. So, it is not a good so
A org.apache.commons.logging.LogConfigurationException is getting thrown by a service
that I've deployed with Axis. The service uses SAAJ 1.2. The exception is happening
when I try to get a SOAPEnvelope from a SOAPPart. In this case, I'm using the
com.sun.xml.messaging.saaj.soap ... implement
I'm getting the following when trying to deploy a handler:
... WSDDException: Must include type attribute for Handler deployment!
However, I *have* included a type attribute. My .wsdd appears below. Any help is
greatly appreciated!
http://xml.apache.org/axis/wsdd/";>
service element
> wsdlServicePort = name for the port
> wsdlTargetNamespace = target namespace
> wsdlInputSchema = Types for inclusion in the types section
>
> You can also control WSDL Generation with the ,
> ,
> , and WSDD elements.
>
> Thomas
>
> > -Ursprüngliche Nac
In looking through some of the sample and test cases related to the JAXRPC
implementation (e.g., /samples/jaxrpc/hello, /test/wsdl/jaxrpchandler), I notice that
some of the deployment files (.wsdd files) define services with parameter sub-elements
having names like:
wsdlServiceElement
wsdlServi
Are there any plans for the Axis implementations of the javax.xml.soap.* interfaces
(e.g., org.axis.message.MessageElement) to implement the org.w3c.dom.Node and other
DOM interfaces as the Sun RI for JAX-RPC/SAAJ has done?
Thanks,
Mark
I'd like to be able to deploy a web services that receives a
javax.xml.soap.SOAPElement and returns the same type. However, when I deploy the
following, Axis is generating invalid WSDL.
The problem in the WSDL is that a undefined prefix "tns1" is being used to define the
return type: "tns1:SOA
I understand that to force a Axis Call instance to use the Literal XML encoding, you
can us this command:
call.setEndocingStyleURI(Constants.NS_URI_LITERAL_XML);
Is there a JAXRPC compliant way to do this? I assume that you can use
call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY,
I'm trying to create/use a custom log4j.xml (same as log4j.properties, but XML
format). As directed in the Axis documentation, I removed log4j.properties from
axis.jar and have placed my custom log4j.xml in the classpath.
But, now when I run the axis-admin Ant tasks (e.g., to deploy or undeploy
Is there any way to get Axis to reconfigure logging (based on an updated
log4j.properties) without rebooting the servlet container that it is running inside of?
Thanks,
Mark
I found some bugs in the JWSDP 1.2 implementation of JAXRPC. For example:
>Oneway operations are not supported for a doc/lit WSDL when using
>dynamic proxy client. This will be fixed in the next version of JWSDP
>expected to release later this year.
On the other hand, the Axis implementation of
Has anyone worked with the method org.apache.axis.client.Call.invokeOneWay(Object[]
params) ?? It does not seem to be working for me. No exception is thrown by the
client, but the web service is not executing.
Is there any sample code out there that uses this method that I can look at?
Thanks
The Axis user guide states that "Message" style services support four valid
signatures. All four appear to map request/response WSDL. Is it possible to use
"Message" style with a one-way operation so that Axis doesn't send SOAP back on the
HTTP response, but just a simple "HTTP 200/202"?
If one uses the tag within a ... definition, does Axis
validate incoming SOAP msgs to that service against the schema specified by the
?
accessing the TypeMappingRegistry in a JAXRPC
> > implemenation
> >
> >
> > > Mark,
> > >
> > > I don't believe that the JAX-RPC spec defines a standard
> > way to do custom
> > > [de]serialization. The Axis classes are used by many ven
The Axis classes are used by many vendors (IBM,
> Borland,
> > Macromedia, Pramati, etc), but I wouldn't say that it has
> been established
> > as a defacto standard. There are lots of other
> implementations that use
> > their own classes.
> >
> > Anne
>
Not much is going on on the JAXRPC-INTEREST discussion, so I'm also
posting this here. I hope it is not considered too "off topic".
> -Original Message-
> From: Public discussion on JAX-RPC
> [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Hansen
> Sent: Friday,
client-side code that uses JAX-RPC
> handlers.
>
> -- dims
>
> --- "Mark D. Hansen" <[EMAIL PROTECTED]> wrote:
> > I'm trying to understand whether or not Axis qualifies as a
> "JAX-RPC runtime implementation".
> > It seems to suppor
t; developers are familiar with Castor.
> >
> > The current Castor serializer in the Axis code assumes a
> default mapping.
> > I've seldom gotten away with not having to write a mapping file with
> Castor
> > so you may have to write your own serializer. I'm wr
I'm trying to understand whether or not Axis qualifies as a "JAX-RPC runtime
implementation". It seems to support JAXRPC, but why doesn't the
org.apache.axis.Handler class (for example) implement javax.xml.rpc.handler.Handler?
Thanks,
Mark
Thank you Steve - this is very helpful. One follow-on question. What do
you mean by "muddy up your XSD"?
> you will have to muddy up your XSD to get your classes to implement
> serializable, and ...
Is is possible to replace the XML Schema --> Java mapping mechanism in WSDL2Java with
JAXB? Alternatively, is there another way to use JAXB as the binding mechanism within
the Axis framework?
Thanks,
Mark
JWSDP 1.2
I have worked with both Axis and JWSDP. What do you want
to know?
> -Original Message- >
From: Mark D. Hansen [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 22, 2003 8:44 PM > To: AXIS Users (E-mail 2) > Subject:
need an alternative to Sun'
I'm pulling my hair out trying to work with Sun's JAX-RPC RI - particularly the
wscompile tool. Am I just dense or is it hard to work with?
Will I be any happier switching over to Axis? Has anybody on this list worked with
both?
Thanks,
Mark
43 matches
Mail list logo
