Hi ,
I have worked with gSOAP. It's good for platforms not supported by AXIS 2C
(ex: Sol 10 when I was using it) where you want to have C++ web services.
Else you are better off with AXIS2C.
gSOAP is more primitive than of AXIS 2C and you'll have to do a lot of hacks
to get things working.
As
[
https://issues.apache.org/jira/browse/AXIS2C-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandika Jayawardana reassigned AXIS2C-884:
--
Assignee: Nandika Jayawardana
Seg fault in libxml when svc client torn down
[
https://issues.apache.org/jira/browse/AXIS2C-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12600692#action_12600692
]
Nandika Jayawardana commented on AXIS2C-884:
Now Axis2/C uses guththila as the
What about IIS 7? Can we re-use the stuff form IIS 6?
Samisa...
Supun Kamburugamuva wrote:
Hi List,
I would like to implement support for IIS 6. At the moment we have an
IIS ISAPI module which is a ISAPI Filter + ISAPI Extension. This is
not a good design for IIS 6 since it doesn't
[
https://issues.apache.org/jira/browse/AXIS2C-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sokov updated AXIS2C-1164:
--
Summary: savan_publishing_client_publish() crashes when trying to publish
message when more
Christopher
You can try the Mail transport implementation we have developed for
Apache Synapse. This can be made to replace the Axis2 Mail transport,
but dropping the JAR file [1] into your lib directory, and updating your
axis2.xml as follows:
[1]
Invalid return type of the generated stub causes complie error
---
Key: AXIS2-3826
URL: https://issues.apache.org/jira/browse/AXIS2-3826
Project: Axis 2.0 (Axis2)
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AXIS2-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge updated AXIS2-3826:
---
Summary: Invalid return type of the generated stub causes compile error
(was:
Thanks for the quick help.
The spec you refer to is actually for SOAP12, therfore it is understandable to
prohibit SOAP11. But I want to stay with SOAP11 completely. I specified my WSDL
(I hope completely) for SOAP11 and expected the generated client-stub and
server-sekelton to use also only
getUniqueSuffix does not return the right String class object
-
Key: AXIS2-3827
URL: https://issues.apache.org/jira/browse/AXIS2-3827
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Hi all,
I'm in the process of moving the Axis2 continuum to vmbuild, but I'm
getting a ClassCastException failure in saaj [1].
Could someone who know a little about saaj take a quick look and let
me know if it's something obvious?
Cheers,
David
[1]
Is it possible to pass XML data as a string without it being escaped?
I am calling the Calais web service, which takes the XML document...
c:params xmlns:c=http://s.opencalais.com/1/pred/; xmlns:rdf=
http://www.w3.org/1999/02/22-rdf-syntax-ns#;
c:processingDirectives c:contentType=text/txt
Hi,
It appears that the woden distribution is required for axis2 1.4 to work
properly. In Axis2 1.3 woden was not required to work properly unless of
course you were using wsdl 2.0.
Without woden in Axis2 1.4 you can't even bring up the index.jsp page. You get
a class not found exception.
Hi All,
I've got a couple of questions about this approach.
1) Are there any semantic differences between an Axis2 handler plugged
into specific phases at specific points and a MAR? For example, the
current JAXWS dispatchers have to plug in so that all the operation
resolution has been
Unable to compile code generated from WSDL
--
Key: AXIS2-3828
URL: https://issues.apache.org/jira/browse/AXIS2-3828
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects
Tony
I just downloaded and deployed AXIS2-1.4 and have it running under
%AXIS2_HOME%/bin/axis2server.bat (without woden*.jar)
Can you display the specific error you are seeing?
Also please display the wsdl as I would be interested in seeing the
implemented wsdl2 declaration
Hi
I created a web service using Axis2-1.3, xmlbeans on weblogic 8.1. The
same code worked fine with ADB, but when I tried to do the same with
xmlbeans throws the following exception:
I am NOT using any authentication for my web service, it is simple
enough to send and receive an order.
Are you saying that this issue is fixed in axis 1.4? And it is a known issue
in Axis 1.3?
Saminda Abeyruwan-3 wrote:
Please try AXIS2 1.4 release. This problem has to be fixed .
Thank you!
Saminda
On Wed, May 28, 2008 at 7:08 PM, cmurali [EMAIL PROTECTED]
wrote:
Hi,
I am
Hi,
Our Axis2 1.3 based web service is in IVV (independent Validation and
verification) and hence would appreciate your quick help.
When I query my web service wsdl using SOAPUI, it queries fine and generates
a sample request fine. But when I used another client tool called soapSonar,
I
Martin,
The dependency comes into to play when deploying modules. Here is the
dependency chain that I tracked down in the source.
org.apache.axis2.deployment.ModuleDeployer (line 60)
org.apache.axis2.deployment.repository.util.ArchiveReader
not much documentation on the dependencies listed
http://ws.apache.org/axis2/1_4/userguide.html#underhood
except for..
lib
activation-1.1.jar
XmlSchema.jar
but in $AXIS2_HOME/lib folder I see 60 jar files!
contents of $AXIS2_HOME/lib
03/14/2008 02:09 PM63,018
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hope this helps -
http://cwiki.apache.org/confluence/display/AXIS2/Axis2+1.4+Dependencies
thanks,
dims
Martin wrote:
| not much documentation on the dependencies listed
| http://ws.apache.org/axis2/1_4/userguide.html#underhood
| except for..
| lib
1. Do we need Nethi jar? Shouldn't it be optional?
2. I think we need HTTP client jars and they shouldn't be optional. For
Axis2 to work out-of-the-box I think it should be marked as needed than
optional. Let's be realistic ;)
On Thu, May 29, 2008 at 12:50 PM, Davanum Srinivas [EMAIL PROTECTED]
Well I am not sure whether this is a bug or not.
The getDefaultEnvelope method is implemented both within SOAP11 and SOAP12
factories. So the code you have mentioned is fine, as far as you get the
proper factory.
Yes, Axis2 will send out the proper version depending on the version of the
message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eran,
Try removing neethi :) it's not optional
This is for general guidance, Axis2 to work out-of-the-box for me is to get a
web service deployed and running, you
don't need the http client jars for that. Please feel free to update the page
as
Never mind, I made progress past that problem by changing to a java 5
vm. I don't see a failure on other Java 6 VMs, so I won't raise a
JIRA.
David
On Thu, May 29, 2008 at 12:03 PM, David Illsley [EMAIL PROTECTED] wrote:
Hi all,
I'm in the process of moving the Axis2 continuum to vmbuild, but
add the ability to state a codegen.config in the Maven WSDL2Code plugin
---
Key: AXIS2-3829
URL: https://issues.apache.org/jira/browse/AXIS2-3829
Project: Axis 2.0 (Axis2)
wsdl2java not mapping nillable elements to wrapper classes
--
Key: AXIS2-3830
URL: https://issues.apache.org/jira/browse/AXIS2-3830
Project: Axis 2.0 (Axis2)
Issue Type: Bug
great...can we get this into the release Notes???
Thanks Dims!
Martin
- Original Message -
From: Davanum Srinivas [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Cc: Tony Dean [EMAIL PROTECTED]
Sent: Thursday, May 29, 2008 3:50 PM
Subject: [Axis2] Documenting Axis2 1.4 dependencies (Re:
Muralidaran,
Please ask these types of questions on the axis-user list rather than
the axis-dev list.
I suspect your problem is caused by the fact that you have a number of
schemas that do not specify targetNamespaces, and that you import
these schemas without specifying a namespace. I believe
[
https://issues.apache.org/jira/browse/AXIS-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12600994#action_12600994
]
Karthik R commented on AXIS-2250:
-
Hello Narayan,
Changing WSDD is possible only if you
[
https://issues.apache.org/jira/browse/AXIS-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik R updated AXIS-2250:
Attachment: Post.zip
1.Wsdl
2. src generated wsdl2java
3. server-config.wsdd, just generated by giving
The Axis2 Kernel has a dependency on Woden (To build a service from a WSDL.
to code Generate from a WSDL etc...). When an aar is deployed in axis2 we
have to decide weather that aar contains a WSDL 2.0 file or an WSDL 1.1 file
and act accordingly. This is where your seeing the Woden dependency in
The WSDL to axis service builders need neethi in order to process policies
in those files (Same with the services.xml deployment case) also If you want
to try codegenaration then neethi is mandatory, cause its burnt into the
codegenaration process. So the bottom line is neethi is mandatory.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Next time? :) we typically don't touch releases that we already made.
- -- dims
Martin wrote:
| great...can we get this into the release Notes???
|
| Thanks Dims!
| Martin
| - Original Message - From: Davanum Srinivas [EMAIL PROTECTED]
|
What about http://ws.apache.org/axis2/1_4/contents.html? Tossing a
pointer in there might be handy
--Glen
Davanum Srinivas wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Next time? :) we typically don't touch releases that we already made.
- -- dims
Martin wrote:
| great...can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 go for it!
- -- dims
Glen Daniels wrote:
| What about http://ws.apache.org/axis2/1_4/contents.html? Tossing a
| pointer in there might be handy
|
| --Glen
|
| Davanum Srinivas wrote:
| Next time? :) we typically don't touch releases that we
37 matches
Mail list logo
