[jira] Created: (AXIS2C-176) Files without content in util sub-build system

Files without content in util sub-build system -- Key: AXIS2C-176 URL: http://issues.apache.org/jira/browse/AXIS2C-176 Project: Axis2-C Type: Task Versions: Current (Nightly) Reporter: Sanjaya Ratnaweera

Pentecost / Whitsun

Isn't it time for a 1.6 release? begin:vcard fn:Dr. Franz Fehringer n:Fehringer;Franz org:ISO Software Systeme adr;quoted-printable:;;Eichendorffstrasse 29;N=C3=BCrnberg;;90491;Deutschland email;internet:mailto:[EMAIL PROTECTED] tel;work:+49/(911) - 99594-0 tel;fax:+49/(911) - 99594-580

[jira] Resolved: (AXIS2-161) Line feed normalization and character reference processing

[ http://issues.apache.org/jira/browse/AXIS2-161?page=all ] Eran Chinthaka resolved AXIS2-161: -- Resolution: Fixed This is handled by the parser itself. Line feed normalization and character reference processing

ApacheCon EU 2006 - Secure Web Services with Apache Axis2 and Apache WSS4J

Hi All, Want to find out how to secure Apache Axis2? Apache Rampart as the ideal module for the job !!! If you are anywhere near Ireland on the 26th of June or really want to know how it all works, come on over to ApacheCon EU 2006 where I will be presenting a tutorial on Secure Web Services

[jira] Commented: (AXIS2-747) Missing namespace on subelement

[ http://issues.apache.org/jira/browse/AXIS2-747?page=comments#action_12414365 ] Ajith Harshana Ranabahu commented on AXIS2-747: --- Hmm... this seems to be an XMLBeans issue to me. We rely on the XMLStreamReader returned from the XMLBeans

[jira] Updated: (AXIS2-664) Exception when generating code for C#

[ http://issues.apache.org/jira/browse/AXIS2-664?page=all ] Ajith Harshana Ranabahu updated AXIS2-664: -- type: Improvement (was: Bug) Description: WSDL2Code cannot find code template for C#... Exception in thread main

Re: [Axis2] Publisher-subscriber implementation for Axis2

Cool I'm +1. I'd like to include this in Synapse too. Paul On 6/2/06, Chamikara Jayalath [EMAIL PROTECTED] wrote: Hi all, As I mentioned in the JIRA http://issues.apache.org/jira/browse/AXIS2-793, there does not seem to be much support for Axis2 in this space. I am workaing on an Pub/Sub

[jira] Commented: (AXIS2-791) NTLM client authentication

[ http://issues.apache.org/jira/browse/AXIS2-791?page=comments#action_12414368 ] Saminda Wishwajith Abeyruwan commented on AXIS2-791: Applied the patch you have send. Please try it, can close this JIRA. Thank you Saminda NTLM client

Re: [Axis2] Fwd: SOAP With Attachments - MIME Part Content Transfer Encoding

Hi Thilina. As I said The use of SUN Javamail 1.4 in AXIS2 replacing geronimo-spec-javamail solves my problem. So Before I submit a JIRA, could you tell me if geronimo-spec-javamail was supposed to do the same for now, or if it is still active developpement ? Let me explain myself : When

[jira] Resolved: (AXIS2-779) Response messages have an incorrect value for wsa:RelationshipType attribute, according to the 2005/08 WS-Addressing spec

[ http://issues.apache.org/jira/browse/AXIS2-779?page=all ] Eran Chinthaka resolved AXIS2-779: -- Resolution: Fixed Patch applied. Thanks Brian. Brian, I had problems in applying your patch. Seems to be some character issue. Manually I did the

Re: [Axis2] temp fix for NTML authentication axiom serialization error

Jeff Thanks for the update. We took a look at it (Saminda and me) and the update you made to AbstractHttpSender is great. We will add it into the core tree. However we still don't understand why you are getting into the second issue and the need to patch OMElementImpl. Can you please give us

[Axis2] Annotation-based service generator plugin for eclipse

Hi! We programmed an annotation-based service generator plugin for eclipse for Axis2. It is - in our opinion - more user friendly than the service generator provided on the Axis2 website is up to now, especially while developing and testing a web service. On the website

[Axis] VectorSerializer and VectorDeserializer bean support

The following patch provides bean support for VectorSerializer and -Deserializer. Instead of item xmlns=, the namespace of the object (if one is registered as TypeMapping) to be serialized is used. ___ Telefonate ohne

Re: [Axis2] temp fix for NTML authentication axiom serialization error

Hi, The reason for this is that OMElement On 6/2/06, Paul Fremantle [EMAIL PROTECTED] wrote: Jeff Thanks for the update. We took a look at it (Saminda and me) and the update you made to AbstractHttpSender is great. We will add it into the core tree. However we still don't understand why you

Re: NTML support in Axis2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please try it with Revision 411069 upwards. Saminda Jeff Ling wrote: So it's not supported yet? Is it possible to provide a patch? Or even some source code that I can compile myself. I guess it's only an issue of providing configuration, right?

Re: [Axis2] temp fix for NTML authentication axiom serialization error

hi, Ooops, hit the send by mistake. Please ignore the last post The reason for this is that the OMElement.serializeAndConsume() has been called twice It is not supposed to be! So my guess is the NTLM authentication pat has to call OMElement.build() first Ajith On 6/2/06, Ajith Ranabahu [EMAIL

[jira] Created: (AXIS2-795) Returning a MTOM message causes IOException (closed stream)

Returning a MTOM message causes IOException (closed stream) --- Key: AXIS2-795 URL: http://issues.apache.org/jira/browse/AXIS2-795 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: databinding

[jira] Resolved: (AXIS2-768) WSDL2Java (via Eclipse plugin) generates code with a bug

[ http://issues.apache.org/jira/browse/AXIS2-768?page=all ] Ajith Harshana Ranabahu resolved AXIS2-768: --- Resolution: Fixed Peter has verified that this issue is solved and hence I'm marking this issue as solved. As for replacing the

[jira] Commented: (AXIS2-776) Make the AddressingBasedDispatcher a handler in the Addressing module

[ http://issues.apache.org/jira/browse/AXIS2-776?page=comments#action_12414399 ] Eran Chinthaka commented on AXIS2-776: -- Hi Brian, I can not apply this patch as I'm getting an error. Can you please re-create this and attach it again. -- Chinthaka

[jira] Resolved: (AXIS2-792) Populating an AxisService via ServiceBuilder does not set service name

[ http://issues.apache.org/jira/browse/AXIS2-792?page=all ] Davanum Srinivas resolved AXIS2-792: Resolution: Fixed Applied. thanks, dims Populating an AxisService via ServiceBuilder does not set service name

Dynamic proxy client for a document/literal web service

Hello, I am developping a dynamic proxy client to access an existing document literal web service (I am not the web service developper). On the client side I am using SPRING ant Axis. I registered properly the complex types. But I have the following error: AxisFault faultCode:

[jira] Resolved: (AXIS2-716) Code Gen produces wrong package in service.xml

[ http://issues.apache.org/jira/browse/AXIS2-716?page=all ] Ajith Harshana Ranabahu resolved AXIS2-716: --- Resolution: Fixed This is fixed in the documentation in the SVN and will be updated in the site soon Code Gen produces wrong

[jira] Resolved: (AXIS2-677) doc error - AntCodeGenTask attribute generateserverxml should be generateservicexml

[ http://issues.apache.org/jira/browse/AXIS2-677?page=all ] Ajith Harshana Ranabahu resolved AXIS2-677: --- Resolution: Fixed The issue has been solved and the site will be updated soon. Please see the solution for issue 716 doc error -

Re: [Axis2] Publisher-subscriber implementation for Axis2

Chamikara, I thought some of this work was already being done under the Pubscribe project? http://ws.apache.org/pubscribe/ Or, is Pubscribe only for Axis1? If so, wouldn't it make sense to just have this as a different version under that project? Just curious Regards, Nicholas Gallardo

Re: [Axis2] Publisher-subscriber implementation for Axis2

I guess I'm not sure where it should go. But technically this seems like a complete new project: Pubscribe is based on Axis1 *and* WSRF / WS-Notification, and so a lightweight framework with Eventing support on Axis2 seems to me to be 100% new code. PaulOn 6/2/06, Nicholas L Gallardo [EMAIL

[jira] Commented: (AXIS-2489) Unable to create compressed request

[ http://issues.apache.org/jira/browse/AXIS-2489?page=comments#action_12414412 ] Andreas Goetz commented on AXIS-2489: - Bjorn, not entirely sure how to answer this. I'm using Axis 1.3 as embedded in the Eclipse 3.2 WST toolkit. How would I find out?

[jira] Resolved: (AXIS2-720) Data binding Error after using WSDL2Java to generate xmlbeans code

[ http://issues.apache.org/jira/browse/AXIS2-720?page=all ] Ajith Harshana Ranabahu resolved AXIS2-720: --- Resolution: Fixed The issue seems to be not the problem of the code but rather the WSDL. Rincewind (the reporter) has verified that

[jira] Updated: (AXIS2-761) SimpleHttpServer based on Jakarta HttpComponents HttpCore

[ http://issues.apache.org/jira/browse/AXIS2-761?page=all ] Oleg Kalnichevski updated AXIS2-761: Attachment: jakarta-httpcore-4.0-20060602.jar Chuck, We are currently in the process of cutting the 4.0 alpha2 release. Just to be on the safe side

[jira] Updated: (AXIS2-761) SimpleHttpServer based on Jakarta HttpComponents HttpCore

: ConfigurableSimpleHTTPServer.consolidated.patch, ConfigurableSimpleHTTPServer.patch, jakarta-httpcore-4.0-20060602.jar, simplehttpserver.patch The following patch replaces the SimpleHttpServer implementation based on the testing framework of Commons HttpClient 3.x with a one based on Jakarta HttpComponents HttpCore

[jira] Resolved: (AXIS2-700) AXIS2 1.0 get wsdl always contains address like http://hostname:8080/axis2/service.. in the WSDL services - address - location

[ http://issues.apache.org/jira/browse/AXIS2-700?page=all ] Deepal Jayasinghe resolved AXIS2-700: - Resolution: Fixed Fixed in currcent SVN AXIS2 1.0 get wsdl always contains address like http://hostname:8080/axis2/service.. in the WSDL

[jira] Resolved: (AXIS2-675) WSDL soap-adress not correctly set by Axis2 1.0 webapp

[ http://issues.apache.org/jira/browse/AXIS2-675?page=all ] Deepal Jayasinghe resolved AXIS2-675: - Resolution: Fixed Fixed in current SVN WSDL soap-adress not correctly set by Axis2 1.0 webapp

[jira] Resolved: (AXIS2-441) Axis 0.94 - Can't use other urlpath than /services/*. Gives AxisService Not found yet in the reply as an AxisFault.

[ http://issues.apache.org/jira/browse/AXIS2-441?page=all ] Deepal Jayasinghe resolved AXIS2-441: - Resolution: Fixed Fixed in current SVN by adding follwoing paramter into axis2.xml you can get the url you want parameter

axis 2 client for axis 1 server

Hi all, I have a strange problem, could please someone try to help me ? I am trying to use an axis 2 client to connect to an axis 1 web service, when running the code I get the error : [2/06/06 15:57:51:830 CEST] 2fdbdee4 WebGroup I SRVE0180I: [SimpleClient] [/SimpleClient]

[jira] Assigned: (AXIS2-789) A SOAPFault targeted at a service (e.g. using WS-Addressing FaultTo) is not passed to the service object

[ http://issues.apache.org/jira/browse/AXIS2-789?page=all ] Deepal Jayasinghe reassigned AXIS2-789: --- Assign To: Deepal Jayasinghe A SOAPFault targeted at a service (e.g. using WS-Addressing FaultTo) is not passed to the service object

[jira] Assigned: (AXIS2-788) Outbound MAP EPRs overwritten with values from the response message

[ http://issues.apache.org/jira/browse/AXIS2-788?page=all ] Deepal Jayasinghe reassigned AXIS2-788: --- Assign To: Deepal Jayasinghe Outbound MAP EPRs overwritten with values from the response message

[jira] Assigned: (AXIS2-787) POST request from a REST client will cause a NullPointerException in the service

[ http://issues.apache.org/jira/browse/AXIS2-787?page=all ] Deepal Jayasinghe reassigned AXIS2-787: --- Assign To: Deepal Jayasinghe POST request from a REST client will cause a NullPointerException in the service

[jira] Assigned: (AXIS2-786) Passing unknown parameters in a GET from a REST client causes NullPointerException in SchemaUtil.java

[ http://issues.apache.org/jira/browse/AXIS2-786?page=all ] Deepal Jayasinghe reassigned AXIS2-786: --- Assign To: Deepal Jayasinghe Passing unknown parameters in a GET from a REST client causes NullPointerException in SchemaUtil.java

[jira] Assigned: (AXIS2-793) Support for Publisher-Subscriber specifications

[ http://issues.apache.org/jira/browse/AXIS2-793?page=all ] Deepal Jayasinghe reassigned AXIS2-793: --- Assign To: Chamikara Jayalath Support for Publisher-Subscriber specifications --- Key:

Re: [Axis2] Publisher-subscriber implementation for Axis2

Hi Nicholas, Paul, All, Yes, pubscribe is basically about Axis1/ WS-Notification and I believe having an Eventing implementation for Axis2 under the Same project could be confusing. Due to the architectural differences b/w Axis2 and Axis1 most of the code would have to be rewritten. For e.g.; 1.

[jira] Created: (AXIS-2490) Class Message has non serializable and non transient field

Class Message has non serializable and non transient field -- Key: AXIS-2490 URL: http://issues.apache.org/jira/browse/AXIS-2490 Project: Apache Axis Type: Bug Components: Basic Architecture Versions:

[jira] Created: (AXIS2-796) WSDL2Java fails with imported schemas in WSDL with file not found.

WSDL2Java fails with imported schemas in WSDL with file not found. -- Key: AXIS2-796 URL: http://issues.apache.org/jira/browse/AXIS2-796 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: Tools

[jira] Commented: (AXIS2-720) Data binding Error after using WSDL2Java to generate xmlbeans code

[ http://issues.apache.org/jira/browse/AXIS2-720?page=comments#action_12414474 ] Rincewind Wizard commented on AXIS2-720: It does indeed work now. However, it would be a good idea to investigate, why the VALID wsdl we used before, with the

Re: [Axis2] temp fix for NTML authentication axiom serialization error

Hi Ajith and Paul,Yes, it sounds right: Parser was accessed when not supposed to be, so a calling sequence might be the reason.Thanks for taking care of this so promptly. Let me know if there is anything else I can help with. (Such as a particular build I can test?) JeffOn 6/2/06, Ajith Ranabahu

Axis Error - Server

Hello all, I have a bug with a web service I have 3 method for show I have a problem with a method excatly I run the client an the tcp-mon show the message that send the client and response the server. this is the messages: User-Agent: NuSOAP/0.6.3 Host: 127.0.0.1:

[jira] Commented: (AXIS-2489) Unable to create compressed request

[ http://issues.apache.org/jira/browse/AXIS-2489?page=comments#action_12414488 ] Bjorn Townsend commented on AXIS-2489: -- It should say in your WSDD file -- that's one of the reasons why I wanted to see it. :) You have to set the CommonsHTTPSender

[jira] Updated: (AXIS2-790) Request to log which XMLStreamReader/Writer is used

[ http://issues.apache.org/jira/browse/AXIS2-790?page=all ] Mike Rheinheimer updated AXIS2-790: --- Attachment: RESTUtil.patch patch attached. Extremely minor improvement to RESTUtil.java to call StAXUtils.createXMLStreamReader directly. Request to

Re: [Axis2] Publisher-subscriber implementation for Axis2

IMO savan is like rampart, rahas, sandesha2 and kandula2 .. all modules for Axis2. Right now we have an inconsistent model: rampart and rahas are maven modules in the axis2 project and sandesha2 and kandula2 are WS projects. My pref would be to bring savan into being as a maven module in axis2

[jira] Resolved: (AXIS2-790) Request to log which XMLStreamReader/Writer is used

[ http://issues.apache.org/jira/browse/AXIS2-790?page=all ] Davanum Srinivas resolved AXIS2-790: Resolution: Fixed Applied. thanks, dims Request to log which XMLStreamReader/Writer is used ---

[jira] Created: (AXIS2-797) ADB does not work with elementFormDefault=unqualified schemas

ADB does not work with elementFormDefault=unqualified schemas Key: AXIS2-797 URL: http://issues.apache.org/jira/browse/AXIS2-797 Project: Apache Axis 2.0 (Axis2) Type: Bug Reporter: Davanum

[jira] Updated: (AXIS2-797) ADB does not work with elementFormDefault=unqualified schemas

[ http://issues.apache.org/jira/browse/AXIS2-797?page=all ] Davanum Srinivas updated AXIS2-797: --- Description: Please see AXIS2-720 for a sample wsdl/xsd that fails. (was: Please see AXIS2-720) ADB does not work with elementFormDefault=unqualified

Re: axis2 - 1.0 - Problem with returning array or ArrayList

Please open up a bug report with stack traces / request-response messages if any. thanks, dims On 6/1/06, Peter Pei [EMAIL PROTECTED] wrote: Hi, With AXIS, obviously I can have a service that returns array or ArrayList, but this seems to be gone with AXIS2. Did I do something wrong, or this

RE: [axis2] changes in 1.0

Dims, I believe Deepal opened a jira for serviceContext.getMyEPR(). I have not heard anything about the axis fault problem. My question is am I doing the right thing here? I remember someone saying that some of that code was going to be cleaned up making it somewhat easier and more intuitive

[jira] Created: (AXIS2-798) WSDL2Java Fails on MTOM wsdls

WSDL2Java Fails on MTOM wsdls - Key: AXIS2-798 URL: http://issues.apache.org/jira/browse/AXIS2-798 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: wsdl Versions: 1.0 Environment: Win32 Reporter: Nadeem Hoda In

Re: [axis2] changes in 1.0

Yes, please create one does not harm and keep the item fresh in everyone's memory. -- dims On 6/2/06, Tony Dean [EMAIL PROTECTED] wrote: Dims, I believe Deepal opened a jira for serviceContext.getMyEPR(). I have not heard anything about the axis fault problem. My question is am I doing the

[jira] Commented: (AXIS2-798) WSDL2Java Fails on MTOM wsdls

[ http://issues.apache.org/jira/browse/AXIS2-798?page=comments#action_12414516 ] Davanum Srinivas commented on AXIS2-798: Nadeem, Please upload you complete wsdl. thanks, dims WSDL2Java Fails on MTOM wsdls -

Log Axis

Hello all, Could they do me a favor.. How I can config the log of Axis? Thanks... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: [axis2] changes in 1.0

I will enter it. Also, another problem. I use to be able to obtain the axis2 lib and axis2 services directory with the following: messageContext().getConfigurationContext().getRealPath(lib); messageContext().getConfigurationContext().getRealPath(services); Now, using:

[jira] Created: (AXIS2-799) serviceContext.getConfigurationContext().getRealPath() not working as intended...

serviceContext.getConfigurationContext().getRealPath() not working as intended... --- Key: AXIS2-799 URL: http://issues.apache.org/jira/browse/AXIS2-799 Project: Apache Axis 2.0 (Axis2)

[jira] Created: (AXIS2-800) creating custom axis fault (application specific faultCode, ReasonCode, and detail)

creating custom axis fault (application specific faultCode, ReasonCode, and detail) --- Key: AXIS2-800 URL: http://issues.apache.org/jira/browse/AXIS2-800 Project: Apache Axis 2.0 (Axis2)

[jira] Commented: (AXIS2-799) serviceContext.getConfigurationContext().getRealPath() not working as intended...

[ http://issues.apache.org/jira/browse/AXIS2-799?page=comments#action_12414525 ] Tony Dean commented on AXIS2-799: - I forgot to put that this was found at 1.0. serviceContext.getConfigurationContext().getRealPath() not working as intended...

Re: axis 2 client for axis 1 server

Can you do a TCPMON trace of the message on the wire? Thats a good way of debugging SOAP interop. Paul On 6/2/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi all, I have a strange problem, could please someone try to help me ? I am trying to use an axis 2 client to connect to an axis 1 web

[jira] Created: (AXIS2-801) UserException - AxisFault is not put in details to the SOAP-response ++ Davanum advised me to open an issue

UserException - AxisFault is not put in details to the SOAP-response ++ Davanum advised me to open an issue Key: AXIS2-801 URL:

patch for org.apache.axiom.om.impl.serialize.StreamingOMSerializer

Hi guys,I got NullpointerException with the request content: ?xml version='1.0' encoding='utf-8'?soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/ soapenv:Header /soapenv:Bodyns1:GetListItems xmlns:ns1= http://schemas.microsoft.com/sharepoint/soap/listName xmlns=