Bo
Its simply that Axis2 uses STAX APIs (JSR 173) as its basis. Castor
predates STAX. Its possible to link them but it wouldn't be
efficient.,
Paul
On 2/7/07, Bo Xie <[EMAIL PROTECTED]> wrote:
Hi,
Just wondering if anyone can share some insight on why Castor is not part
of Axis2 data bindin
hi,
Can we use a simple type union as an attribute type? in other words is the
following xmlSchema fragment correct?
if so what could be the serialized xml pattern?
I recently implemented the Union type support for adb.
For a example Lets take following schema fra
Hi,
Just wondering if anyone can share some insight on why Castor is not part
of Axis2 data binding options? Or in another word, any features from
XMLBean that makes it a better choice than Castor?
Thanks,
-Bo
Addendum to last post:
Neither the unwrapping nor backwards compatilbity options in the codegen
tool helped - which leads me to believe that something in the WSDL I
attached in the last message may be amiss. Our goal is to pack portions of
a SOAP header and SOAP body using the WSDL definitions -
Hi Anne,
Thanks for the response.
Here is what we were able to get working with Axis 1.4, and have been
struggling with Axis 2...
Our input message contained TWO parts, one destined for the body, and the
other destined for the header (we set this up in the binding).
The header contains security
There's an error in the WSDL.
The name attribute in the (name="getVersionFault") must
match the name attribute in the definition that defines
the fault message (name="part1").
I suggest you switch to Axis2 1.1.1.
Anne
On 2/5/07, donald yang <[EMAIL PROTECTED]> wrote:
Hi,
When I use AXIS1.4
I have a complex type containing numerous Java Collection objects
(ArrayList, Set, etc.) which are being defined by axis in the generated wsdl
as ArrayOf_xsd_anyType. The problem is that when the WSDL2Java-generated
client calls the web service the following error is generated:
org.xml.sax.SAXEx
Thank you Dims.
One more question, when I used OperationClient API, the content-type and
content-transfer-encoding for first part look like this:
content-type: text/xml; charset=UTF-8
content-transfer-encoding: 8bit
And for attachment part look like this:
content-type: application/octet-stream
co
Yogen,
Those are from Commons HTTP Client basically means that the client is
using http chunking.
thanks,
dims
On 2/6/07, Yadav, Yogendra (IT) <[EMAIL PROTECTED]> wrote:
Hi,
Anyone who has used attachments with AXIS2 ?
-yogen
From: Yadav, Yogendra (IT)
S
Hi Anne,
I tried axis1.4 and my client works fine now. Thank you for your help.
Cheers,
Marian
2007/2/4, Anne Thomas Manes <[EMAIL PROTECTED]>:
This WSDL uses RPC/encoded, and Axis2 does not support SOAP Encoding.
I recommend that you use Axis 1.4 instead.
See http://www.apache.org/dyn/clos
Dims,
https://issues.apache.org/jira/browse/AXIS2-2122
VBR
johan
Davanum Srinivas wrote:
Johan,
Yes, please create a JIRA and summarize the discussions/symptoms and
patch.
thanks,
dims
On 2/6/07, Johan Lundberg <[EMAIL PROTECTED]> wrote:
Hi Alan
Yes, your patch works fine when the param
Hi,
Anyone who has used attachments with AXIS2 ?
-yogen
From: Yadav, Yogendra (IT)
Sent: Tuesday, February 06, 2007 3:26 PM
To: axis-user@ws.apache.org
Subject: FW: MTOM and SWA related problem
Sorry if this email is repeated multiple times. I had corporate s
Hi, I'm having a problem using Axis2-1.1.1 and Rampart-1.1 with the new
WS-SecurityPolicy configurations. Specifically, I get a
NullPointerException
on the server side that gets propogated back to the client via an
AxisFault every time I send a request secured with WS-Security. Here's
the
s
Sorry if this email is repeated multiple times. I had corporate security
issues sending attachments.
Hi,
This problem is related to using MTOM and SAAJ APIs in AXIS2. I am
sending attachment to a service which is implemented using Sun's SAAJ
implementation. When I use Sun's SAAJ as client to acc
Hi,
This problem is related to using MTOM and SAAJ APIs in AXIS2. I am
sending attachment to a service which is implemented using Sun's SAAJ
implementation. When I use Sun's SAAJ as client to access this service
everything works well. But when use AXIS2's MTOM or SAAJ implementation,
the service re
I seriously doubt that you will find anyone that has don't this type
of market analysis. It's almost impossible to determine the total
market share of an open source project (at least with any kind of
statistical accuracy). Axis and Axis2 certainly hold a major share of
the open source SOAP implem
Johan,
Yes, please create a JIRA and summarize the discussions/symptoms and patch.
thanks,
dims
On 2/6/07, Johan Lundberg <[EMAIL PROTECTED]> wrote:
Hi Alan
Yes, your patch works fine when the parameter useOriginalwsdl=false but
it does not seems to have an effect when useOriginalwsdl=true. A
"changing a few 'types' to 'elements'" tells me that the original WSDL
was defined as style="rpc", and my guess is that it used RPC/encoded.
Unfortunately, you have to do a little more than just tweak the
"types" to "elements". For one thing, when using document style, your
message may contain at
Axis2 supports RPC/literal, but it does not support RPC/encoded.
Anne
On 2/6/07, Marian Suran <[EMAIL PROTECTED]> wrote:
Hi,
I have the same problem and when I go with mouse pointer in the debug mode
inside net beans IDE over "env" variable, which holds soap envelope request,
right before serv
Thanks. Was able to finally getting to use the original wsdl. However,
another issues has surfaced where the xsd's that are imported in the types
section of the wsdl cannot be resolved.
When I change the schemaLocation in the xsd:import element and deploy the
service on axis2, axis2 keeps ret
Hi Alan
Yes, your patch works fine when the parameter useOriginalwsdl=false but
it does not seems to have an effect when useOriginalwsdl=true. As you
say, this might be taken care of in another place. However I don't know
the axis2 code at all so I just have to report a bug and try to find a
Hi,
I have the same problem and when I go with mouse pointer in the debug mode
inside net beans IDE over "env" variable, which holds soap envelope request,
right before service execute method to watch its current value I can see
correct soap envelope and then I step over execute method in the deb
Hi,
I use Axis2-1.1.1 version as an embedded webapp in Tomcat 5.5.17. I've
deployed my service and the endpoint to this service is
http://localhost:8080/Comergent/ws/matrix/services/UserService . Without
changing the settings for contextRoot and servicePath properties in
axis2.xml, the service
That sounds like a problem with Xerces, if it's not catching the
validation error.
(Note that Axis does not attempt to validate messages, so you must
perform the validation using a handler or intermediary.)
Anne
On 2/6/07, pau carre <[EMAIL PROTECTED]> wrote:
Hi all, I have witten an schema (XS
I recommend that you edit the generated WSDL and fix the import, and
make sure that the invDoc element is properly defined (i.e., not
xsd:anyType), then gen your service from the WSDL using wsdl2java.
Anne
On 2/6/07, Pedro Silveira Vieira da Silva <[EMAIL PROTECTED]> wrote:
I've created a web s
Hi,
Thanks for the answer. However, I don't quite understand how I can get
the MessageContext. I am not calling any service.
Let me clarify a bit:
say the axis2.war is already running and has its own
ConfigurationContext. So I can deploy modules/services to it.
Now I am writing a test case
Yes, I used -e with soapcpp2 and then it worked fine...
Heiko
Original-Nachricht
Datum: Fri, 2 Feb 2007 18:19:47 -0500
Von: "Anne Thomas Manes" <[EMAIL PROTECTED]>
An: axis-user@ws.apache.org
CC:
Betreff: Re: Axis gsoap interoperability
> Well, for one thing, you should not
El mar, 06-02-2007 a las 11:52 +0530, sumedha rubasinghe escribió:
> Hi Javier,
> I am not quite sure what you meant by ' describing the following two
> fault messages with WSDL + SOAP1.1'.
>
> But what I gathered from the replies you got is,
>
> 1. You have called a web service ( possibly an a
Thanks for the reply Slim. Did you have to configure the gSOAP client with the
client.axis2.xml file?
From: zze-Basic DRISS S ext RD-MAPS-ISS [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 23, 2007 10:46 AM
To: axis-user@ws.apache.org
Subject: RE: WS-Security
I have a WSDL that defines a method that has 1 argument: an array of a custom
class MyClass:
void f(MyClass[] arr){}
I convert this WSDL to Java using Axis2 wsdl2java tool.
The conversion creates a method that instead of MyClass[] receives a generated
class:
ArrayOfMyClass: void f(ArrayOf
I've created a web service that has a simple function that receives a
parameter:
package pt.gedi.ws;
import oasisNamesSpecificationUblSchemaXsdInvoice2.InvoiceDocument;
public class ReceiveInvoice {
public void receive(InvoiceDocument invDoc) {
doSomething(invDoc);
Not right now, sorry.
I created the webservice because I needed to be able to deploy
webservices from any machine, not just from the machine Axis2 is
deployed on.
You could look at the code [1] to find out how to initiate the
ConfigurationContext. Look for initConfigContext.
Brecht
[1]
http://s
Here's what i use: I think you can strip it down further.
XmlSchema-1.2.jar
activation-1.1.jar
annogen-0.1.0.jar
axiom-api-1.2.2.jar
axiom-impl-1.2.2.jar
axis2-adb-1.1.1.jar
axis2-adb-codegen-1.1.1.jar
axis2-codegen-1.1.1.jar
axis2-java2wsdl-1.1.1.jar
axis2-kernel-1.1.1.jar
axis2-tools-1.1.1.jar
Jim,
I opened a JIRA issue. Could you please upload your wsdl here?
https://issues.apache.org/jira/browse/AXIS2-2119
thanks,
dims
On 2/6/07, Jim Apple <[EMAIL PROTECTED]> wrote:
I tried building a client using Axis2-1.1.1, wsdl2java and it fails to
compile. The problem is caused by t
Hi all, I have witten an schema (XSD) using key and keyref elements.
This XSD has been tested successfully with some XML files.
The problem is that when I add this XSD to a WSDL (copy-paste) wrong
soap instances (XML instances in the context of XSD) are validated OK
when they do not fit the keyref
https://issues.apache.org/jira/browse/AXIS2-2118
Thanks,
Brecht
-Original Message-
From: David Illsley [mailto:[EMAIL PROTECTED]
Sent: dinsdag 6 februari 2007 13:51
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Change Axis2 Addressing behaviour
Hi Brent,
Can you raise a JIRA [1], and
Hi Brent,
Can you raise a JIRA [1], and mention the version of Axis2 you're
using and which client API. e.g. ServiceClient/Generated Stub.
Thanks,
David
[1] http://issues.apache.org/jira/browse/AXIS2
On 06/02/07, Brecht Yperman <[EMAIL PROTECTED]> wrote:
Hi,
I'm trying to communicate to a .NE
I tried building a client using Axis2-1.1.1, wsdl2java and it fails
to compile. The problem is caused by this line in the wsdl
It results in a Java variable name with a "-" in it.
java.lang.String tempAttribpost-sale
Thanks
- Jim
You can get the ConfigurationContext using a method like this:
private File getServiceDir() {
if (f_serviceDir == null) {
MessageContext mc =
MessageContext.getCurrentMessageContext();
try {
ConfigurationContext cc =
mc.getConfigurati
Hi,
I've done this creating a webservice which mimicks behaviour from the
AxisAdminServlet (AdminAgent.processUpload).
Basically it's a webservice that takes user credentials (to prevent
anyone from deploying webservices), a base64 encoded webservice jar and
a filename, and writes the bytes from
Hi,
I want to programmatically deploy modules/services to the axis2
repository configured in axis2.war. This way I want to be able to admin
the services I deploy from my application using axis2.war administration
page.
As far as I understand I need to somehow get the instance of
Configurati
Hi,
I'm trying to communicate to a .NET/WSE2.0 webservice.
The problem we have now seems to be something with addressing. I already
changed the namespace using the ServiceClient options:
f_client.getOptions().setProperty(AddressingConstants.WS_ADDRESSING_VERS
ION, Submission.WSA_NAMESPACE);
The
Amila,
Not so fast :) search for soap_header in
InterfaceImplementationTemplate.xsl. I think we do. We should if we
don't...
thanks,
dims
On 2/6/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
On 2/3/07, Kang, Kamaljeet K. <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi,
>
>
> I have a following wsd
Hello,
Please help me in the following issue: I’m writing a web service in java
with
Tomcat + Axis which provides only just one method for sending a mail.
Based on the given parameters it retrieves the email addresses from an
ldap server and then sends the mails. I need to create a server sid
Maybe the address is populated in more than one place, i don't know
the axis code well enough to find out. Try not telling it to use your
wsdl as my patch definitely works for automatically generated wsdls
Quoting Johan Lundberg <[EMAIL PROTECTED]>:
So I tried to run my .aar file in the nig
I wrote my sample code with Axis2 and deployed Axis2.war on both jakarta
tomcat 4.1.31 and IBM WebSphere 6.0.2. I found it behaves weird on WebSphere
when I was running my Microsoft WSE 3.0 client against it. I enabled MTOM in
axis2.xml. From WSE 3.0 client to axis2.war on tomcat, the content type
46 matches
Mail list logo
