Re: How to change the ContextRoot of the StandAlone SimpleAxis2Server

[Charles Ambrose]

Hi Martin!

Thanks for the reply.

Yes, I have modified axis2.xml and configured it to be:
axxis

Even this has already been set, the standalone simpleaxis2server still
resolves to:
http://localhost:8080/axis2/services which I expect it to:
http://localhost:8080/axxis/services

What else do I need to configure?

Thanks again!



On 4/6/07, Martin Gainty <[EMAIL PROTECTED]> wrote:


 Good AfternoonCharles-

/WEB-INF/conf/axis2.xml
you would need to reconfigure the value for contextRoot element from axis2
to axis
 

HTH
Martin--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please
notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.


- Original Message -
*From:* Charles Ambrose <[EMAIL PROTECTED]>
*To:* axis-user@ws.apache.org
*Sent:* Friday, April 06, 2007 2:36 PM
*Subject:* How to change the ContextRoot of the StandAlone
SimpleAxis2Server


Hi guys!

I am unable to modify the root context of the services made available by
the stand-alone version of the SimpleAxis2Server of the standard
distribution of axis2 version 1.1.1.

Basically the default path of the services are:
http://localhost:8080/axis2/services. I would like to change this to:
http://localhost:8080/axis/services. From what I understand, I need to
modify the tag on axis2.xml: axis.

I still cannot access the path: http://localhost:8080/axis/services . It
re-directs to: http://localhost:8080/axis2/services.

How do I accomplish this?

Also, are there examples of how to create your own Embedded SimpleAxis2
Server?


Thanks!

Regards,

Jonathan



 




true
false
false
false





30



false





false

admin
axis2











axxis









false






false


false


false



















http://www.w3.org/2004/08/wsdl/in-only";
 class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/>
http://www.w3.org/2004/08/wsdl/in-out";
 class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>





8080























	
>












HTTP/1.1
chunked


HTTP/1.1
chunked














































	



	































	



	






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How to not use prefix "ns1"?

[Jess Fisher]

My SOAP always includes the prefix "ns1".
   
  
http://schemas.xmlsoap.org/soap/envelope/";>
  
  

  false
  
  
  
  
  

   
  What can I do so that it does not include the prefix "ns1" ? 
  For example: I just want this:
  
   

 
-
Don't get soaked.  Take a quick peek at the forecast 
 with theYahoo! Search weather shortcut.

Extracting information from soap messages-Beginner question

[Inder Dhillon]

Hello 

I have one more question, while writing the code for new handler I want to
use the messagecontext as argument to the method in my handler class. 
But I don't know how to invoke the methods of the inbuilt classes of axis2.
I'll really appreciate if someone can help me with this.

Actually I am building one handler to extract the xml tags from the soap
messages. So I need to use the message context.

Thanks in advance.
Inder

-Original Message-
From: Inder Dhillon [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 05, 2007 3:59 PM
To: axis-user@ws.apache.org
Subject: Extracting information from soap messages.

Hello

I am a new user of Axis2. I have one question that can we induce our handler
to extract the tags from the soap messages i.e. from both headers and body
into a file. And if we can then in which phase should I include this
handler. 

Thanks in advance.

Inder


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Question on Namespaces

[Anne Thomas Manes]

Please file a JIRA.

The only problem I see with your WSDL is that you need to remove the
"namespace" attributes from the  and 
declarations. They should be



But I'm sure that's not what's causing the problem. And certainly
Axis2 should not be changing the D09 element and placing it into no
namespace (xmlns="").

Having extraneous namespace declarations or using prefixes versus the
default shouldn't make a difference as long as the messages are
semantically equivalent. But changing the D09 element to no namespace
is a semantic change.

Anne

On 4/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

We have been running into a wall on this problem for about two weeks
(everything else in our system works), so I thought I would throw it out
to the community.  We have created a web service with several operations.
One operation returns an XML document that is defined by an XSD associated
with a standard.  We can not change the XSD for the standard, but can if
necessary change our WSDL that references it or the Java code that
dynamically constructs the XML payload/SOAP.  We use Axis2, the XML Beans
tools, and WSDL2Java to generate the Java classes to construct the XML.
For this newsgroup, we created a simple example of an XML schema and WSDL
(only a simplified version of one operation) that replicates the same
problem, but much less complex.

The namespaces in the payload corresponding to the standard need to be as
if it was a standalone XML document.

I originally tried the XMLBeans community, but no one there could help
track the problem.  However, they did suggest printing out the XML
structure, before it was returned to the web service client.  They are in
fact different (the XML constructed before its return and the XML received
by the web services client).  I wonder if this problem is related to the
attribute qualification, but don't know how to solve it.

1. XML Constructed
The XML constructed by XMLBeans before its return is as follows:
http://PolarisWS.ws4.ems.cognitech.com/types";>

  
http://www.nemsis.org
http://www.nemsis.org/media/XSD/EMSDemographicDataSet.xsd";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:nem="http://www.nemsis.org";>
  
Stuff
  

  


2. SOAP Message
The actual SOAP message received by the web services client (simple
example) looks like this:

http://PolarisWS.ws4.ems.cognitech.com/types";
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
  
http://www.nemsis.org
http://www.nemsis.org/media/XSD/EMSDemographicDataSet.xsd";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns="http://www.nemsis.org";>
  

http://www.nemsis.org";>Stuff
  

  




3. Desired SOAP Message/XML Document
We would like the payload corresponding to Test.xsd (defined later in this
message) to look something like the following:

http://www.nemsis.org
http://www.nemsis.org/media/XSD/EMSDemographicDataSet.xsd";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns="http://www.nemsis.org";>
  

Stuff
  


In other words, we want to get rid of the xmlns="" associated with D09 and
the xmlns="http://www.nemsis.org"; associated with D09_04.  The xmlns=""
only occurs when attributes are defined.


4. WSDL
Our WSDL looks like this.  Note that the elementFormDefault is qualified
and the attributeFormDefault is unqualified.  We can change the WSDL if
that would fix the problem.
WSDL (services.wsdl)

http://schemas.xmlsoap.org/wsdl/";
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
xmlns:ns1="http://PolarisWS.ws4.ems.cognitech.com/types";
xmlns:ns="http://PolarisWS.ws4.ems.cognitech.com";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
targetNamespace="http://PolarisWS.ws4.ems.cognitech.com";>





http://www.w3.org/2001/XMLSchema";

xmlns:types="http://PolarisWS.ws4.ems.cognitech.com/types";

targetNamespace="http://PolarisWS.ws4.ems.cognitech.com/types";
elementFormDefault="qualified" 
attributeFormDefault="unqualified"
xmlns:Q1="http://www.nemsis.org";>
http://www.nemsis.org";>






















   

Re: [Axis2] Using custom SSLSocketFactory or ssl connection

[Mahesh Rachakonda]

It is all working now, it turned out to be a CipherSuite limitation in
Entrust. I restricted the CipherSuite in custom SocketFactory create methods
and vioa! It all works!!

Thanks again, Aaron!

Mahesh

Re: Method that returns HashMap[]

[Tim Chan]

I'm using Axis-1.2

-Tim

---

Tim can you specify which version of AXIS you are using?


Regards

Nilesh


- Original Message 
From: Tim Chan <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Thursday, April 5, 2007 4:20:12 AM
Subject: Method that returns HashMap[]

Hi,

Can I get some pointers about implementing a service method that
returns HashMap[]?

In my implementation, the server method returns a HashMap[] w/ 3
HashMap objects.  \
However, on the client end, the array contains 3 null objects!

Any pointers on this?  Thanks.

-Tim

Info on transfer of HashMap via axis2?

[Tim Chan]

I've had little success writing a method that successfully returns a basic
HashMap object via axis2.  I tried searching for existing information but
had little success.  I'd appreciate any pointers.  Thanks.

-Tim

Question on Namespaces

[soller]

We have been running into a wall on this problem for about two weeks
(everything else in our system works), so I thought I would throw it out
to the community.  We have created a web service with several operations.
One operation returns an XML document that is defined by an XSD associated
with a standard.  We can not change the XSD for the standard, but can if
necessary change our WSDL that references it or the Java code that
dynamically constructs the XML payload/SOAP.  We use Axis2, the XML Beans
tools, and WSDL2Java to generate the Java classes to construct the XML.
For this newsgroup, we created a simple example of an XML schema and WSDL
(only a simplified version of one operation) that replicates the same
problem, but much less complex.

The namespaces in the payload corresponding to the standard need to be as
if it was a standalone XML document.

I originally tried the XMLBeans community, but no one there could help
track the problem.  However, they did suggest printing out the XML
structure, before it was returned to the web service client.  They are in
fact different (the XML constructed before its return and the XML received
by the web services client).  I wonder if this problem is related to the
attribute qualification, but don't know how to solve it.

1. XML Constructed
The XML constructed by XMLBeans before its return is as follows:
http://PolarisWS.ws4.ems.cognitech.com/types";>

  
http://www.nemsis.org
http://www.nemsis.org/media/XSD/EMSDemographicDataSet.xsd";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:nem="http://www.nemsis.org";>
  
Stuff
  

  


2. SOAP Message
The actual SOAP message received by the web services client (simple
example) looks like this:

http://PolarisWS.ws4.ems.cognitech.com/types";
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
  
http://www.nemsis.org
http://www.nemsis.org/media/XSD/EMSDemographicDataSet.xsd";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns="http://www.nemsis.org";>
  

http://www.nemsis.org";>Stuff
  

  




3. Desired SOAP Message/XML Document
We would like the payload corresponding to Test.xsd (defined later in this
message) to look something like the following:

http://www.nemsis.org
http://www.nemsis.org/media/XSD/EMSDemographicDataSet.xsd";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns="http://www.nemsis.org";>
  

Stuff
  


In other words, we want to get rid of the xmlns="" associated with D09 and
the xmlns="http://www.nemsis.org"; associated with D09_04.  The xmlns=""
only occurs when attributes are defined.


4. WSDL
Our WSDL looks like this.  Note that the elementFormDefault is qualified
and the attributeFormDefault is unqualified.  We can change the WSDL if
that would fix the problem.
WSDL (services.wsdl)

http://schemas.xmlsoap.org/wsdl/";
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
xmlns:ns1="http://PolarisWS.ws4.ems.cognitech.com/types";
xmlns:ns="http://PolarisWS.ws4.ems.cognitech.com";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
targetNamespace="http://PolarisWS.ws4.ems.cognitech.com";>





http://www.w3.org/2001/XMLSchema";

xmlns:types="http://PolarisWS.ws4.ems.cognitech.com/types";

targetNamespace="http://PolarisWS.ws4.ems.cognitech.com/types";
elementFormDefault="qualified" 
attributeFormDefault="unqualified"
xmlns:Q1="http://www.nemsis.org";>
http://www.nemsis.org";>

















































http://schemas.xmlsoap.org/soap/http"; />




http://PolarisWS.ws4.ems.cognitech.com"; use="literal" />


http://PolarisWS.ws4.ems.cognitech.com"; use="literal" />

Re: [Axis2] Using custom SSLSocketFactory or ssl connection

[Shaoguang Cong]

Figured it out.  I thought about it too much.  All needed is to create a new 
Protocol using the custom factory and then call Protocol.registerProtocol. 
   
  So missed Axis 1.x that handles this with just one simple property :)
   
  Thanks.
  Shaoguang

Shaoguang Cong <[EMAIL PROTECTED]> wrote:
  Thanks, Mahesh.  I looked at it and have my test http client talking to 
the Axis 2 server successfully.  
   
  How do you plug it into the Axis 2 client? Are you using the WSDL2Java 
generated stub?
   

  Shaoguang

Mahesh Rachakonda <[EMAIL PROTECTED]> wrote:
  Shaoguang,

Take a look at this web page, this has three different examples on how to 
implement your own SecureProtocolSocketFactory.

http://jakarta.apache.org/commons/httpclient/sslguide.html 

Mahesh


  On 4/6/07, Shaoguang Cong <[EMAIL PROTECTED]> wrote: I'm trying to solve 
the same problem. Could you post your LenientSslSocketFactory class? I'd like 
to know how you associate it with the trustManagers.
   
  Thanks.
  Shaoguang



-
  Finding fabulous fares is fun.
Let Yahoo! FareChase search your favorite travel sites to find flight and hotel 
bargains.

 
-
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.

WSDL and ant build errors

[[p e r c e p t i c o n]]

Hello Experts,

I apologize for the ganged topics, but they might be related...

i'm running wsdl2java like this

C:\axis2-1.1.1\bin>wsdl2java -uri http://someURL/Service.asmx?wsdl
  -ss -t

and receiving the following errors

log4j:WARN No appenders could be found for logger (
org.apache.axis2.addressing.wsdl.WSDL11ActionHelper).

log4j:WARN Please initialize the log4j system properly.

(Location of error unknown)org.apache.xml.utils.URI$MalformedURIException:
Cannot initialize URI with empty parameters

(Location of error unknown)org.apache.xml.utils.URI$MalformedURIException:
Cannot initialize URI with empty parameters

then i run

C:\ant

and receive the following errors


compile.src:
   [javac] Compiling 7 source files to C:\axis2-1.1.1\bin\build\classes
   [javac] C:\axis2-
1.1.1\bin\src\us\datacore\invisalign\DoctorLocatorServiceMessageReceiverInOut.java:47:cannot
find symbol
   [javac] symbol  : method fromOM(org.apache.axiom.om.OMElement,
java.lang.Class,java.util.Map)
   [javac] location: class
us.datacore.invisalign.DoctorLocatorServiceMessageReceiverInOut (
us.datacore.invisalign.GetDoctor)
fromOM(
   [javac]^
   [javac] C:\axis2-
1.1.1\bin\src\us\datacore\invisalign\DoctorLocatorServiceMessageReceiverInOut.java:55:cannot
find symbol
   [javac] symbol  : method toEnvelope(org.apache.axiom.soap.SOAPFactory,
us.datacore.invisalign.GetDoctorResponse,boolean)
   [javac] location: class
us.datacore.invisalign.DoctorLocatorServiceMessageReceiverInOut
   [javac] envelope =
toEnvelope(getSOAPFactory(msgContext), param5, false);
   [javac]^


my questions are as follows

1). what does this mean :(Location of error
unknown)org.apache.xml.utils.URI$MalformedURIException: Cannot initialize
URI with empty parameters
and how do i resolve it?

2). how do i resolve these

  [javac] C:\axis2-
1.1.1\bin\src\us\datacore\invisalign\DoctorLocatorServiceMessageReceiverInOut.java:47:cannot
find symbol
   [javac] symbol  : method fromOM(org.apache.axiom.om.OMElement,
java.lang.Class,java.util.Map)
   [javac] location: class
us.datacore.invisalign.DoctorLocatorServiceMessageReceiverInOut(
us.datacore.invisalign.GetDoctor)
fromOM(
   [javac]^
   [javac] C:\axis2-
1.1.1\bin\src\us\datacore\invisalign\DoctorLocatorServiceMessageReceiverInOut.java:55:cannot
find symbol
   [javac] symbol  : method toEnvelope(org.apache.axiom.soap.SOAPFactory,
us.datacore.invisalign.GetDoctorResponse,boolean)
   [javac] location: class
us.datacore.invisalign.DoctorLocatorServiceMessageReceiverInOut
   [javac] envelope =
toEnvelope(getSOAPFactory(msgContext), param5, false);

and are the two related?


thanks so much

Re: How to change the ContextRoot of the StandAlone SimpleAxis2Server

[Martin Gainty]

Good AfternoonCharles-

/WEB-INF/conf/axis2.xml
you would need to reconfigure the value for contextRoot element from axis2 to 
axis
 

HTH
Martin--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

  - Original Message - 
  From: Charles Ambrose 
  To: axis-user@ws.apache.org 
  Sent: Friday, April 06, 2007 2:36 PM
  Subject: How to change the ContextRoot of the StandAlone SimpleAxis2Server


  Hi guys!

  I am unable to modify the root context of the services made available by the 
stand-alone version of the SimpleAxis2Server of the standard distribution of 
axis2 version 1.1.1.

  Basically the default path of the services are: 
http://localhost:8080/axis2/services. I would like to change this to: 
http://localhost:8080/axis/services. From what I understand, I need to modify 
the tag on axis2.xml: axis.

  I still cannot access the path: http://localhost:8080/axis/services . It 
re-directs to: http://localhost:8080/axis2/services.

  How do I accomplish this?

  Also, are there examples of how to create your own Embedded SimpleAxis2 
Server? 


  Thanks!

  Regards,

  Jonathan 

Re: [Axis2] Using custom SSLSocketFactory or ssl connection

[Shaoguang Cong]

  Thanks, Mahesh.  I looked at it and have my test http client talking to the 
Axis 2 server successfully.  
   
  How do you plug it into the Axis 2 client? Are you using the WSDL2Java 
generated stub?
   

  Shaoguang

Mahesh Rachakonda <[EMAIL PROTECTED]> wrote:
  Shaoguang,

Take a look at this web page, this has three different examples on how to 
implement your own SecureProtocolSocketFactory.

http://jakarta.apache.org/commons/httpclient/sslguide.html 

Mahesh


  On 4/6/07, Shaoguang Cong <[EMAIL PROTECTED]> wrote: I'm trying to solve 
the same problem. Could you post your LenientSslSocketFactory class? I'd like 
to know how you associate it with the trustManagers.
   
  Thanks.
  Shaoguang



 
-
Finding fabulous fares is fun.
Let Yahoo! FareChase search your favorite travel sites to find flight and hotel 
bargains.

How to change the ContextRoot of the StandAlone SimpleAxis2Server

[Charles Ambrose]

Hi guys!

I am unable to modify the root context of the services made available by the
stand-alone version of the SimpleAxis2Server of the standard distribution of
axis2 version 1.1.1.

Basically the default path of the services are:
http://localhost:8080/axis2/services. I would like to change this to:
http://localhost:8080/axis/services. From what I understand, I need to
modify the tag on axis2.xml: axis.

I still cannot access the path: http://localhost:8080/axis/services . It
re-directs to: http://localhost:8080/axis2/services.

How do I accomplish this?

Also, are there examples of how to create your own Embedded SimpleAxis2
Server?


Thanks!

Regards,

Jonathan

Re: [Axis2] Using custom SSLSocketFactory or ssl connection

[Mahesh Rachakonda]

Shaoguang,

Take a look at this web page, this has three different examples on how to
implement your own SecureProtocolSocketFactory.

http://jakarta.apache.org/commons/httpclient/sslguide.html

Mahesh


On 4/6/07, Shaoguang Cong <[EMAIL PROTECTED]> wrote:


I'm trying to solve the same problem. Could you post your
LenientSslSocketFactory class? I'd like to know how you associate it with
the trustManagers.

Thanks.
Shaoguang

Re: [Axis2] Using custom SSLSocketFactory or ssl connection

[Mahesh Rachakonda]

Hi Aaron,

Thank you for your helpful note. I implemented a custom
SecureProtocolSocketFactory, which was very straighforward. I unit-tested it
to be creating connections alright. Then I plug it into my Axis2 client
code, and I start seeing NullPointerExceptions coming from the stubs
(WSDL2Java generated). I am still trying to figure out why with DEBUG and
SSL trace options enabled. But it doesn't seem to be directly related to
connection creation. Here is the snippet of the logs when I try to invoke an
operation named "getProxyNumber".

It is printing to debug (not as errors) that providers BC and JuiCE could
not be added. I am not sure if they are required, as the same client works
just fine without my custom factory.

Have you seen anything like this before? Any helpful pointers are sincerely
appreciated.

Thanks,

Mahesh

DEBUG - Handler RequestURIBasedDispatcher added to Phase Transport
DEBUG - Handler SOAPActionBasedDispatcher added to Phase Transport
DEBUG - Handler AddressingBasedDispatcher added to Phase Dispatch
DEBUG - Handler SOAPMessageBodyBasedDispatcher added to Phase Dispatch
DEBUG - Handler InstanceDispatcher added to Phase Dispatch
DEBUG - Handler RequestURIBasedDispatcher added to Phase Dispatch
DEBUG - Handler SOAPActionBasedDispatcher added to Phase Dispatch
DEBUG - Handler AddressingBasedDispatcher added to Phase Dispatch
DEBUG - Handler SOAPMessageBodyBasedDispatcher added to Phase Dispatch
DEBUG - Handler InstanceDispatcher added to Phase Dispatch
DEBUG - START_DOCUMENT:
DEBUG - START_ELEMENT: {
http://schemas.xmlsoap.org/soap/envelope/}Envelope:Envelope
DEBUG - Build the OMElelment EnvelopeBy the StaxSOAPModelBuilder
DEBUG - START_ELEMENT: {
http://schemas.xmlsoap.org/soap/envelope/}Header:Header
DEBUG - Build the OMElelment HeaderBy the StaxSOAPModelBuilder
DEBUG - END_ELEMENT: {
http://schemas.xmlsoap.org/soap/envelope/}Header:Header
DEBUG - START_ELEMENT: {http://schemas.xmlsoap.org/soap/envelope/}Body:Body
DEBUG - Build the OMElelment BodyBy the StaxSOAPModelBuilder
DEBUG - START_ELEMENT: {
http://cc.proxy.mydomain.com}getProxyNumber:getProxyNumber
DEBUG - Build the OMElelment getProxyNumberBy the StaxSOAPModelBuilder
DEBUG - START_ELEMENT: {http://cc.proxy.mydomain.com}in0:in0
DEBUG - Build the OMElelment in0By the StaxSOAPModelBuilder
DEBUG - CHARACTERS: [372]
DEBUG - END_ELEMENT: {http://cc.proxy.mydomain.com}in0:in0
DEBUG - END_ELEMENT: {
http://cc.proxy.mydomain.com}getProxyNumber:getProxyNumber
DEBUG - END_ELEMENT: {http://schemas.xmlsoap.org/soap/envelope/}Body:Body
DEBUG - END_ELEMENT: {
http://schemas.xmlsoap.org/soap/envelope/}Envelope:Envelope
DEBUG - START_ELEMENT: {
http://schemas.xmlsoap.org/soap/envelope/}Envelope:Envelope
DEBUG - Build the OMElelment EnvelopeBy the StaxSOAPModelBuilder
DEBUG - START_ELEMENT: {
http://schemas.xmlsoap.org/soap/envelope/}Header:Header
DEBUG - Build the OMElelment HeaderBy the StaxSOAPModelBuilder
DEBUG - END_ELEMENT: {
http://schemas.xmlsoap.org/soap/envelope/}Header:Header
DEBUG - START_ELEMENT: {http://schemas.xmlsoap.org/soap/envelope/}Body:Body
DEBUG - Build the OMElelment BodyBy the StaxSOAPModelBuilder
DEBUG - START_ELEMENT: {
http://cc.proxy.mydomain.com}getProxyNumber:getProxyNumber
DEBUG - Build the OMElelment getProxyNumberBy the StaxSOAPModelBuilder
DEBUG - START_ELEMENT: {http://cc.proxy.mydomain.com}in0:in0
DEBUG - Build the OMElelment in0By the StaxSOAPModelBuilder
DEBUG - CHARACTERS: [372]
DEBUG - END_ELEMENT: {http://cc.proxy.mydomain.com}in0:in0
DEBUG - END_ELEMENT: {
http://cc.proxy.mydomain.com}getProxyNumber:getProxyNumber
DEBUG - END_ELEMENT: {http://schemas.xmlsoap.org/soap/envelope/}Body:Body
DEBUG - END_ELEMENT: {
http://schemas.xmlsoap.org/soap/envelope/}Envelope:Envelope
DEBUG - Canonicalizer.register(
http://www.w3.org/TR/2001/REC-xml-c14n-20010315,
org.apache.xml.security.c14n.implementations.Canonicalizer20010315OmitComments
)
DEBUG - Canonicalizer.register(
http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments,
org.apache.xml.security.c14n.implementations.Canonicalizer20010315WithComments
)
DEBUG - Canonicalizer.register(http://www.w3.org/2001/10/xml-exc-c14n#,
org.apache.xml.security.c14n.implementations.Canonicalizer20010315ExclOmitComments
)
DEBUG - Canonicalizer.register(
http://www.w3.org/2001/10/xml-exc-c14n#WithComments,
org.apache.xml.security.c14n.implementations.Canonicalizer20010315ExclWithComments
)
DEBUG - Transform.register(http://www.w3.org/2000/09/xmldsig#base64,
org.apache.xml.security.transforms.implementations.TransformBase64Decode)
DEBUG - Transform.register(http://www.w3.org/TR/2001/REC-xml-c14n-20010315,
org.apache.xml.security.transforms.implementations.TransformC14N)
DEBUG - Transform.register(
http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments,
org.apache.xml.security.transforms.implementations.TransformC14NWithComments
)
DEBUG - Transform.register(http://www.w3.org/2001/10/xml-exc-c14n#,
org.apache.xml.security.transfor

Re: [Axis2] Using custom SSLSocketFactory or ssl connection

[Shaoguang Cong]

I'm trying to solve the same problem. Could you post your 
LenientSslSocketFactory class? I'd like to know how you associate it with the 
trustManagers.
   
  Thanks.
  Shaoguang

aaron aston <[EMAIL PROTECTED]> wrote:
  I think I just did this to support self-signed certs ...  Axis2 uses the 
Apache HttpClient instead of the 'normal' Java HttpURLConnection.  You can 
configure a new 'https' protocol using the HttpClient API, specifying your own 
socket factory.  

  Protocol protocol = new Protocol("https", new 
LenientSslSocketFactory(trustManagers), 443);
  Protocol.register("https", protocol);
  

  where LenientSslSocketFactory implements the HttpClient interface 
SecureProtocolSocketFactory.
  

  er ... SecureProtocolSocketFactory doesn't seem to be related to 
javax.net.SocketFactory at all though ...
  

  Aaron.
  

  
On 5-Apr-07, at 4:39 PM, Mahesh Rachakonda wrote:

  I have been using Axis2 client with default JSSE to create ssl connections. 
Now I have a need to use Entrust certificate stores, so I can provide a JSSE 
SSLSocketFactory or a socket to Axis2. I am having a hard time figuring out how 
to go about it. I see that the previous versions (Axis) offered the following 
approach which is no longer available: 

org.apache.axis.AxisProperties.setProperty("axis.socketSecureFactory", 
"mypackage.MySSLSocketFactory");

Any help is sincerely appreciated. Thanks!

Mahesh

  











 
-
Now that's room service! Choose from over 150,000 hotels 
in 45,000 destinations on Yahoo! Travel to find your fit.

Re: [Axis2] Axis2 1.2 RC2 Released - SOAP problem

[Alistair Young]

sorted! was my fault (as usual!).

In the modular WSDL, the messages.wsdl file wasn't importing the
messages-types.xsd. It was imported in the root WSDL file but wasn't
making it's way down to the messages.wsdl file.

Removing the xsd import from the root WSDL and putting it in the
messages.wsdl solved the problem.

must blog that...

Alistair


-- 
mov eax,1
mov ebx,0
int 80h

> The problem only occurs if I split up the WSDL into modular parts:
>
> WSDL_1 includes types from two XSD files
> WSDL_1 imports bindings from WSDL_2
> bindings imports portTypes from WSDL_3
> portTypes imports messages from WSDL_4
>
> if I combine the whole lot into one WSDL file, it works.
>
> In both cases the SOAP on the wire is identical so it must be something to
> do with the generated classes in the service.
>
> Alistair
>
>
>
> --
> mov eax,1
> mov ebx,0
> int 80h
>
>> Using the nightly build.
>>
>> In my MessageReceiverInOut I get this error when invoking a web service:
>>
>> org.apache.axis2.AxisFault: First Element must contain the local name,
>> Envelope
>>
>> I've checked on the wire and this is what comes in:
>>
>> 
>> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>>  
>>  > xmlns="uk:ac:ox:oucs:ask:repo:ws:collectionmanager:messages:types">
>>  
>>  
>>  
>>  
>> 
>>
>> the problem happens when the message receiver calls fromOM():
>>  
>> (GetBriefcaseInputDocument)fromOM(
>> msgContext.getEnvelope().getBody().getFirstElement(),
>> GetBriefcaseInputDocument.class,
>> getEnvelopeNamespaces(msgContext.getEnvelope()));
>>
>> why would it say that Envelope is missing?
>>
>> thanks,
>>
>> Alistair
>>
>>
>>
>>
>> --
>> mov eax,1
>> mov ebx,0
>> int 80h
>>
>>> Hi Deepal
>>>
>>> Let me suggest that the problem arises because Axis2 doesn't take the
>>> service namespace into account. In my opinion services should be
>>> differentiated by both name and namespace. This should be the "key"
>>> for any mapping. Imagine that I have many clients wanting to deploy
>>> services - then it will be guaranteed that there are collisions in
>>> names. If they would use their own company namespace, in addition to
>>> that, this problem would be certainly avoided. Thanks.
>>>
>>> Regards,
>>> Angel
>>>
>>> On 4/6/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
 Hi All;

 I think this a major issue AFAIK , if some one generate services for
 two
 wsdls then he will get two services with the same name . Then the
 issue
 is how do you differentiate the two ? you can not deploy the files
 with
 the same name to services directory (only one will be picked up).
 Therefore I think we need to fix this b4 the release and I think we
 should either pick WSDL file name as the service aar name or the one
 of
 the service name in the wsdl as the service aar file name.

 Thanks
 Deepal

 Alistair Young wrote:

 >wsdl2java now creates the service as Service.aar instead of
 >ServiceName.aar. e.g. previously, if your service was called
 >MinervaService, you would get:
 >build/lib/MinervaService.aar
 >
 >now you get:
 >build/lib/Service.aar
 >
 >so you have to rename before deploying (as they're all called
 Service.aar
 >now)
 >
 >Alistair
 >
 >
 >
 >

 --
 Thanks,
 Deepal
 
 "The highest tower is built one brick at a time"



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Axis2 1.2 RC2 Released - SOAP problem

[Alistair Young]

The problem only occurs if I split up the WSDL into modular parts:

WSDL_1 includes types from two XSD files
WSDL_1 imports bindings from WSDL_2
bindings imports portTypes from WSDL_3
portTypes imports messages from WSDL_4

if I combine the whole lot into one WSDL file, it works.

In both cases the SOAP on the wire is identical so it must be something to
do with the generated classes in the service.

Alistair



-- 
mov eax,1
mov ebx,0
int 80h

> Using the nightly build.
>
> In my MessageReceiverInOut I get this error when invoking a web service:
>
> org.apache.axis2.AxisFault: First Element must contain the local name,
> Envelope
>
> I've checked on the wire and this is what comes in:
>
> 
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>   
>xmlns="uk:ac:ox:oucs:ask:repo:ws:collectionmanager:messages:types">
>   
>   
>   
>   
> 
>
> the problem happens when the message receiver calls fromOM():
>  
> (GetBriefcaseInputDocument)fromOM(
> msgContext.getEnvelope().getBody().getFirstElement(),
> GetBriefcaseInputDocument.class,
> getEnvelopeNamespaces(msgContext.getEnvelope()));
>
> why would it say that Envelope is missing?
>
> thanks,
>
> Alistair
>
>
>
>
> --
> mov eax,1
> mov ebx,0
> int 80h
>
>> Hi Deepal
>>
>> Let me suggest that the problem arises because Axis2 doesn't take the
>> service namespace into account. In my opinion services should be
>> differentiated by both name and namespace. This should be the "key"
>> for any mapping. Imagine that I have many clients wanting to deploy
>> services - then it will be guaranteed that there are collisions in
>> names. If they would use their own company namespace, in addition to
>> that, this problem would be certainly avoided. Thanks.
>>
>> Regards,
>> Angel
>>
>> On 4/6/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
>>> Hi All;
>>>
>>> I think this a major issue AFAIK , if some one generate services for
>>> two
>>> wsdls then he will get two services with the same name . Then the issue
>>> is how do you differentiate the two ? you can not deploy the files with
>>> the same name to services directory (only one will be picked up).
>>> Therefore I think we need to fix this b4 the release and I think we
>>> should either pick WSDL file name as the service aar name or the one of
>>> the service name in the wsdl as the service aar file name.
>>>
>>> Thanks
>>> Deepal
>>>
>>> Alistair Young wrote:
>>>
>>> >wsdl2java now creates the service as Service.aar instead of
>>> >ServiceName.aar. e.g. previously, if your service was called
>>> >MinervaService, you would get:
>>> >build/lib/MinervaService.aar
>>> >
>>> >now you get:
>>> >build/lib/Service.aar
>>> >
>>> >so you have to rename before deploying (as they're all called
>>> Service.aar
>>> >now)
>>> >
>>> >Alistair
>>> >
>>> >
>>> >
>>> >
>>>
>>> --
>>> Thanks,
>>> Deepal
>>> 
>>> "The highest tower is built one brick at a time"
>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Axis2 1.2 RC2 Released - SOAP problem

[Alistair Young]

Using the nightly build.

In my MessageReceiverInOut I get this error when invoking a web service:

org.apache.axis2.AxisFault: First Element must contain the local name,
Envelope

I've checked on the wire and this is what comes in:


http://schemas.xmlsoap.org/soap/envelope/";>








the problem happens when the message receiver calls fromOM():
 
(GetBriefcaseInputDocument)fromOM(
msgContext.getEnvelope().getBody().getFirstElement(),
GetBriefcaseInputDocument.class,
getEnvelopeNamespaces(msgContext.getEnvelope()));

why would it say that Envelope is missing?

thanks,

Alistair




-- 
mov eax,1
mov ebx,0
int 80h

> Hi Deepal
>
> Let me suggest that the problem arises because Axis2 doesn't take the
> service namespace into account. In my opinion services should be
> differentiated by both name and namespace. This should be the "key"
> for any mapping. Imagine that I have many clients wanting to deploy
> services - then it will be guaranteed that there are collisions in
> names. If they would use their own company namespace, in addition to
> that, this problem would be certainly avoided. Thanks.
>
> Regards,
> Angel
>
> On 4/6/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
>> Hi All;
>>
>> I think this a major issue AFAIK , if some one generate services for two
>> wsdls then he will get two services with the same name . Then the issue
>> is how do you differentiate the two ? you can not deploy the files with
>> the same name to services directory (only one will be picked up).
>> Therefore I think we need to fix this b4 the release and I think we
>> should either pick WSDL file name as the service aar name or the one of
>> the service name in the wsdl as the service aar file name.
>>
>> Thanks
>> Deepal
>>
>> Alistair Young wrote:
>>
>> >wsdl2java now creates the service as Service.aar instead of
>> >ServiceName.aar. e.g. previously, if your service was called
>> >MinervaService, you would get:
>> >build/lib/MinervaService.aar
>> >
>> >now you get:
>> >build/lib/Service.aar
>> >
>> >so you have to rename before deploying (as they're all called
>> Service.aar
>> >now)
>> >
>> >Alistair
>> >
>> >
>> >
>> >
>>
>> --
>> Thanks,
>> Deepal
>> 
>> "The highest tower is built one brick at a time"
>>
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANN] Apache AXIOM 1.2.3 Released

[Deepal Jayasinghe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
 
Apache AXIOM is a StAX-based, XML Infoset compliant object model which
supports on-demand building of the object tree. It supports a novel
"pull-through" model which allows one to turn off the tree building
and directly access the underlying pull event stream. It also has
built-in support for XML Optimized Packaging (XOP) and MTOM, the
combination of which allows XML to carry binary data efficiently  and
in a transparent manner. The combination of these results in a easy to
use API with a very high performant architecture!

Initialy developed as part of Apache Axis2, Apache AXIOM (AXIs Object
Model) is the core of Apache Axis2. However, it is a pure standalone
XML Infoset model with novel features and can be used independently of
Apache Axis2.

Please visit: http://ws.apache.org/commons/axiom/


Key Features


* Full XML Infoset compliant XML object model
* StAX based builders with on-demand building and pull-through
* XOP/MTOM support offering direct binary support
* Convenient SOAP Infoset API on top of AXIOM
* Two implementations included:
  o Linked list based implementation
  o W3C DOM supporting implementation
* High performant

 

What's New in This Release
==

This is release includes a set of  bug fixes which are necessary for
Axis2 release and  improvements to file caching.

- - The Apache Axiom Team.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
 
iD8DBQFGFhOmjOGcXNDx0CARAufEAJ9GwbwHEsy1sK11SDKdmyvF93nLowCeJV2r
GqqO5wc4ZX+M6AnQFIIXbY8=
=Bf/N
-END PGP SIGNATURE-



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re : Re : Re : Re : [Axis2] Axis2 1.2 RC2 Released

[Julien HENRY]

Thanks for your consideration, but I'm looking for a Maven 2 repository.

++
Julien

- Message d'origine 
De : Deepal Jayasinghe <[EMAIL PROTECTED]>
À : axis-user@ws.apache.org
Envoyé le : Vendredi, 6 Avril 2007, 10h20mn 31s
Objet : Re: Re : Re : Re : [Axis2] Axis2 1.2 RC2 Released

http://people.apache.org/~deepal/axis2/1.2-RC2/

Thanks
Deepal

Julien HENRY wrote:

> In
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2/
> I have :
> 1.2-SNAPSHOT
> SNAPSHOT
>
> In
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/axis2/
> I have :
> 1.1
>
> In http://repo1.maven.org/maven2/org/apache/axis2/axis2/ I have :
> 1.1
> 1.1.1
>
> Could you please help me to find 1.2-rc2?
>
> Thanks
>
> Julien
>
> - Message d'origine 
> De : Patrick Houbaux <[EMAIL PROTECTED]>
> À : axis-user@ws.apache.org
> Envoyé le : Jeudi, 5 Avril 2007, 18h31mn 21s
> Objet : Re: Re : Re : [Axis2] Axis2 1.2 RC2 Released
>
> Check links in this message below ;)
>
> Cheers,
> Patrick.
>
> Julien HENRY wrote:
>
>>Can't manage to find 1.2-rc2 in releases. The latest release seems to be 1.1.
>>
>>++
>>
>>Julien
>>
>>- Message d'origine 
>>De : Thilina Gunarathne <[EMAIL PROTECTED]>
>>À : axis-user@ws.apache.org
>>Envoyé le : Jeudi, 5 Avril 2007, 14h00mn 59s
>>Objet : Re: Re : [Axis2] Axis2 1.2 RC2 Released
>>
>>Snapshots,
>>http://people.apache.org/repo/m2-snapshot-repository/
>>
>>Releases,
>>http://people.apache.org/repo/m2-ibiblio-rsync-repository/
>>
>>~Thilina
>>
>>On 4/5/07,
>> Julien HENRY <[EMAIL PROTECTED]> wrote:
>>  
>>
>>>Do you plan to provide a Maven 2 repository ?
>>>
>>>++
>>>
>>>Julien
>>>
>>>- Message d'origine 
>>>De : Deepal Jayasinghe <[EMAIL PROTECTED]>
>>>À : "axis-dev@ws.apache.org" ;
>>>"axis-user@ws.apache.org" 
>>>Envoyé le : Mardi, 3 Avril 2007, 12h59mn 49s
>>>Objet : [Axis2] Axis2 1.2 RC2 Released
>>>
>>>
>>> Hi all,
>>>
>>> I uploaded Axis2 1.2 RC2 release artifacts. Please
>>> help us by downloading
>>>and reviewing them.
>>>
>>> Download locations :
>>> binary distributions-
>>>http://people.apache.org/~deepal/axis2/1.2-RC2/axis2-1.2-RC2.zip
>>> source distribution
>>>http://people.apache.org/~deepal/axis2/1.2-RC2/axis2-1.2-RC2-src.zip
>>> docs distribution
>>>http://people.apache.org/~deepal/axis2/1.2-RC2/axis2-1.2-RC2-docs.zip
>>> war distribution
>>> http://people.apache.org/~deepal/axis2/1.2-RC2/axis2.war
>>>
>>> jars
>>>http://people.apache.org/~deepal/maven/org.apache.axis2/jars/
>>>
>>> mars (addressing and soapmonitor)
>>>http://people.apache.org/~deepal/maven/org.apache.axis2/mars/
>>>
>>> poms
>>>http://people.apache.org/~deepal/maven/org.apache.axis2/poms/
>>>
>>>
>>> According to the release plan, I'm expecting to release Axis2 1.2 on
>>> 6th   April, 2007.
>>>
>>>
>>> Features included in the release :
>>> - WSDL 2.0 fully
>>> support
>>> (Reading , writing and codegen)
>>> - POJO – annotation
>>> - JAX-WS integration
>>> - JAX-WS -annotation
>>> - Un-wrapping (Response)
>>> - ADB - missing schema support
>>> - Maven2 support
>>> - JSON support
>>> - Binary serialization (Fast Inforset)
>>> - Multiple services support in code gen
>>> - HTTP code generation (both WSDL 1.1 and 2.0)
>>> - Fix/update helper mode
>>> - Custom deployers support
>>> - Message formatters
>>> - Message Builders
>>>
>>> In addition to above major features we have fixed numerous JIRA issues.
>>>
>>>
>>> Thanks,
>>>  Deepal
>>>
>>>
>>>
>>> 
>>> Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions
>>>! Profitez des connaissances, des opinions et des expériences des
>>>internautes sur Yahoo! Questions/Réponses.
>>>
>>>
>>  
>>
>
> -- 
> --
> | *Patrick Houbaux*
> | Senior Consultant
> | Eurostep ABEmail: [EMAIL PROTECTED]
> | Drottninggatan 68  Mobile: +33 611 192 943
> | SE-111 21 StockholmFax: +46 (0) 8-200 399
> | Sweden URL: http://www.eurostep.com
> |Skype name: phoubaux
> | Home address:
> | BAT A11
> | 12 Rue de Paris
> | F-78560 Le Port-Marly
> | France
> ---
>
> This message contains information that may be privileged or
> confidential and is the property of Eurostep Group. It is intended
> only for the person to whom it is addressed. If you are not the
> intended recipient, you are not authorized to read, print, retain,
> copy, disseminate, distribute, or use this message or any part
> thereof. If you receive this message in error, please notify the
> sender immediately and delete all copies of this message.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED] For
> additional commands, e-mail: [EMAIL PROTECTED]
>
>
> 
> Découvrez une nouvelle façon d'obtenir des r

Re : Re : Re : Re : [Axis2] Axis2 1.2 RC2 Released

[Julien HENRY]

Thanks for the explanation about differences between 1.2-SNAPSHOT and SNAPSHOT 
versions. I suppose I will have to wait for 1.2 final, as I don't want to use a 
snapshot repository in order to keep reproducible builds.

For future RC (and even alpha, beta), perhaps Axis 2 team should try to 
"release" (Maven meaning) artifacts, to allow a maximum amount of people to 
test it in "real" production configuration (no snapshot). This could lead to 
discover some nasty dependency mistakes, like with 1.1.1, where 2 artifacts are 
not available on ibiblio (woden-1.0.0M6 et  wsdl4j-1.6.2).

++

Julien

- Message d'origine 
De : Asankha C. Perera <[EMAIL PROTECTED]>
À : axis-user@ws.apache.org
Envoyé le : Vendredi, 6 Avril 2007, 9h31mn 02s
Objet : Re: Re : Re : Re : [Axis2] Axis2 1.2 RC2 Released




  

Hi Julien



As far as I know, an artifacts for RC releases have not been uploaded
to the maven repos. What you would find in the m2-snapshot-repository
are nightly build snapshots created off the 1.2 branch (i.e. if you are
looking at version "1.2-SNAPSHOT") and the trunk (i.e. under "SNAPSHOT"
version). 



I understand your concern, as I have a project dependent on Axis2 1.2
as well - and hence would suggest you point your pom to the
1.2-SNAPSHOT as its what will go into the 1.2 final release in the next
few days.



asankha



Julien HENRY wrote:

  
  
  In
  http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2/
I have :

1.2-SNAPSHOT

SNAPSHOT

  

  In 
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/axis2/
I have :

1.1

  

  In http://repo1.maven.org/maven2/org/apache/axis2/axis2/
I have :

1.1

1.1.1

  

Could you please help me to find 1.2-rc2?

  

Thanks

  

Julien

  

  

  


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]











___ 
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
Profitez des connaissances, des opinions et des expériences des internautes sur 
Yahoo! Questions/Réponses 
http://fr.answers.yahoo.com

Re: Re : Re : Re : [Axis2] Axis2 1.2 RC2 Released

[Deepal Jayasinghe]

http://people.apache.org/~deepal/axis2/1.2-RC2/

Thanks
Deepal

Julien HENRY wrote:

> In
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2/
> I have :
> 1.2-SNAPSHOT
> SNAPSHOT
>
> In
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/axis2/
> I have :
> 1.1
>
> In http://repo1.maven.org/maven2/org/apache/axis2/axis2/ I have :
> 1.1
> 1.1.1
>
> Could you please help me to find 1.2-rc2?
>
> Thanks
>
> Julien
>
> - Message d'origine 
> De : Patrick Houbaux <[EMAIL PROTECTED]>
> À : axis-user@ws.apache.org
> Envoyé le : Jeudi, 5 Avril 2007, 18h31mn 21s
> Objet : Re: Re : Re : [Axis2] Axis2 1.2 RC2 Released
>
> Check links in this message below ;)
>
> Cheers,
> Patrick.
>
> Julien HENRY wrote:
>
>>Can't manage to find 1.2-rc2 in releases. The latest release seems to be 1.1.
>>
>>++
>>
>>Julien
>>
>>- Message d'origine 
>>De : Thilina Gunarathne <[EMAIL PROTECTED]>
>>À : axis-user@ws.apache.org
>>Envoyé le : Jeudi, 5 Avril 2007, 14h00mn 59s
>>Objet : Re: Re : [Axis2] Axis2 1.2 RC2 Released
>>
>>Snapshots,
>>http://people.apache.org/repo/m2-snapshot-repository/
>>
>>Releases,
>>http://people.apache.org/repo/m2-ibiblio-rsync-repository/
>>
>>~Thilina
>>
>>On 4/5/07,
>> Julien HENRY <[EMAIL PROTECTED]> wrote:
>>  
>>
>>>Do you plan to provide a Maven 2 repository ?
>>>
>>>++
>>>
>>>Julien
>>>
>>>- Message d'origine 
>>>De : Deepal Jayasinghe <[EMAIL PROTECTED]>
>>>À : "axis-dev@ws.apache.org" ;
>>>"axis-user@ws.apache.org" 
>>>Envoyé le : Mardi, 3 Avril 2007, 12h59mn 49s
>>>Objet : [Axis2] Axis2 1.2 RC2 Released
>>>
>>>
>>> Hi all,
>>>
>>> I uploaded Axis2 1.2 RC2 release artifacts. Please
>>> help us by downloading
>>>and reviewing them.
>>>
>>> Download locations :
>>> binary distributions-
>>>http://people.apache.org/~deepal/axis2/1.2-RC2/axis2-1.2-RC2.zip
>>> source distribution
>>>http://people.apache.org/~deepal/axis2/1.2-RC2/axis2-1.2-RC2-src.zip
>>> docs distribution
>>>http://people.apache.org/~deepal/axis2/1.2-RC2/axis2-1.2-RC2-docs.zip
>>> war distribution
>>> http://people.apache.org/~deepal/axis2/1.2-RC2/axis2.war
>>>
>>> jars
>>>http://people.apache.org/~deepal/maven/org.apache.axis2/jars/
>>>
>>> mars (addressing and soapmonitor)
>>>http://people.apache.org/~deepal/maven/org.apache.axis2/mars/
>>>
>>> poms
>>>http://people.apache.org/~deepal/maven/org.apache.axis2/poms/
>>>
>>>
>>> According to the release plan, I'm expecting to release Axis2 1.2 on
>>> 6th   April, 2007.
>>>
>>>
>>> Features included in the release :
>>> - WSDL 2.0 fully
>>> support
>>> (Reading , writing and codegen)
>>> - POJO – annotation
>>> - JAX-WS integration
>>> - JAX-WS -annotation
>>> - Un-wrapping (Response)
>>> - ADB - missing schema support
>>> - Maven2 support
>>> - JSON support
>>> - Binary serialization (Fast Inforset)
>>> - Multiple services support in code gen
>>> - HTTP code generation (both WSDL 1.1 and 2.0)
>>> - Fix/update helper mode
>>> - Custom deployers support
>>> - Message formatters
>>> - Message Builders
>>>
>>> In addition to above major features we have fixed numerous JIRA issues.
>>>
>>>
>>> Thanks,
>>>  Deepal
>>>
>>>
>>>
>>> 
>>> Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions
>>>! Profitez des connaissances, des opinions et des expériences des
>>>internautes sur Yahoo! Questions/Réponses.
>>>
>>>
>>  
>>
>
> -- 
> --
> | *Patrick Houbaux*
> | Senior Consultant
> | Eurostep ABEmail: [EMAIL PROTECTED]
> | Drottninggatan 68  Mobile: +33 611 192 943
> | SE-111 21 StockholmFax: +46 (0) 8-200 399
> | Sweden URL: http://www.eurostep.com
> |Skype name: phoubaux
> | Home address:
> | BAT A11
> | 12 Rue de Paris
> | F-78560 Le Port-Marly
> | France
> ---
>
> This message contains information that may be privileged or
> confidential and is the property of Eurostep Group. It is intended
> only for the person to whom it is addressed. If you are not the
> intended recipient, you are not authorized to read, print, retain,
> copy, disseminate, distribute, or use this message or any part
> thereof. If you receive this message in error, please notify the
> sender immediately and delete all copies of this message.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED] For
> additional commands, e-mail: [EMAIL PROTECTED]
>
>
> 
> Découvrez une nouvelle façon d'obtenir des réponses à toutes vos
> questions ! Profitez des connaissances, des opinions et des
> expériences des internautes sur Yahoo! Questions/Réponses
> .


-- 
Thanks,
Deepal
.

Re: Re : Re : Re : [Axis2] Axis2 1.2 RC2 Released

[Asankha C. Perera]

Hi Julien

As far as I know, an artifacts for RC releases have not been uploaded
to the maven repos. What you would find in the m2-snapshot-repository
are nightly build snapshots created off the 1.2 branch (i.e. if you are
looking at version "1.2-SNAPSHOT") and the trunk (i.e. under "SNAPSHOT"
version). 

I understand your concern, as I have a project dependent on Axis2 1.2
as well - and hence would suggest you point your pom to the
1.2-SNAPSHOT as its what will go into the 1.2 final release in the next
few days.

asankha

Julien HENRY wrote:

  
  
  In
  http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2/
I have :
1.2-SNAPSHOT
SNAPSHOT
  
  In http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/axis2/
I have :
1.1
  
  In http://repo1.maven.org/maven2/org/apache/axis2/axis2/
I have :
1.1
1.1.1
  
Could you please help me to find 1.2-rc2?
  
Thanks
  
Julien
  
  
  




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re : Re : Re : [Axis2] Axis2 1.2 RC2 Released

[Julien HENRY]

In http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2/ 
I have :
1.2-SNAPSHOT
SNAPSHOT

In 
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/axis2/
 I have :
1.1

In http://repo1.maven.org/maven2/org/apache/axis2/axis2/ I have :
1.1
1.1.1

Could you please help me to find 1.2-rc2?

Thanks

Julien

- Message d'origine 
De : Patrick Houbaux <[EMAIL PROTECTED]>
À : axis-user@ws.apache.org
Envoyé le : Jeudi, 5 Avril 2007, 18h31mn 21s
Objet : Re: Re : Re : [Axis2] Axis2 1.2 RC2 Released





  
  

Check links in this message below ;)



Cheers,

Patrick.



Julien HENRY wrote:

  Can't manage to find 1.2-rc2 in releases. The latest release seems to be 1.1.

++

Julien

- Message d'origine 
De : Thilina Gunarathne <[EMAIL PROTECTED]>
À : axis-user@ws.apache.org
Envoyé le : Jeudi, 5 Avril 2007, 14h00mn 59s
Objet : Re: Re : [Axis2] Axis2 1.2 RC2 Released

Snapshots,
http://people.apache.org/repo/m2-snapshot-repository/

Releases,
http://people.apache.org/repo/m2-ibiblio-rsync-repository/

~Thilina

On 4/5/07, Julien HENRY <[EMAIL PROTECTED]> wrote:
  
  
Do you plan to provide a Maven 2 repository ?

++

Julien

- Message d'origine 
De : Deepal Jayasinghe <[EMAIL PROTECTED]>
À : "axis-dev@ws.apache.org" ;
"axis-user@ws.apache.org" 
Envoyé le : Mardi, 3 Avril 2007, 12h59mn 49s
Objet : [Axis2] Axis2 1.2 RC2 Released


 Hi all,

 I uploaded Axis2 1.2 RC2 release artifacts. Please help us by downloading
and reviewing them.

 Download locations :
 binary distributions-
http://people.apache.org/~deepal/axis2/1.2-RC2/axis2-1.2-RC2.zip
 source distribution
http://people.apache.org/~deepal/axis2/1.2-RC2/axis2-1.2-RC2-src.zip
 docs distribution
http://people.apache.org/~deepal/axis2/1.2-RC2/axis2-1.2-RC2-docs.zip
 war distribution
 http://people.apache.org/~deepal/axis2/1.2-RC2/axis2.war

 jars
http://people.apache.org/~deepal/maven/org.apache.axis2/jars/

 mars (addressing and soapmonitor)
http://people.apache.org/~deepal/maven/org.apache.axis2/mars/

 poms
http://people.apache.org/~deepal/maven/org.apache.axis2/poms/


 According to the release plan, I'm expecting to release Axis2 1.2 on
 6th   April, 2007.


 Features included in the release :
 - WSDL 2.0 fully support
 (Reading , writing and codegen)
 - POJO – annotation
 - JAX-WS integration
 - JAX-WS -annotation
 - Un-wrapping (Response)
 - ADB - missing schema support
 - Maven2 support
 - JSON support
 - Binary serialization (Fast Inforset)
 - Multiple services support in code gen
 - HTTP code generation (both WSDL 1.1 and 2.0)
 - Fix/update helper mode
 - Custom deployers support
 - Message formatters
 - Message Builders

 In addition to above major features we have fixed numerous JIRA issues.


 Thanks,
  Deepal



 
 Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions
! Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses.

  
  
  



-- 




--

| Patrick Houbaux

| Senior Consultant

| Eurostep ABEmail: [EMAIL PROTECTED]

| Drottninggatan 68  Mobile: +33 611 192 943

| SE-111 21 StockholmFax: +46 (0) 8-200 399

| Sweden URL: http://www.eurostep.com

|Skype name: phoubaux

| Home address: 

| BAT A11 

| 12 Rue de Paris 

| F-78560 Le Port-Marly

| France

---





This message contains information that may be privileged or confidential and is 
the property of Eurostep Group. It is intended only for the person to whom it 
is addressed. If you are not the intended recipient, you are not authorized to 
read, print, retain, copy, disseminate, distribute, or use this message or any 
part thereof. If you receive this message in error, please notify the sender 
immediately and delete all copies of this message.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]











___ 
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
Profitez des connaissances, des opinions et des expériences des internautes sur 
Yahoo! Questions/Réponses 
http://fr.answers.yahoo.com