RE: Standard for publishing custom WSDL/XSD using axis2

: Re: Standard for publishing custom WSDL/XSD using axis2 Hi, are you asking about how to specify schema location in your WSDL during runtime? I believe absolute HTTP URL such as schemaLocation="http://foo.com/foo.xsd"; is best. Relative URL may not work correctly and file paths don'

Standard for publishing custom WSDL/XSD using axis2

I have a number of Document based web services. Separate XSD document imported into my WSDL. All is well. I can use the WSDL in the .NET world, IBM world all the clients work. What I can't figure out, yet. Is where to put the WSDL so that it is picked up via a URL whilest in Axis2. The

RPC in DOCUMENT Out

Axis 2 question Is there an off the shelf solution for a web service client to bind and invoke a RPC style method with a DOCUMENT style return? XMLDocument myDoc = a.getData( "test" ); // pseudo client code Standard message receiver, services.xml WSDL, stuff. Thanks for reading and

RE: Minimal set of JARs to embed Axis2 into a webapp?

Can I please be taken off the black list... :-) _ From: Kurt Kavanaugh Sent: Monday, June 02, 2008 1:47 PM To: axis-user@ws.apache.org Subject: Re: Minimal set of JARs to embed Axis2 into a webapp? > > +---lib > > > axiom-api-1.2.5.jar > > > axiom-im

Re: Minimal set of JARs to embed Axis2 into a webapp?

> > +---lib > > > axiom-api-1.2.5.jar > > > axiom-impl-1.2.5.jar > > > axis2-kernel-1.3.jar > > > backport-util-concurrent-2.2.jar > > > commons-fileupload-1.1.1.jar > > > commons-httpclient-3.0.1.jar > > > jax-qname-1.5.jar (QName API part of stax-api) neethi-2.0.2.jar > > > wsdl4j-1.6.2.jar wstx-

RE: Multi-Part/ SOAP body return

extends the depricated class AbstractInOutSyncMessageReceiver. Again any information is greatly appreciated... Kurt P.S. Is there documentation on extending and creating receivers? Do's and don't's so to speak. _ From: Kurt Kavanaugh Sent: Monday, May 19, 2008 4

RE: Multi-Part/ SOAP body return

AbstractInOutSyncMessageReceiver is depricated. Taking the other path of extending AbstractMessageReceiver means more work. However if that is the way to go or if I am missing an *obvious* pattern please, knock me on the head Thanks in advance Kurt _ From: Kurt Kavanaugh Sent: Monday, May 19, 2008

Multi-Part/ SOAP body return

Looking for I am implementing a service with message receiver RawXMLINOutMessageReceiver which has a single entry point return (ie OMElement ) Snippet from source * start snippet * OMElement result = (OMElement) method.invoke(obj, new Object[]{m

RE: Body element missing - using javax.xml.SOAP client

Never mind. Pilot error to a degree. The message.getMimeHeaders().addHeader("SOAPAction", "mynamespace:getValue"); Was required but the rest is me on too much caffiene.. Kurt _ From: Kurt Kavanaugh Sent: Friday, May 09, 2008 3:46 PM To: axis-user@ws.ap

RE: Body element missing - using javax.xml.SOAP client

is is being dropped. Again any and all help is appreciated _ From: Kurt Kavanaugh Sent: Friday, May 09, 2008 3:37 PM To: axis-user@ws.apache.org Subject: RE: Body element missing - using javax.xml.SOAP client More info... After the service is called, the return element is att

RE: Body element missing - using javax.xml.SOAP client

.xmlsoap.org/soap/envelope/";> But instead we build up the factory default. I am going to modify the code recompile and test. Kurt _ From: Kurt Kavanaugh Sent: Friday, May 09, 2008 3:02 PM To: axis-user@ws.apache.org Subject: Body element missing - using javax.xml.SOAP c

Body element missing - using javax.xml.SOAP client

Background: Trying to invoke a SOAP service endpoint from old school API's. Why? Requiring clients to have as little knowledge, ie no Axiom/Axis jars, as possible. First I had to add a a Mime Header to get it to play well the Dispatch,Phase and AbstractDispatcher pattern in the Axis 2 Ke

RE: Choosing a path

typically not validated, due to performance reasons. [Kurt Kavanaugh] Hmmm mildly disagree. If a HashTree is built based upon XSD at bootstrap or on demand and cached with a shelf life, binding to various XSD namespaces, lookup and comparing at the node level is fast and trivial, with either a push or

Choosing a path

I have been doing some reading... and more reading... :-) So many choices. But all start with business requirements. In a nutshell. I like the Axiom model and the ability to write code vs generated code. On the other hand I want XSD conformance. We also need to have a fairly rich XML mo

Attributes vs. Elements

Pros cons... So rather than...

RE: One url-pattern to bind them all...:) - (url-pattern not getting to the AxisServlet)

worker.properties file JkMount /services/* foo Otherwise nary a service invoke will ye see. Kurt _ From: Kurt Kavanaugh Sent: Monday, May 05, 2008 1:08 PM To: axis-user@ws.apache.org Subject: One url-pattern to bind them all...:) - (url-pattern not getting to the

One url-pattern to bind them all...:) - (url-pattern not getting to the AxisServlet)

Not seeing the AxisServlet being invoked for /services/* url-pattern... Web.xml *** AxisServlet Apache-Axis Servlet org.apache.axis2.transport.http.AxisServlet 1

RE: ConfigurationContext

: axis-user@ws.apache.org Subject: Re: ConfigurationContext -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 rename address.mar as addressing.jar and drop it into WEB-INF/lib. Kurt Kavanaugh wrote: | Background: | | | | Java: 1.5 | | Tomcat 5.25 | | Mod_JK Connector | | Apache web server | | Axis 2

ConfigurationContext

Background: Java: 1.5 Tomcat 5.25 Mod_JK Connector Apache web server Axis 2 IDE: Intellij 7.x We have non-standard web layout, I am using the init-params and params in the axis.xml to explicitly set up the contexts and other entry points. I have some experience with Axis back in