Re: [axis2] woden/axis2 interop

[Eran Chinthaka]

Sorry for the late reply.

This is the progress so far from Axis2 side.

I started on populating AxisService from Woden. The code can be found in
WSDL20ToAxisServiceBuilder [1]. I was stuck with a problem there, but
will complete this asap. At the same time Deepal had completed ?wsdl2
generation.

About the suggestion made by Arthur, I'm not that convinced to go
through WSDL 1.1 to support WSDL 2.0. Once we are done with
WSDL20ToAxisServiceBuilder, we don't need to do the mentioned hack, IMO.


-- Chinthaka

[1] :
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/core/src/org/apache/axis2/description/WSDL20ToAxisServiceBuilder.java?view=markup
Chathura Herath wrote:
> Hi,
> 
> So here is where we stand. Basic skeleton of the integration is
> there.I called it skeleton because it need to handle the rpc case and
> not so urgent but eventually need to handle the policy stuff. you can
> run WSDL2Jave with -wv 2 which will engage the woden. It will not
> codegen successfully, there is a schema compilation issue and have to
> fix it. I am concentrating on the xmlbeans databinding right now.
> 
> The two Scenarios given above are the classic interop test and would
> be great to have. My guess is within two weeks we should be able to
> get the run time up and them we could see how the clients and servers
> generated with the isomorphic but two WSDL versions would interop. So
> i would say we will be able to have at least one interop scenario for
> the interop.
> 
> John you could see the WSDL20ToAxisServiceBuilder which is the center
> of the integration work.
> Oshini please send your patches often and do have a look at the latest
> code. I should commit more often cos you are working on it as well. I
> have changed it to work with the component model, i belive you
> followed that thread.
> Thanks
> Chathura
> 
> 
> 
> On 6/6/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
>> Oshani,
>>
>> can you please open a JIRA issue and keep uploading diff's as you
>> progress?
>>
>> thanks,
>> dims
>>
>> On 6/6/06, Oshani Seneviratne <[EMAIL PROTECTED]> wrote:
>> > Hi,
>> >
>> > With the help of the core Axis2 dev team, I'm also in the process of
>> > implementing the Axis2/Woden integration. At the moment, my efforts
>> are on
>> > populating the AxisService once a WSDL2.0 is bundled in a service
>> archive
>> > file and deployed on Axis2.
>> >
>> >
>> > >
>> > > There's a class called WSDL20ToAxisServiceBuilder in Axis2. I haven't
>> > looked at it yet, but is this the 'layer' between Woden and Axis2?
>> >
>> >
>> > AFAIK, yes. And I am using this class to populate the AxisService
>> from the
>> > Woden components.
>> >
>> > Hopefully I should be able to finish this by July 5th, so that the
>> scenarios
>> > mentioned earlier can be tested with Axis2.
>> >
>> > Oshani
>> >
>> >
>>
>>
>> -- 
>> Davanum Srinivas : http://wso2.com/blogs/
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Fw: Comments in AddressingBasedDispatcher

[Eran Chinthaka]

Hi David,

That was a comment put a long time back. Please ignore it. I just
deleted it anyway.



David Illsley wrote:
> Adding correct prefix. Sorry
> David
> - Forwarded by David Illsley/UK/IBM on 06/05/2006 11:00 AM -
> 
> David Illsley/UK/[EMAIL PROTECTED] wrote on 06/05/2006 10:58:35 AM:
> 
>> Hi all,
>> I've noticed the following comment in the AddressingBasedDispatcher:
>> // TODO this logic needed to be improved, as the Dispatching is 
>> almost guaranteed to fail
>> I've been using wsa:Action to dipatch recently and it seems to work and 
>> the logic looks fine to me.
>>
>> Does anyone know why it might not work and therefore what I need to do 
> to 
>> make it work reliably?
>> Thanks,
>> David
>>
>> -
>> 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]
> 
> 




signature.asc
Description: OpenPGP digital signature

Axis2/Woden Integration Scenario Explanation

[Eran Chinthaka]

Hi,

This will explain how the woden integration is happening with Axis2, as
requested during the last woden telecon.

I got the HotelReservationService.wsdl [1] from the woden repo and
generated java artifacts from it. Axis2 wsdl2java can generate both
skeletons (this is the skeleton of the service implementation which is
described by the wsdl) and stubs (this is used to invoke the service).
This step required to read the wsdl 2.0 documents through Woden, then
pump the information populated in Woden in to Axis2 data binding frameowrk.

Then I filled the methods in the skeleton to make it a dummy service and
deployed as web service in Axis2 engine.
Next, I used the above generated stub to invoke the service that was
deployed.
I could successfully complete the scenario getting a response for the
invocation. This is an *initial* sign which indicates that Axis2/Woden
integration is successful.

Things to do :
- I need to check other WSDLs
- need to improve Axis2 internals a bit more to make sure new MEP uris
and other new namespaces are integrated properly.
- improve ?wsdl20, if there are problems

How to try :
One can run Axis2 wsdl2java tool by running
org.apache.axis2.wsdl.WSDL2Code with the following command line options.

-uri
$AXIS2_HOME/modules/adb-codegen/test-resources/wsdl20/HotelReservationService.wsdl
-ss -sd -g -o  -p
org.apache.wodenintegration -wv 2

You will get stubs and skeletons for the given wsdl.

If required I can host this service in a public endpoint for you all to
invoke and see.

Thanks,
-- Chinthaka

[1] :
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/adb-codegen/test-resources/wsdl20/HotelReservationService.wsdl?view=markup



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Build for SVN snapshot at the revision 414289 fails

[Eran Chinthaka]

Hi Oleg,

This was fixed just now by Ruchith.

-- Chinthaka

Oleg Kalnichevski wrote:
> There appears to be a problem with the Rahas module
> 
> Oleg
> 
>  __  __
> |  \/  |__ _Apache__ ___
> | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
> |_|  |_\__,_|\_/\___|_||_|  v. 1.0.2
> 
> Attempting to download axiom-api-SNAPSHOT.jar.
> Attempting to download axiom-impl-SNAPSHOT.jar.
> Attempting to download axiom-dom-SNAPSHOT.jar.
> Attempting to download axis2-common-SNAPSHOT.jar.
> Attempting to download axis2-java2wsdl-SNAPSHOT.jar.
> Attempting to download axis2-codegen-SNAPSHOT.jar.
> Attempting to download axis2-core-SNAPSHOT.jar.
> Attempting to download axis2-adb-SNAPSHOT.jar.
> Attempting to download axis2-jibx-SNAPSHOT.jar.
> Attempting to download axis2-xmlbeans-SNAPSHOT.jar.
> Attempting to download wss4j-SNAPSHOT.jar.
> Attempting to download neethi-SNAPSHOT.jar.
> Attempting to download woden-SNAPSHOT.jar.
> build:start:
> 
> java:prepare-filesystem:
> 
> java:compile:
> [echo] Compiling
> to /home/oleg/src/apache.org/webservices/axis2/modules/rahas/target/classes
> 
> BUILD FAILED
> File.. /home/oleg/src/apache.org/webservices/axis2/modules/rahas/maven.xml
> Element... copy
> Line.. 39
> Column 81
> Warning: Could not find
> file 
> /home/oleg/src/apache.org/webservices/axis2/modules/rahas/src/META-INF/module.xml
>  to copy.
> Total time: 55 seconds
> Finished at: Wed Jun 14 17:31:55 CEST 2006
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Build for SVN snapshot at the revision 414289 fails

[Eran Chinthaka]

Hi Oleg,

This is strange. I just got the whole build successful. Can you send us
with the test-report to check what has gone wrong ?

You can see the test report in
$YOUR_AXIS_ROOT/modules/integration/target/test-reports/TEST-org.apache.axis2.security.rahas.ConversationScenario3Test.txt.

-- Chinthaka

Oleg Kalnichevski wrote:
> On Wed, 2006-06-14 at 23:29 +0530, Eran Chinthaka wrote:
>> Hi Oleg,
>>
>> This was fixed just now by Ruchith.
>>
>> -- Chinthaka
>>
> 
> Hi Chinthaka,
> 
> SVN trunk still does not build due to a test case failure. I did update
> local dependencies prior to running the build
> 
> Oleg
> ---
> test:test:
> ...
> [junit] [ERROR] TEST
> org.apache.axis2.security.rahas.ConversationScenario3Test FAILED
> ...
> 
> BUILD FAILED
> File.. 
> /home/oleg/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly
> Element... maven:reactor
> Line.. 217
> Column 9
> Unable to obtain goal [multiproject:install-callback]
> -- /home/oleg/.maven/cache/maven-test-plugin-1.6.2/plugin.jelly:181:54:
>  There were test failures.
> Total time: 13 minutes 26 seconds
> Finished at: Wed Jun 14 20:36:45 CEST 2006
> 
> 
> 
> 
> 
>> Oleg Kalnichevski wrote:
>>> There appears to be a problem with the Rahas module
>>>
>>> Oleg
>>> 
>>>  __  __
>>> |  \/  |__ _Apache__ ___
>>> | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
>>> |_|  |_\__,_|\_/\___|_||_|  v. 1.0.2
>>>
>>> Attempting to download axiom-api-SNAPSHOT.jar.
>>> Attempting to download axiom-impl-SNAPSHOT.jar.
>>> Attempting to download axiom-dom-SNAPSHOT.jar.
>>> Attempting to download axis2-common-SNAPSHOT.jar.
>>> Attempting to download axis2-java2wsdl-SNAPSHOT.jar.
>>> Attempting to download axis2-codegen-SNAPSHOT.jar.
>>> Attempting to download axis2-core-SNAPSHOT.jar.
>>> Attempting to download axis2-adb-SNAPSHOT.jar.
>>> Attempting to download axis2-jibx-SNAPSHOT.jar.
>>> Attempting to download axis2-xmlbeans-SNAPSHOT.jar.
>>> Attempting to download wss4j-SNAPSHOT.jar.
>>> Attempting to download neethi-SNAPSHOT.jar.
>>> Attempting to download woden-SNAPSHOT.jar.
>>> build:start:
>>>
>>> java:prepare-filesystem:
>>>
>>> java:compile:
>>> [echo] Compiling
>>> to /home/oleg/src/apache.org/webservices/axis2/modules/rahas/target/classes
>>>
>>> BUILD FAILED
>>> File.. 
>>> /home/oleg/src/apache.org/webservices/axis2/modules/rahas/maven.xml
>>> Element... copy
>>> Line.. 39
>>> Column 81
>>> Warning: Could not find
>>> file 
>>> /home/oleg/src/apache.org/webservices/axis2/modules/rahas/src/META-INF/module.xml
>>>  to copy.
>>> Total time: 55 seconds
>>> Finished at: Wed Jun 14 17:31:55 CEST 2006
>>>
>>>
>>>
>>>
>>> -
>>> 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]
> 
> 




signature.asc
Description: OpenPGP digital signature

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

[Eran Chinthaka]

Bille (JIRA) wrote:
> [ 
> http://issues.apache.org/jira/browse/AXIS2-801?page=comments#action_12415618 
> ] 
> 
> Bille commented on AXIS2-801:
> -
> 
> since my last comment mysteriously faded away, here again:
> Hi Eran,
> 
> Three things is left concerning the SOAP Version.
> 1) I read that Axis2 uses SOAP 1.2 per default, so I wondered why my 
> SOAP-response is SOAP 1.1. I used SOAP12Factory to build the SOAPFault, so 
> why this ?

This is bit strange to me. Is the request message you received is SOAP
1.1 ? Then we reply using SOAP 1.1. But in that case if you have
explicitly made the objects using SOAP12Factory, it can not happen.
Please let us know where you are trying to do this and the request you get.
Can you help to reproduce this problem, so that I can look in to this
better.

> 2) How can I set that the server is the errorcause, till the response says 
> 'Client' ?

Where do u wanna do this? If its within the Service implementation
class, first get access to the message context (this [1] might help you
in doing that). Then if you only need to change the fault code,

SOAPFactory soapFactory;
if (inMessageContext.isSOAP11()) {
soapFactory = OMAbstractFactory.getSOAP11Factory();
} else {
soapFactory = OMAbstractFactory.getSOAP12Factory();
}

soapFaultCode = soapFactory.createSOAPFaultCode();
SOAPFaultValue soapFaultValue =
soapFactory.createSOAPFaultValue(soapFaultCode);
soapFaultValue.setText(new QName("Client"));

inMessageContext.setProperty(SOAP12Constants.SOAP_FAULT_CODE_LOCAL_NAME,
soapFaultCode);

> 3) If I don't use stubs and skeletons from wsdl2java generation, do I have to 
> create the SOAPFaults manually like I did? Or is there a nicer way to do 
> that. If manually, so then Userexptions-classes do not make really sense, do 
> they?

Did u read this [2] ?

-- Chinthaka

[1] : http://www.wso2.net/kb/106
[2] : http://www.wso2.net/kb/171



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Build for SVN snapshot at the revision 414289 fails

[Eran Chinthaka]

Hi Oleg,

create-lib won't update the maven repo.

Anyway, it seems some problem here. I heard some one else also
complained about this. Can you please post your configuration here.

Mr.Rampart (Ruchith), I hope you are the right person to help Oleg :)

-- Chinthaka


Oleg Kalnichevski wrote:
> On Thu, 2006-06-15 at 09:46 +0530, Eran Chinthaka wrote:
>> Hi Oleg,
>>
>> This is strange. I just got the whole build successful. Can you send us
>> with the test-report to check what has gone wrong ?
>>
>> You can see the test report in
>> $YOUR_AXIS_ROOT/modules/integration/target/test-reports/TEST-org.apache.axis2.security.rahas.ConversationScenario3Test.txt.
>>
>> -- Chinthaka
>>
> 
> Chinthaka,
> 
> I ran svn up and maven create-lib prior to running the build.
> ConversationScenario3Test is still failing for me
> 
> Oleg
> ---
> 
> Testsuite: org.apache.axis2.security.rahas.ConversationScenario3Test
> Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 4.455 sec
> 
> - Standard Output ---
> Server started on port .[SimpleHTTPServer] Stop called
> Server stopped .[SimpleHTTPServer] Stop called
> -  ---
> - Standard Error -
> Jun 15, 2006 12:01:04 PM org.apache.axis2.deployment.DeploymentEngine
> doDeploy
> INFO: Deploying module : addressing
> Jun 15, 2006 12:01:04 PM org.apache.axis2.deployment.DeploymentEngine
> doDeploy
> INFO: Deploying module : rahas
> Jun 15, 2006 12:01:05 PM org.apache.axis2.deployment.DeploymentEngine
> doDeploy
> INFO: Deploying module : rampart
> Jun 15, 2006 12:01:05 PM
> org.apache.axis2.transport.http.server.DefaultConnectionListener run
> INFO: Listening on port 
> Jun 15, 2006 12:01:07 PM org.apache.axis2.deployment.DeploymentEngine
> prepareRepository
> INFO: no services directory found , new one created
> Jun 15, 2006 12:01:07 PM org.apache.axis2.deployment.DeploymentEngine
> doDeploy
> INFO: Deploying module : addressing
> Jun 15, 2006 12:01:08 PM org.apache.axis2.deployment.DeploymentEngine
> doDeploy
> INFO: Deploying module : rahas
> Jun 15, 2006 12:01:08 PM org.apache.axis2.deployment.DeploymentEngine
> doDeploy
> INFO: Deploying module : rampart
> org.apache.axis2.AxisFault: WSDoAllReceiver: Request does not contain
> required Security header
>   at
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287)
>   at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:451)
>   at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:393)
>   at
> org.apache.axis2.security.rahas.TestClient.testConversation(TestClient.java:95)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:585)
>   at junit.framework.TestCase.runTest(TestCase.java:154)
>   at junit.framework.TestCase.runBare(TestCase.java:127)
>   at junit.framework.TestResult$1.protect(TestResult.java:106)
>   at junit.framework.TestResult.runProtected(TestResult.java:124)
>   at junit.framework.TestResult.run(TestResult.java:109)
>   at junit.framework.TestCase.run(TestCase.java:118)
>   at junit.framework.TestSuite.runTest(TestSuite.java:208)
>   at junit.framework.TestSuite.run(TestSuite.java:203)
>   at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:325)
>   at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:536)
> Caused by: java.lang.Exception: org.apache.axis2.AxisFault:
> WSDoAllReceiver: Request does not contain required Security header
>   at
> org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiver.java:280)
>   at
> org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.java:100)
>   at
> org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:82)
>   at org.apache.axis2.engine.Phase.invoke(Phase.java:380)
>   at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:500)
>   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:470)
>   at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
>   at
> org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:238)
>   at
> org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.doService(DefaultHttpSer

Re: [Axis2] Initial JAX-WS Implementation

[Eran Chinthaka]

Hi Nicholas and IBM team,

I'd say this is great work.

I'd like to see some explanation on how this is implemented on Axis2. I
agree that code is the best document, but if we can have an explanation,
it will be very easy for all of us to understand it and help within a
short period of time. Perhaps the guys here knows Axis2 internals better
than anyone else, there can be improvement suggestions as well.

Can one of you please volunteer to do that? I know that will be a big
document, but it will be beneficial.

(One additional question. If this yet another module and if it requires
jdk5, then we need to do a small trick for people using jdk14 to not
have problems. I think Dims had already done to one of the modules.)

-- Chinthaka

Nicholas L Gallardo wrote:
> The IBM Web services team has been developing a JAX-WS 2.0 implementation 
> that we will contribute to Apache, which uses Axis2 as it's core runtime. 
> It is an initial drop, but we intend to continue this development in 
> Apache open source.  Given the increased interest that has been displayed 
> on the mailing list, we will be opening a JIRA issue with a patch 
> containing code that we would like to have considered for contribution as 
> a jumpstart for the support.
> 
> This is just a first pass and is intended to be a starting point to allow 
> the Apache community involvement.  The IBM Web services team would like to 
> participate in building a JAX-WS 2.0 implementation in conjunction with 
> the Apache community. 
> 
> Developers that have participating in developing this drop, and are 
> planning to continue are the following:
> 
> Nick Gallardo
> Rich Scheuerle
> Jeff Barrett
> Nikhil Thaker
> Mike Rheinheirmer
> Brent Ulbricht
> Dan Sedov
> Lizet Ernand
> Samuel Isokpunwu
> 
> 
> Code structure:
> 
> This code has been built as a module under the Axis2 root in 
> modules/jaxws.
> - Maven enabled
> - Java 5 enabled
> - Verification tests included (many more to come)
> 
> As we've started developing this code, the goal has been to re-use as much 
> of the underlying Axis2 runtime as possible.  This includes making use of 
> the existing ServiceClient API on the client and the MessageReceiver API 
> for services. 
> 
> 
> 
> Contents:
> 
> Client
> ---
> Support for JAX-WS javax.xml.ws.Dispatch
> * Parameter types supported: 
>   - JAX-B (using JAXBContext) 
>   - javax.xml.transform.Source (StreamSource, DOMSource, SAXSource)
>   - String (non-spec)
> 
> * Invocation patterns supported:
>   - sync: invoke
>   - one-way: invokeOneWay
>   - async: invokeAsync (callback only) 
> 
> * Usage modes
>   - PAYLOAD (SOAP Body contents)
>   - MESSAGE (the entire SOAP Envelope)
> 
> 
> Service
> ---
> Support for javax.xml.ws.Provider style endpoints
> * Parameter types
>   - javax.xml.transform.Source (StreamSource, DOMSource, SAXSource)
>   - String (non-spec)
> 
> * Usage modes
>   - PAYLOAD only (MESSAGE requires annotations support for 
> javax.xml.ws.ServiceMode)
> 
> 
> 
> Development activity in progress: 
> 
> * SAAJ SOAPMessage support for both the Dispatch and Provider
> * Fault processing
> * Attachments
> * SOAP 1.2 support 
> * Annotations support for Provider
> * JAXWSMessageReceiver with support for pluggable dispatchers and server 
>   side application handlers
> 
> 
> Again, this is our first step here.  We look forward to working with the 
> Apache Web services community on furthering this implementation.  We 
> welcome the community's feedback.
> 
> Regards,
> 
> The IBM Web services team
> 




signature.asc
Description: OpenPGP digital signature

Re: [Proposal][Axis2][Axiom] Adding writable capability to OM elements

[Eran Chinthaka]

Ajith,

I'd like to suggest a small change for your proposal.

> Hi All,
> There have been some talk about performance improvements for Axis2
> next steps. So here is a small proposal of how to do a possible
> optimization with AXIOM and ADB.
> 
> 1. AXIOM needs to have an interface that allows a XMLStreamWriter to
> passed. This allows the implementer (of the interface) to have code
> that directly uses the writer. (Currently the OMDataSource has the
> necessary methods. We actually need only one, the write method).
> 
> 2. We have a special OMElement abstract class that implements the
> OMDataSource that has a constructor taking in an ADBBean.

OMDataSource having dependency on ADBBean? I think u didn't mean it :).

Let me re-phrase this. Ajith, please confirm if you agree.

There will be a new OMElement implementation (say,
ObjectWrappingOMElement) which extends from OMElement. It will have a
constructor to get an instance of OMObjectWrapper.

public interface OMObjectWrapper(){

 public XMLStreamReader getPullParser();

 public void writeYourSelf(XMLStreamWriter);

}

public class OMObjectWrappingElement extends OMElement{

  public OMObjectWrappingElement(OMObjectWrapper wrapper){

  }

  public void serializeWithConsume(XMLStreamWriter writer){
 wrapper.writeYourSelf(writer)
  }

}

And perhaps implement the OMObjectWrapper interface to ADBBean so that
ADBBean can be directly input to the constructor of the
OMObjectWrappingElement.



signature.asc
Description: OpenPGP digital signature

Re: [Proposal][Axis2][Axiom] Adding writable capability to OM elements

[Eran Chinthaka]

Ajith Ranabahu wrote:
> Hi,

> I was thinking a slightly different approach. We have an
> 'ADBOMElement' abstract class that has the write method unimplemented
> (and the rest of the methods are implemented in a generic way which I
> suppose is reasonable)
> During the codegen ADBBeans will have a method "getOMElement" which
> returns the ADBOMElement  with the write method implemented!
> 
> public OMElement getOMElement(){
> return new ADBOMElement(this){
>public void write(XMLStreamWriter writer){
> 
> // generated code that writes the output directly
> 
> 
>   }
>  }

Ok, if its a question of where we keep the new OMElement, then either
way is fine with me.

Your initial post some how made me think that you are trying to put a
ADB dependency on Axiom :).

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Initial JAX-WS Implementation

[Eran Chinthaka]

R J Scheuerle Jr wrote:

> 
> Eran said:
> (One additional question. If this yet another module and if it requires
> jdk5, then we need to do a small trick for people using jdk14 to not
> have problems. I think Dims had already done to one of the modules.)
> 
> Scheu reply:
> (Yes, the patch includes changes to the etc/project.properties file to
> ensure that the jaxws module is compiled with jdk5.   Is this the trick
> that you are referring to:
> 
> maven.multiproject.includes.requiresJDK15=\
> modules/jaxbri/project.xml,\
> modules/jaxws/project.xml
> )

Yes. Thanks for the clarification.



-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Build for SVN snapshot at the revision 414289 fails

[Eran Chinthaka]

[EMAIL PROTECTED] wrote:
> 
> maven-itest-plugin-1.0.jar

You can get it from here :
http://people.apache.org/~chinthaka/maven/maven-itest-plugin/plugins/maven-itest-plugin-1.0.jar

I can remember Dims also put this in some location. But I can not find
remember where he put it.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Initial JAX-WS Implementation

[Eran Chinthaka]

Hi Nicholas,

How about a wiki for the document (just an idea). I know its a pain to
write a large document in wiki, but that will enable people to comment
very easily.

-- Chinthaka

Nicholas L Gallardo wrote:
> Chinthaka,
> 
> Rich and I had discussed yesterday putting something together that 
> explains some of what we're trying to do.  Unfortunately, some of those 
> ideas aren't reflected in the code yet so a document is the best place to 
> start.  We'll put something together and will post it to the list in the 
> early part of next week.
> 
> Thanks to all for the reception.  We're looking forward to working with 
> the team on this.
> 
> Regards,
> 
> Nicholas Gallardo
> WebSphere  -  WebServices Development
> [EMAIL PROTECTED]
> Phone: 512-838-1182
> Building: 901 / 5G-016
> 
> 



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Initial JAX-WS Implementation

[Eran Chinthaka]

Hi Scheuerle and Nicholas,

Its not required you to be a committer to edit wikies. Anyway, I created
a blank page here
(http://wiki.apache.org/ws/FrontPage/Axis2/JAX-WS-Proposal) for you to
keep the proposal.

-- Chinthaka

R J Scheuerle Jr wrote:
> 
> 
> 
> 
> +1 for the wiki page.
> 
> FYI, we use wiki pages for our internal development.  It will be very easy
> for us to transition our work to a Axis 2 / JAX-WS wiki page.
> 
> I already have committer access (via my work on Axis).  Please let me know
> how I can help move this along.
> 
> Rich Scheuerle
> Senior Developer
> IBM WebSphere Web Services Engine & Tooling
> 512-838-5115  (IBM TL 678-5115)
> 
> 
>
>  Nicholas L
>  Gallardo/Austin/I 
>  [EMAIL PROTECTED]
>To 
>axis-dev@ws.apache.org  
>  06/17/2006 10:55   cc 
>  AMaxis-dev@ws.apache.org  
>Subject 
>Re: [Axis2] Initial JAX-WS  
>  Please respond to Implementation  
>  [EMAIL PROTECTED] 
>e.org   
>
>
>
>
> 
> 
> 
> 
> 
> Chinthaka,
> 
> That's not a bad idea since it should really be a living document.  Do we
> just create this off of the existing Axis2 wiki?
> 
> Thanks,
> 
> Nicholas Gallardo
> WebSphere  -  WebServices Development
> [EMAIL PROTECTED]
> Phone: 512-838-1182
> Building: 901 / 5G-016
> 
>
>  Eran Chinthaka
>  <[EMAIL PROTECTED]> 
> To 
> axis-dev@ws.apache.org 
>  06/17/2006 10:28 AMcc 
>
>Subject 
>Please respond toRe: [Axis2] Initial
>  axis-dev@ws.apache.org JAX-WS Implementation  
>
>
>
>
>
>
>
> 
> 
> 
> 
> 
> Hi Nicholas,
> 
> How about a wiki for the document (just an idea). I know its a pain to
> write a large document in wiki, but that will enable people to comment
> very easily.
> 
> -- Chinthaka
> 
> Nicholas L Gallardo wrote:
>> Chinthaka,
>>
>> Rich and I had discussed yesterday putting something together that
>> explains some of what we're trying to do.  Unfortunately, some of those
>> ideas aren't reflected in the code yet so a document is the best place to
> 
>> start.  We'll put something together and will post it to the list in the
>> early part of next week.
>>
>> Thanks to all for the reception.  We're looking forward to working with
>> the team on this.
>>
>> Regards,
>>
>> Nicholas Gallardo
>> WebSphere  -  WebServices Development
>> [EMAIL PROTECTED]
>> Phone: 512-838-1182
>> Building: 901 / 5G-016
>>
>>
> 
> (See attached file: signature.asc)
> -
> 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]




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Build for SVN snapshot at the revision 414289 fails

[Eran Chinthaka]

Hi Mike,

[EMAIL PROTECTED] wrote:
> 
> 1.  Attempts to download various Axis2 and Axiom SNAPSHOT jars occurred 
> repeatedly for each goal.  Sometimes it appeared that these SNAPSHOTS 
> downloaded but most of the time it appeared that they didn't.
> B.  It was not always the first attempt to download these SNAPSHOT jars 
> that was successful.

This is a known problem we have with maven 1.x version. If something is
SNAPSHOT then maven tries to check it whenever it sees a SNAPSHOT entry
in any of the modules.

What we normally do is, we run "maven clean jar -Dmaven.test.skip=true"
once to get all the dependencies at once, without running the tests.
Then we always run "maven clean jar -o" which will not bother to
download SNAPSHOTS.
We do not run without -o option, until we hit an unsatisfied dependency
problem.

> III.  Regardless of whether or not a successful download occurred, the 
> message "Response content length is not known" for each attempt.

Sorry I do not know anything about this.

- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Accept JAX-WS Implementation

[Eran Chinthaka]

Venkat Reddy wrote:
> +1.
> 
> Greetings every one :-) Will the JAX-WS code be part of Axis2 core, or
> an optional package? If it is going to be core, 

It should not be in the core and should be an optional package. I think
we agreed on this in the first f2f itself.


> then it's a good news

So its not a good news ;)



signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Accept JAX-WS Implementation

[Eran Chinthaka]

+1 from me too.

-- Chinthaka

Rajith Attapattu wrote:
> +1 from me
> 
> -Rajith
> 
> On 6/20/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
>>
>> +1 from me. Paul
>>
>>
>>
>> On 6/20/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
>> > Hi,
>> >
>> > +1 from me
>> >
>> >
>> >
>> > On 6/20/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
>> > > Hi Team,
>> > >
>> > > Let's hold an explicit vote for accepting the contribution (As
>> > > required by ip-clearance process in incubator).
>> > >
>> > > Please vote to accept the initial code from from IBM folks
>> attached to
>> > > the following JIRA issue:
>> > > http://issues.apache.org/jira/browse/AXIS2-826
>> > >
>> > > Here's my +1
>> > >
>> > > thanks,
>> > > dims
>> > >
>> > > PS: All PMC Members, please make sure u cast your vote.
>> > >
>> > > --
>> > > Davanum Srinivas : http://wso2.com/blogs/
>> > >
>> > > -
>> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > > For additional commands, e-mail: [EMAIL PROTECTED]
>> > >
>> > >
>> >
>> >
>> > --
>> > Ajith Ranabahu
>> >
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>>
>>
>> -- 
>> Paul Fremantle
>> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>>
>> http://bloglines.com/blog/paulfremantle
>> [EMAIL PROTECTED]
>>
>> "Oxygenating the Web Service Platform", www.wso2.com
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] REMINDER : Axis IRC chat TOMORROW

[Eran Chinthaka]

+1 from me too.

-- EC

Glen Daniels wrote:
> Sanjiva Weerawarana wrote:
>> +1 for canning it .. I don't see us doing these regularly any more and
>> its better to schedule them as needed IMO.
> 
> OK.  Waiting on a few other votes before making a final decision on
> this, but this sounds reasonable into the future.
> 
> --Glen
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: Axis2/Woden Integration Scenario Explanation

[Eran Chinthaka]

Graham Turrell wrote:
> Hi Chinthaka,
> 
> I have been able to generate the skeleton/stub artifacts using WSDL2Code as
> you described,
> within an eclipse development environment.
> 
> So that I can recreate your simple service exactly as you have done,
> would it be possible to see your manually filled-in versions of the
> generated java artifacts, please?


Yeah, I can give that.

From which wsdl were you trying to generate. I only did the
HotelReservation and echo?

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: Migration Axis 1 to Axis 2

[Eran Chinthaka]

Hi Fabio,

Why don't you try to do it yourself and get that "Aha" feeling yourself.
I can send it over but the one of the key features of Axis2 is its
usability.

Get the Axis2 1.0 release, find the wsdlcode.bat inside bin folder. Run
it with the following options.

If u r in Windows : WSDL2Code.bat -uri Servizio.wsdl -ss -sg -g

If u r in a linux distro, just run WSDL2Code.sh with the above options.

Read the user guide as well.

-- Chinthaka

[EMAIL PROTECTED] wrote:
> I have a wsdl genereted by SOA Editor.
> I'm able to develop a service in Axis 1.2 from this WSDL, but i'm not able to 
> develop a service with Axis 2 v1.0.
> Someome can send me send me a service developed using my WSDL in Axis 2.
> In attachment the Servizio.wsdl (Servizio means Service in italian ;)) 
> Thanks Fabio
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]




signature.asc
Description: OpenPGP digital signature

Re: [AXIS2] [WS-COMMONS] [VOTE] Nomination for Committer

[Eran Chinthaka]

+1 welcome aboard !!

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: Axis2 build with Maven 1.0.2

[Eran Chinthaka]

Hi Nathan,

I also noticed that the ibiblio repos do not contain the itest plugin
anymore.

Try the following.

maven plugin:download -DgroupId=maven-itest-plugin
-DartifactId=maven-itest-plugin -Dversion=1.0
-Dmaven.repo.remote=http://people.apache.org/repository/maven

-- Chinthaka

Nathan Sowatskey wrote:
> Hi
> 
> I am having the itest jar problem with building Axis2, which I have just
> checked out from SVN.
> 
> I tried to get the itest jar as described in the FAQ, but:
> 
> [echo] 1.4
> build:start:
> 
> plugin:download-artifact:
> [echo] repo is 'http://www.openejb.org/maven'
> [echo] trying to download
> http://www.openejb.org/maven/maven-itest-plugin/pl
> ugins/maven-itest-plugin-1.0.jar
> [echo] repo is 'http://www.ibiblio.org/maven'
> [echo] trying to download
> http://www.ibiblio.org/maven/maven-itest-plugin/pl
> ugins/maven-itest-plugin-1.0.jar
> Response content length is not known
> 
> BUILD FAILED
> File.. C:\Documents and
> Settings\nsowatsk\.maven\cache\maven-plugin-plugin-1
> .5.2\plugin.jelly
> Element... ant:fail
> Line.. 251
> Column 52
> Unable to find plug-in
> Total time: 4 seconds
> Finished at: Tue Jul 11 14:30:08 CEST 2006
> 
> 
> So, am I missing something?
> 
> Many thanks
> 
> Nathan




signature.asc
Description: OpenPGP digital signature

Re: Axis2 build - stax-utils-20060501.jar

[Eran Chinthaka]

Nathan Sowatskey wrote:
> Hi
> 
> I have:
> 
> The build cannot continue because of the following unsatisfied dependency:
> 
> stax-utils-20060501.jar
> 
> Total time: 11 minutes 7 seconds
> Finished at: Tue Jul 11 16:42:33 CEST 2006
> 
> Any ideas anyone please?

Get it from here http://ws.zones.apache.org/~dims/maven/stax-utils/jars/

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: Axis2 build - stax-utils-20060501.jar

[Eran Chinthaka]

Graham Turrell wrote:
> Nathan,
> 
> I'm going though this process too :-0 To pre-empt your next roadblock, you
> may now find you have
> 
> bcprov-jdk13-132.jar
> 
> missing also.
> 
> If so this can be found at
> http://ws.zones.apache.org/~dims/maven/bouncycastle/jars/ and should be
> copied into .maven/repository/bouncycastle/jars

He he. Let me generalize this. If you find some jars are missing, first
look them in http://ws.zones.apache.org/~dims/maven.





signature.asc
Description: OpenPGP digital signature

[Vote][Axis2] Rajith Attapattu as a committer

[Eran Chinthaka]

Hi all,

Rajith was contributing to WS project for some time. His contributed in
terms of ideas and patches to session management, clustering, JSR 181
efforts, samples, etc.,

So I would like to propose him as a committer.

Here is my +1.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Vote] [Axis2] Nick Gallardo as a committer

[Eran Chinthaka]

+1.

-- Chinthaka

R J Scheuerle Jr wrote:
> I would like to nomimate Nick Gallardo as committer to Axis2.
> 
> Nick is the technical expert of the Axis2 JAX-WS contribution.
> I have worked with Nick on the IBM Web Services team for several years.
> He is familiar with the Axis and Axis2 code bases. He has been involved
> in the
> development of several web service technologies, including JAX-RPC, SAAJ
> and WebServices for J2EE.
> 
> Making Nick a committer will streamline our ability to complete the
> JAX-WS implementation.
> 
> Rich Scheuerle
> IBM WebSphere Web Services Engine & Tooling
> Apache Axis2 ([EMAIL PROTECTED])
> 512-838-5115 (IBM TL 678-5115)
> 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] ServiceClient should provide Namespace declaration

[Eran Chinthaka]

Hi Christian,

The ServiceClient is carefully designed abstraction of the client API
which provides easy and simple API. So don't expect each and every
convenience method from ServiceClient. If you wanna do all sorts of
flexible things, then please use OperationClient.

-- Chinthaka

Christian Kloner wrote:
> hi,
> 
> I know you can use the OperationClient to get access to the underlying
> SOAPEnvelope such that you can create it and have access to it on your own.
> But I find the ServiceClient more convenient because all the Envelope
> creation is done behind the curtain.  But now, I am missing a method
> like "declareNamespace(OMNamespace, Type)" where Type is an enum of
> HEADER, BODY or ENVELOPE. Because if you look at the following message
> fragment, you will see, that the header contains a WebServiceAddress
> where for each element the wsa namespace is repeated. I think the only
> possibility to avoid this is to add a method which does the declaration
> to the Header OMElement. Is this right? Or should there be reasons why
> such methods should not be there?
> 
> 
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> 
>  xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing";
> soapenv:mustUnderstand="0">urn:uuid:E866B6CA2E6142C24C11531204167313
> 
> http://schemas.xmlsoap.org/ws/2004/03/addressing";
> soapenv:mustUnderstand="0">http://127.0.1.1:8080/wsrf/services/gridminer/TestService
> 
> http://schemas.xmlsoap.org/ws/2004/03/addressing";
> soapenv:mustUnderstand="0">
> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
> 
> 
> http://schemas.xmlsoap.org/ws/2004/03/addressing";
> soapenv:mustUnderstand="0">http://testservice.gridminer.org/TestPortType/getAttribute
> 
> http://keys.ae.gridminer.org/keys";
> soapenv:mustUnderstand="0">23743079
> 
> 
> If it should not be there, is there a possiblity to make the method
> "fillSoapEnvelope(MessageContext, OMElement)" protected or to use
> default scope? Because then i will simple extend ServiceClient and
> override the method.
> thank you.
> 
> Christian
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Creation of OMElement objects

[Eran Chinthaka]

did you try this :

createOMText(OMElement parent, char[] charArary, int type)

-- Chinthaka

Jean-Michel PATER wrote:
> Hi,
> 
> I want to create an OMElement with a child which type is byte[] (in the
> WSDL description type is "xsd:base64Binary").
> 
> The createOMText() method of OMFactory can't receive such type so how
> can I do that ?
> 
> Thanks in advance.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: AXIS SUCKS (In Capitals) - Help us

[Eran Chinthaka]

First lessson before using Axis should have been to understand the idea
behind opensource. According to www.opensource.org,

"The basic idea behind open source is very simple: When programmers can
read, redistribute, and modify the source code for a piece of software,
the software evolves. People improve it, people adapt it, people fix
bugs..."

So if you feel uncomfortable with current Axis, please help us to
improve it. Thats how Axis evolved so far. It was not one company or
small set of people who developed it. Its the community that behind in
any Apache and open-source projects made any project successful and
thats the simple reason why we value the community a lot in Apache.

Mr. Deep Ghosh, continue to give feedback like this to Axis or any other
project. You might even want to help contribute to Axis from your vast
experiences. We are happy to accept any valuable contributions, as that
benefits our community as a whole.

-- Chinthaka

Deep Ghosh wrote:
> 
> All,
>  
>   I could generate a Microsoft web service in 5 minutes and with axis
> its more than 5 hours so far. Thus the Subject.
>  
>   Generating wsdl2java was pretty ok (Although in Windows I would have
> expected a Program Menu Item to do such thing...or at least a
> batch/shell file in
>   DOS/UNIX but you guys will never learn that.
>  
>   So...ran wsdl2java and got a bunch of classes. Now what?
>  
>   Agree jws deployment is smart...but I have compiled a bunch of java
> classes.. so have a list of class files.
>  
>   Used AdminClient to deploy the wsdd.
>  
>   Used the section *Custom Deployment - Introducing WSDD in
> http://ws.apache.org/axis/java/user-guide.html#PublishingWebServicesWithAxis
> *
> ** 
> *  This is written by a moron. Rules : Dont write a bunch of stuff
> without telling what needs to be done. I know you are proud of the stuff
> you have developed but all the user cares is about how to use it and quick.*
> ** 
> *  AdminClient saysDone processing. Yes, everyone
> knows that. Did someone teach this guy that if you write a program, you
> should let the user what happens?*
> ** 
> * * So now..i have these bunch of classes. I dont know to what URL this
> damn thing is deployed.
>  
>   Whereas in Microsoft, they would start the URL and create a ASP.NET
> form to run my web service.
>  
>   When will this apache people grow up? I am sure ten years letter I
> will see them doing the same mistakes.
>  
> Best Regards,
> Deep
> 
> 




signature.asc
Description: OpenPGP digital signature

[Axis2] Axis2 1.1

[Eran Chinthaka]

Hi,

I think its the best time to plan for Axis2 next release, Axis2 1.1. I
know there are bunch of people who rely on nightlies since we fixed some
bugs after 1.0 and we have done enough, since the last release, to go
for the next release.

I put up some identified tasks here [1] as the criteria for Axis2 1.1.
Please go through the list and add/change/delete(?) items to/from that.

My suggestion is to plan for a release after a month from now.



Thanks,
Chinthaka


[1] : http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.1



signature.asc
Description: OpenPGP digital signature

Re: How should MessageReceiver be invoked

[Eran Chinthaka]

Hasalaka Waravita wrote:
> Hi
> Im trying to use Axis2 to do an EJB invocation. My approach is to plug
> transport senders/receivers and introduce a Message Receiver for EJB
> invocation.
> In Axis2 MessageReceivers are triggered on engine.receive() at server
> side. My problem is, I cannot run Axis2 on server side (Its not a
> WebServer, but an Appserver I'm calling, I don't want to convert request
> into SOAP/HTTP due overhead ).
> I can obviously  call  engine.receive() from transport, hence calling
> AxisEngine within the same JVM and achieve what I want.
> But is there an elegant way of doing this ? Your suggestions are highly
> appreciated.

Did you read this :
http://www.developer.com/java/ent/article.php/10933_3606466_1

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Non-blocking dual client

[Eran Chinthaka]

Hi Marta,

If there is an NPE, I will fix it.

But I'm sorry I'm missing something here. You *must* have a relatesTo
value, when you do a dual channel, non-blocking invocation. So what do
you mean by saying "in my case relatesTO is null"?


-- Chinthaka


Marta García Rueda wrote:
> I´m very sorry, I don´t explain my problem well.
> You are right, I´m trying to do a dual channel non-blocking client and the
> CodeGen generates my CallbackHandler, I´m using ADB also.
> 
> The problem it´s that when I´m trying to obtain the result for:
> callbackReceiver.receive(messageContext) I have an exception.
> 
> java.lang.NullPointerException at
> org.apache.axis2.util.CallbackReceiver.receive(CallbackReceiver.java:32)
> 
> I have seen that the method receive in
> org.apache.axis2.util.CallbackReceiver makes 
> RelatesTo relatesTO = messageCtx.getOptions().getRelatesTo();
> String messageID = relatesTO.getValue();
> 
> And in my case relatesTO is null so messageID throws an exception and I
> can´t obtain the result. So, callback in never onComplete and the
> CallbackHandler is never call.
> 
> My client works fine but I don´t know how to obtain the webservice response.
> 
> 
> Thank you very much.
> 
> Marta García.
> 
> -Mensaje original-
> De: robert lazarski [mailto:[EMAIL PROTECTED] 
> Enviado el: miércoles, 19 de julio de 2006 20:32
> Para: axis-dev@ws.apache.org
> Asunto: Re: [Axis2] Non-blocking dual client
> 
> You're trying to do dual channel non-blocking, right?  Several things
> here don't make sense to me here. Perhaps with some more info maybe we
> can help:
> 
> 1) You say you are using codegen with a hashMap - but there is no wsdl
> type for java.util.HashMap .
> 
> 2) CodeGen generates its own *CallbackHandler.java , right? The code
> you are showing looks like its from the code gen stub. What you really
> need to do, IMHO, is implement your
> *CallbackHandler.java methods and invoke your Stub.start* (at least
> using xmlbeans, probably the samething for ADB) methods that receive
> the argument of *CallbackHandler .
> 
> HTH,
> Robert
> http://www.braziloutsource.com/
> 
> On 7/19/06, Marta García Rueda <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> Hi,
>>
>> I´m doing an asynchronous client for a web services with the Code
> Generator
>> Tool and my stub class it´s like that:
>>
>>
>>
>> _operationClient.getOptions().setUseSeparateListener(true);
>>
>>
> _operationClient.getOptions().setTransportInProtocol(org.apache.axis2.Consta
> nts.TRANSPORT_HTTP);
>> org.apache.axis2.util.CallbackReceiver _callbackReceiver =
>> null;
>>
>> if (_operations[0].getMessageReceiver() == null &&
>> _operationClient.getOptions().isUseSeparateListener()) {
>>
>> _callbackReceiver = new
>> org.apache.axis2.util.CallbackReceiver();
>>
>>
>> _operations[0].setMessageReceiver(_callbackReceiver);
>>
>> }
>>
>> _operationClient.execute(false);
>>
>>
>>
>> When I debug this I see that the object callbackReceiver has the result in
> a
>> hashMap callbackStore. But I don´t know how to retrieve the result. I have
>> to implement a Listener o something like that? Could you tell me where can
> I
>> find an example?
>>
>>
>>
>> Thank you very much.
>>
>> Marta García.
>>
>>
> 
> -
> 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]
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] ADB build failure

[Eran Chinthaka]

Hi,

I can not move forward with the build failure. Already reverted the last
commit.

Please some one who committed that fix it again, TEST THE BUILD and
commit it.

-- Chinthaka

Davanum Srinivas wrote:
> Dennis,
> 
> This checkin for AXIOM caused the problem:
> http://mail-archives.apache.org/mod_mbox/ws-commons-dev/200607.mbox/[EMAIL 
> PROTECTED]
> 
> 
> I already posted an email to Rich:
> http://marc.theaimsgroup.com/?l=axis-dev&m=115368198831268&w=2
> 
> -- dims
> 
> On 7/24/06, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
>> I've been trying to build current Axis2 code for the last couple of days
>> (across several updates, hoping the problem would be fixed) without
>> success. The error I'm getting is in the ADB tests:
>>
>> [junit] Tests run: 15, Failures: 2, Errors: 3, Time elapsed: 0.942
>> sec
>> [junit] [ERROR] TEST
>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderTest FAILED
>>
>> The error report says:
>>
>> Testsuite:
>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderTest
>> Tests run: 15, Failures: 2, Errors: 3, Time elapsed: 0.942 sec
>>
>> - Standard Error -
>> [Fatal Error] :1:271: The prefix "axis2" for element
>> "axis2:SecondOMElement" is not bound.
>> -  ---
>> Testcase:
>> testComplexObjectArrayScenarioWithNulls(org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderTest):
>>
>> FAILED
>> Error has occurred java.lang.NullPointerException
>> junit.framework.AssertionFailedError: Error has occurred
>> java.lang.NullPointerException
>> at
>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderTest.testComplexObjectArrayScenarioWithNulls(ADBXMLStreamReaderTest.java:185)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>
>>
>> Anyone have an idea why this is occurring? Thanks,
>>
>>   - Dennis
>>
>> -- 
>> Dennis M. Sosnoski
>> SOA, Web Services, and XML
>> Training and Consulting
>> http://www.sosnoski.com - http://www.sosnoski.co.nz
>> Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: [AXIS2] Saving the message context

[Eran Chinthaka]

I can remember Chamikara from WS-RM team did some thing like this. You
can either wait for him to see this or ask in Sandesha-dev list.

-- Chinthaka

Ann Robinson wrote:
> Hi,
> I am investigating how to save and restore the message context in AXIS2.
> This is functionality that would be used, for example, by
> WS-ReliableMessaging to recover from a server/engine restart. This would
> also involve having a plugpoint for handlers to be able to save and
> restore their message context-related data (for example, the security
> handler might need to save a certificate or to re-establish a
> credential/token).
> 
> I have noticed that many of the classes involved with the MessageContext
> reference java.io.Serializable although few actually implement it. Has
> there been any thoughts or work regarding this?
> Thanks,
> Ann
> 
> WebSphere Development, Web Services Engine
> 
> IBM
> 11501 Burnet Rd IZip 9035G021
> Austin, TX 78758
> (512)838-9438 TL 678-9438
> 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] svn commit: r424366 - in /webservices/axis2/trunk/java/modules/jaxws: ./ src/org/apache/axis2/jaxws/ src/org/apache/axis2/jaxws/client/factory/ src/org/apache/axis2/jaxws/client/proxy/ src

[Eran Chinthaka]

Hi Rich,

[EMAIL PROTECTED] wrote:
> Author: scheu
> Date: Fri Jul 21 08:58:31 2006
> New Revision: 424366
> 
> URL: http://svn.apache.org/viewvc?rev=424366&view=rev
> Log:
> AXIS2-914
> Cont. JAX-WS Proxy Work
> Contributor: Nikhil Thaker
> 

Is this work done by Nikhil? If yes, he better needs to send patches if
he is thinking of getting committership. Thats been the way one becomes
a committer. Even myself and all the others sent patches before we
became committers and from that only others know about the new one.

So if you all thinking of later making this person a committer, ask him
to create a JIRA and attach the patch.

-- Chinthaka





signature.asc
Description: OpenPGP digital signature

Re: REMINDER on Changes to AXIOM

[Eran Chinthaka]

One more thing.

Please make sure the build works both on jdk14 and jdk15. If you want
some module to only work on jdk15, make sure you exclude that module
when jdk14 jvm is in place (see jax-ws module in Axis2).

Shall we setup a wiki with these guidelines for committers?

-- Chinthaka

Ruchith Fernando wrote:
> Hi All,
> 
> We are experiencing build failures in Axis2 right now due to latest
> AXIOM changes :-(
> 
> We have an understanding among the developers that whenever we change
> axiom we *always* check the axis2 build before checking in the changes
> to axiom.
> 
> Please see here [1] for previous discussions on this issue.
> 
> Thanks,
> Ruchith
> 
> [1]
> http://mail-archives.apache.org/mod_mbox/ws-commons-dev/200604.mbox/[EMAIL 
> PROTECTED]
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: Customization of SOAP Envelop using Axis2 1.0

[Eran Chinthaka]

What exactly you want to do here? Do you want to send a SOAP request
with WS-Addressing enabled?
If yes, the easiest way is to use the ServiceClient api with addressing
enabled (refer the user guide for this)

-- Chinthaka

Shyam Shukla wrote:
> 
> 
> Hello All,
> 
>  
> 
> I am just started working with axis2 1.0 with wss4j 1.5 and my task is
> to create SOAP request which refers to WS-Addressing
> http://schemas.xmlsoap.org/ws/2004/03/addressing while I am getting
> following format in SOAP request:
> 
>  
> 
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:wsa="http://www.w3.org/2005/08/addressing";>
> 
>  
> 
> Can anyone guide me how can I modify this request?
> 
>  
> 
>  
> 
> Thanks in Advance,
> Shyam Shukla
> 
>  
> 
> DISCLAIMER == This e-mail may contain privileged and
> confidential information which is the property of Persistent Systems
> Pvt. Ltd. It is intended only for the use of the individual or entity to
> which it is addressed. If you are not the intended recipient, you are
> not authorized to read, retain, copy, print, distribute or use this
> message. If you have received this communication in error, please notify
> the sender and delete all copies of this message. Persistent Systems
> Pvt. Ltd. does not accept any liability for virus infected mails.




signature.asc
Description: OpenPGP digital signature

Re: Customization of SOAP Envelop using Axis2 1.0

[Eran Chinthaka]

No wait, you don't need to change the source code to do that.

just do the following.

options.setProperty(
org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION,
org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE);

Hope you know how to set the options.

(Your next question might be that what are the other params that can be
set thru the client api. Do not worry an article on that is coming soon.
There is a small delay in getting that published :).)

-- Chinthaka

Shyam Shukla wrote:
> Thanks Chinthaka for your reply.
> I've enabled WS-Addressing and have associated in my SOAP Request.
> My problem is I want to modify the SOAP Envelop part in the request, by
> default axis2 1.0 is referring to
> "xmlns:wsa="http://www.w3.org/2005/08/addressing"; namespace as I have
> mentioned in my email while I want WS-Addressing namespace should refer to
> "http://schemas.xmlsoap.org/ws/2004/03/addressing"; URL.
> I have gone through all the addressing APIs of axis2 to find out any way to
> do it but could not be succeeded.
> I guess now I will have to modify the source code which is responsible for
> generating this part of the SOAP request.
> Can you please let me know which file will I be required to modify or Is
> there any API to accomplish this task?
>  
> 
> Best Regards,
> Shyam Shukla
> 
> -Original Message-
> From: Eran Chinthaka [mailto:[EMAIL PROTECTED] 
> Sent: Monday, July 31, 2006 12:11 PM
> To: axis-dev@ws.apache.org
> Subject: Re: Customization of SOAP Envelop using Axis2 1.0
> 
> 
> What exactly you want to do here? Do you want to send a SOAP request
> with WS-Addressing enabled?
> If yes, the easiest way is to use the ServiceClient api with addressing
> enabled (refer the user guide for this)
> 
> -- Chinthaka
> 
> Shyam Shukla wrote:
>>
>> Hello All,
>>
>>  
>>
>> I am just started working with axis2 1.0 with wss4j 1.5 and my task is
>> to create SOAP request which refers to WS-Addressing
>> http://schemas.xmlsoap.org/ws/2004/03/addressing while I am getting
>> following format in SOAP request:
>>
>>  
>>
>> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>> xmlns:wsa="http://www.w3.org/2005/08/addressing";>
>>
>>  
>>
>> Can anyone guide me how can I modify this request?
>>
>>  
>>
>>  
>>
>> Thanks in Advance,
>> Shyam Shukla
>>
>>  
>>
>> DISCLAIMER == This e-mail may contain privileged and
>> confidential information which is the property of Persistent Systems
>> Pvt. Ltd. It is intended only for the use of the individual or entity to
>> which it is addressed. If you are not the intended recipient, you are
>> not authorized to read, retain, copy, print, distribute or use this
>> message. If you have received this communication in error, please notify
>> the sender and delete all copies of this message. Persistent Systems
>> Pvt. Ltd. does not accept any liability for virus infected mails.
> 
> 
> 
> 
> DISCLAIMER
> ==
> This e-mail may contain privileged and confidential information which is the 
> property of Persistent Systems Pvt. Ltd. It is intended only for the use of 
> the individual or entity to which it is addressed. If you are not the 
> intended recipient, you are not authorized to read, retain, copy, print, 
> distribute or use this message. If you have received this communication in 
> error, please notify the sender and delete all copies of this message. 
> Persistent Systems Pvt. Ltd. does not accept any liability for virus infected 
> mails.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: [AXIS2] soap header

[Eran Chinthaka]

David Illsley wrote:
> Fabien,
> If you want access to the SOAPHeader, you can get it through the
> MessageContext. You can get this by adding the following method to
> your skeleton (I think this works for all MessageReceivers):
> 

No it doesn't happen for all the message receivers. I think the code gen
templates should be modified to implement the Service interface by the
skeleton and the generated message receiver to invoke the
setOperationContext method.

What do others think about this?

(If agreed I'd like to implement this as an exercise to get in to code
gen module :) )

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: Customization of SOAP Envelop using Axis2 1.0

[Eran Chinthaka]

options.setProperty(org.apache.axis2.Constants.Configuration.TRANSPORT_URL,
"http://the-real-url-I-want-to-send-my-request.org";);



Shyam Shukla wrote:
> Hi All,
> 
> To solve wsa namespace issue as I've mentioned in this email, instead of
> modifying existing handlers I wrote separate handlers and they all are
> working fine to support WS-Addressing namespace
> "http://schemas.xmlsoap.org/ws/2004/03/addressing";.
> 
> Now I have again come up with a problem, actually in my current project to
> obtain SAML Assertion from a web service which resides at remote location, I
> will have to send SOAP request which contains WS-Addressing, WS-Trust,
> WS-Security and WS-Policy over http. I have implemented all these WS-*
> specification using axis2 architecture although I had some problems with
> WS-Addressing but that has been solved by all your inputs.
> 
> The problem part is this 
> urn:GSO-System-Services:external:1.65:GatewaySecurityTokenService sa:To> tag. As I understand,  tag must point to URL where SOAP
> request is posted and axis2 picks this value to send request over transport
> protocol e.g. http but in my case as you can see I will have to provide a
> URN over http in a different location other than  value.
> 
> I know there is axis2 API to set  tag value but then how will I send
> it over http at different URL?
> 
>
> 
> Best Regards,
> Shyam Shukla
> 
> -Original Message-
> From: Shyam Shukla [mailto:[EMAIL PROTECTED] 
> Sent: Monday, July 31, 2006 3:46 PM
> To: 'axis-dev@ws.apache.org'
> Subject: RE: Customization of SOAP Envelop using Axis2 1.0
> 
> Thanks David I've obtained this file and will go through it to make desire
> changes.
> 
> I will again bother you if I am stuck somewhere.
> 
> Thanks & Regards,
> Shyam Shukla
> 
> 
> -Original Message-
> From: David Illsley [mailto:[EMAIL PROTECTED] 
> Sent: Monday, July 31, 2006 2:55 PM
> To: axis-dev@ws.apache.org
> Subject: Re: Customization of SOAP Envelop using Axis2 1.0
> 
> The AddressingOutHandler shipped with Axis2 (in the addressing module)
> which adds the soap headers can be found at [1].
> 
> David
> 
> [1]
> http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/addressing
> /src/org/apache/axis2/handlers/addressing/AddressingOutHandler.java?view=mar
> kup
> 
> On 31/07/06, Shyam Shukla <[EMAIL PROTECTED]> wrote:
>> David you got my point I was just going to reply Eran about this point.
>> Actually, in my current project web services which I have to invoke
> support
>> mentioned WSA namespace in this email
>> i.e."http://schemas.xmlsoap.org/ws/2004/03/addressing"; only and I am
>> required to write a client program to invoke those services.
>> So I think I will have to play with axis2 handlers.
>> David, can you please provide me the name and/or location of these handler
>> file(s) to create only SOAP Request.
>>
>>
>> Best Regards,
>> Shyam Shukla
>>
>> -Original Message-
>> From: David Illsley [mailto:[EMAIL PROTECTED]
>> Sent: Monday, July 31, 2006 2:26 PM
>> To: axis-dev@ws.apache.org; [EMAIL PROTECTED]
>> Subject: Re: Customization of SOAP Envelop using Axis2 1.0
>>
>> Eran, unfortunately Shyam is looking for the 2004/03 namespace which
>> the current addressing handlers do not support and if you sets the
>> WS_ADDRESSING_VERSION property to
>> "http://schemas.xmlsoap.org/ws/2004/03/addressing";, the submission
>> version is used.
>>
>> Shyam, if you can move up to a newer version of WS-Addressing that is
>> your best option (2004/03 is not widely supported now and won't be
>> going forward. There is broad vendor support for 2004/08 and 2005/08).
>> If you cannot move to one of these specifications, modifying the axis2
>> handlers to support 2004/03 or writing your own handlers are your
>> other options.
>>
>> David
>>
>> --
>> David Illsley - IBM Web Services Development
>>
>> On 31/07/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
>>> No wait, you don't need to change the source code to do that.
>>>
>>> just do the following.
>>>
>>> options.setProperty(
>>> org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION,
>>>
> org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE);
>>> Hope you know how to set the options.
>>>
>>> (Your next question might be that what are the other params that can be
>>> set thru the client api. Do not worry an article on that is c

Re: FW: [axis2] questions...

[Eran Chinthaka]

Tony Dean wrote:
> Does anyone have any insights on the questions listed below.
> 
> For instance setting some HTTP headers works while others do not.
> 
> These work:
> options.setProperty(MessageContextConstants.HTTP_PROTOCOL_VERSION,
> HTTPConstants.HEADER_PROTOCOL_10);
> options.setProperty(HTTPConstants.PROXY, proxyProperties);
> options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,
> basicAuthentication)
> 
> serviceClient.setOptions(options);
> 
> While setting options like the following seem to have not affect:
> options.setProperty(HTTPConstants.HEADER_CONNECTION,
> HTTPConstants.HEADER_CONNECTION_CLOSE);
> 
> Is there an exaustive list of options that one can use to control his/her 
> client invocation?

Well, I can not wait till my article gets published on this. Thought of
helping you by hosting it in my little space in apache itself.
You might find this
(http://people.apache.org/~chinthaka/articles/axis2-parameters.html)
useful.
(Note : This is a temp place)

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

[Axis2] Auto-reply messages

[Eran Chinthaka]

Hi,

I know lot of people have started enjoying vacations. But the auto
replies some of you have set are very much annoying. Whenever I send a
reply to a mail either in axis-dev or in axis-user, I get some number of
out of office messages. Its ok to leave that message to your clients,
but all the people here doesn't need to know that :).
Please please please be kind enough to set auto-replies off for the
email addresses you have subscribed to these mailing lists. Anyway we
are getting very large number of email per day from axis-dev and
axis-user alone. These out of office and other auto replies make it
worse :(.

Thanks a lot !!

- Chinthaka




signature.asc
Description: OpenPGP digital signature

Re: Customization of SOAP Envelop using Axis2 1.0

[Eran Chinthaka]

Yes you can. Last week we re-factored that constant to the proper place.
If you have Axis2 1.0 then go ahead with that.

I thought you were using Axis2 nightly builds.

-- Chinthaka

Shyam Shukla wrote:
> Hi Eran,
> 
> I couldn't find "org.apache.axis2.Constants.Configuration.TRANSPORT_URL" in
> my installed version of axis2 1.0 but the same constant I have got in
> "org.apache.axis2.context.MessageContextConstants.TRANSPORT_URL" package.
> 
> Can I use this one to fulfill my need?
> 
> Best Regards,
> Shyam Shukla
> 
> -Original Message-
> From: Eran Chinthaka [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, August 02, 2006 11:33 PM
> To: axis-dev@ws.apache.org
> Subject: Re: Customization of SOAP Envelop using Axis2 1.0
> 
> options.setProperty(org.apache.axis2.Constants.Configuration.TRANSPORT_URL,
> "http://the-real-url-I-want-to-send-my-request.org";);
> 
> 
> 
> Shyam Shukla wrote:
>> Hi All,
>>
>> To solve wsa namespace issue as I've mentioned in this email, instead of
>> modifying existing handlers I wrote separate handlers and they all are
>> working fine to support WS-Addressing namespace
>> "http://schemas.xmlsoap.org/ws/2004/03/addressing";.
>>
>> Now I have again come up with a problem, actually in my current project to
>> obtain SAML Assertion from a web service which resides at remote location,
> I
>> will have to send SOAP request which contains WS-Addressing, WS-Trust,
>> WS-Security and WS-Policy over http. I have implemented all these WS-*
>> specification using axis2 architecture although I had some problems with
>> WS-Addressing but that has been solved by all your inputs.
>>
>> The problem part is this 
>>
> urn:GSO-System-Services:external:1.65:GatewaySecurityTokenService> sa:To> tag. As I understand,  tag must point to URL where SOAP
>> request is posted and axis2 picks this value to send request over
> transport
>> protocol e.g. http but in my case as you can see I will have to provide a
>> URN over http in a different location other than  value.
>>
>> I know there is axis2 API to set  tag value but then how will I
> send
>> it over http at different URL?
>>
>>
>>
>> Best Regards,
>> Shyam Shukla
>>
>> -Original Message-
>> From: Shyam Shukla [mailto:[EMAIL PROTECTED] 
>> Sent: Monday, July 31, 2006 3:46 PM
>> To: 'axis-dev@ws.apache.org'
>> Subject: RE: Customization of SOAP Envelop using Axis2 1.0
>>
>> Thanks David I've obtained this file and will go through it to make desire
>> changes.
>>
>> I will again bother you if I am stuck somewhere.
>>
>> Thanks & Regards,
>> Shyam Shukla
>>
>>
>> -Original Message-
>> From: David Illsley [mailto:[EMAIL PROTECTED] 
>> Sent: Monday, July 31, 2006 2:55 PM
>> To: axis-dev@ws.apache.org
>> Subject: Re: Customization of SOAP Envelop using Axis2 1.0
>>
>> The AddressingOutHandler shipped with Axis2 (in the addressing module)
>> which adds the soap headers can be found at [1].
>>
>> David
>>
>> [1]
>>
> http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/addressing
> /src/org/apache/axis2/handlers/addressing/AddressingOutHandler.java?view=mar
>> kup
>>
>> On 31/07/06, Shyam Shukla <[EMAIL PROTECTED]> wrote:
>>> David you got my point I was just going to reply Eran about this point.
>>> Actually, in my current project web services which I have to invoke
>> support
>>> mentioned WSA namespace in this email
>>> i.e."http://schemas.xmlsoap.org/ws/2004/03/addressing"; only and I am
>>> required to write a client program to invoke those services.
>>> So I think I will have to play with axis2 handlers.
>>> David, can you please provide me the name and/or location of these
> handler
>>> file(s) to create only SOAP Request.
>>>
>>>
>>> Best Regards,
>>> Shyam Shukla
>>>
>>> -Original Message-
>>> From: David Illsley [mailto:[EMAIL PROTECTED]
>>> Sent: Monday, July 31, 2006 2:26 PM
>>> To: axis-dev@ws.apache.org; [EMAIL PROTECTED]
>>> Subject: Re: Customization of SOAP Envelop using Axis2 1.0
>>>
>>> Eran, unfortunately Shyam is looking for the 2004/03 namespace which
>>> the current addressing handlers do not support and if you sets the
>>> WS_ADDRESSING_VERSION property to
>>> "http://schemas.xmlsoap.org/ws/2004/03/addressing";, the subm

Re: Customization of SOAP Envelop using Axis2 1.0

[Eran Chinthaka]

Shyam Shukla wrote:
> Thanks Eran it worked and now I have one more problem... :)
> In my SOAP request header under  tag, there is 
> tag as below:
> 
>  xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit
> y-utility-1.0.xsd" wsu:Id="Timestamp-2086370">
> 
>   2006-08-02T11:39:58.015Z
>   2006-08-02T11:44:58.015Z
>  
> 
> My task is to modify the format of  and  tags in a
> different format like -mm-ddThh:mm:ssZ and also want to change the
> timezone.

Do you wanna do this, after security handler puts these information? I
don't think its a good idea as if you change the stuff after security
handler, message integrity checks in the server side might fail. So the
best thing is to change the formats in the security handlers itself.

Ruchith (Mr. security), do you have inputs for this?

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: FW: [axis2] questions...

[Eran Chinthaka]

Hi Tony,

The article on client api parameters is finally published here
(http://www.wso2.net/articles/axis2/java/2006/08/01/client-api-parameters).

-- Chinthaka

Eran Chinthaka wrote:
> Tony Dean wrote:
>> Does anyone have any insights on the questions listed below.
>>
>> For instance setting some HTTP headers works while others do not.
>>
>> These work:
>> options.setProperty(MessageContextConstants.HTTP_PROTOCOL_VERSION,
>> HTTPConstants.HEADER_PROTOCOL_10);
>> options.setProperty(HTTPConstants.PROXY, proxyProperties);
>> options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,
>> basicAuthentication)
>>
>> serviceClient.setOptions(options);
>>
>> While setting options like the following seem to have not affect:
>> options.setProperty(HTTPConstants.HEADER_CONNECTION,
>> HTTPConstants.HEADER_CONNECTION_CLOSE);
>>
>> Is there an exaustive list of options that one can use to control his/her 
>> client invocation?
> 
> Well, I can not wait till my article gets published on this. Thought of
> helping you by hosting it in my little space in apache itself.
> You might find this
> (http://people.apache.org/~chinthaka/articles/axis2-parameters.html)
> useful.
> (Note : This is a temp place)
> 
> -- Chinthaka
> 




signature.asc
Description: OpenPGP digital signature

Re: WSDL2Java works for an invalid WSDL

[Eran Chinthaka]

Keith,

Can you please file a JIRA with this.

Thanks,
Chinthaka

keith chapman wrote:
> Hi,
> 
> I tried using the WSDL2Java tool of axis 2 using the following WSDL's.
> 
> Using the following valid WSDL it generates the java classes
> 
> 
> http://org.apache.axis2/xsd";
> xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:soap="
> http://schemas.xmlsoap.org/wsdl/soap/
> "
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:tns="
> http://org.apache.axis2/"; targetNamespace=" http://org.apache.axis2/";>
>   
> http://www.w3.org/2001/XMLSchema"; xmlns:ns1="
> http://org.apache.axis2/xsd"; targetNamespace="
> http://org.apache.axis2/xsd"; elementFormDefault="qualified"
> attributeFormDefault="unqualified">
>   
> 
>   
> 
>   
> 
>   
>   
> 
>   
> 
>   
> 
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
> http://schemas.xmlsoap.org/soap/http
> " style="document"/>
> 
>   
>   
> http://www.org.apache.axis2
> "/>
>   
>   
> http://www.org.apache.axis2
> "/>
>   
> 
>   
>   
> 
>   http://127.0.0.1:8080/axis2/services/EchoService
> "/>
> 
>   
> 
> 
> 
> 
> 
> Then I deleted the message element corresponding to helloRequestMessage.
> Still it generates the classes for the following WSDL (with the
> helloRequestMessage element deleted)
> 
> 
> 
> 
> 
> http://org.apache.axis2/xsd"; xmlns:xs="
> http://www.w3.org/2001/XMLSchema"; xmlns:soap="
> http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:wsdl="
> http://schemas.xmlsoap.org/wsdl/"; xmlns:tns="http://org.apache.axis2/";
> targetNamespace=" http://org.apache.axis2/";>
>   
> http://www.w3.org/2001/XMLSchema"; xmlns:ns1="
> http://org.apache.axis2/xsd "
> targetNamespace="http://org.apache.axis2/xsd";
> elementFormDefault="qualified" attributeFormDefault="unqualified">
>   
> 
>   
> 
>   
> 
>   
>   
> 
>   
> 
>   
> 
>   
> 
>   
>  
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
> http://schemas.xmlsoap.org/soap/http";
> style="document"/>
> 
>   
>   
> http://www.org.apache.axis2
> "/>
>   
>   
> http://www.org.apache.axis2
> "/>
>   
> 
>   
>   
> 
>location="http://127.0.0.1:8080/axis2/services/EchoService
> "/>
> 
>   
> 
> 
> 
> Shouldn't this report an error instead of generating the java classes?
> 
> Thx,
> Keith




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] REST: Response content type and the wrapping XML

[Eran Chinthaka]

Ruchith Fernando wrote:
> Hi Folks,
> 
> I'm developing a simple REST service. I'm trying to return some HTML
> content and render that response in a browser window.
> Right now it is not possible to do this since the content type
> returned is text/xml. Shall we allow the service/handler developers to
> switch the response content type in the REST case?

Will check on this and fix of there is a problem.

> 
> Also shall we add another switch to get rid of the wrapper xml in the
> REST response? right now we wrap the response from an operation with :
> 
>  xmlns:ns="http://tinyurl.samples.axis2.apache.org/xsd";>
> 
> 
> 
> 
> elements.

Write your own message receiver my friend. RPC message receiver is for
rpc style of interaction and its a must that you wrap your response with
a return element. So the best option is writing your own message
receiver or to use XMLInOutMessageReceiver.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [AXIS2] [VOTE] Jeff Barrett for Committer

[Eran Chinthaka]

+1. Welcome Jeff.

BTW, some of his contributions can be viewed here FYI
(http://tinyurl.com/jtbke).

-- Chinthaka

Brent Ulbricht wrote:
> 
> +1 for Jeff
> *
> Brent Ulbricht
> WebSphere FVT* *
> [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> *Nicholas L Gallardo/Austin/[EMAIL PROTECTED]
> 
> 08/10/2006 07:57 AM
> Please respond to
> axis-dev@ws.apache.org
> 
> 
>   
> To
>   axis-dev@ws.apache.org
> cc
>   
> Subject
>   Re: [AXIS2] [VOTE] Jeff Barrett for Committer
> 
> 
>   
> 
> 
> 
> 
> 
> 
> Absolutely +1
> 
> Nicholas Gallardo
> WebSphere  -  WebServices Development
> [EMAIL PROTECTED]
> Phone: 512-838-1182
> Building: 901 / 5G-016
> 
> *"Davanum Srinivas" <[EMAIL PROTECTED]>*
> 
> 08/10/2006 07:50 AM
> Please respond to
> axis-dev@ws.apache.org
> 
>   
> To
>   axis-dev@ws.apache.org
> cc
>   
> Subject
>   Re: [AXIS2] [VOTE] Jeff Barrett for Committer
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> +1 from me.
> 
> On 8/10/06, R J Scheuerle Jr <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> I would like to nominate Jeff Barrett as a Committer to the Axis2 project.
>>
>>  Jeff is an experienced web service developer.
>>  He has architected large portions of several web service engines. He
> was a
>> key contributor to the initial JAX-WS drop into Axis2.
>>  He is currently working on the interaction between the JAX-WS
>> ServiceDescription and the AxisService/Annotations.
>>  He is working with Bill Nagy, Ann Robinson, Ming Cheung, and Lori Van
>> Gulick on separate Axis 2 contributions that are outside of the JAX-WS
>> component.
>>
>>  Jeff has experience as a development team lead. He was the team lead when
>> Russell Butek and I contributed to Axis Version 1.0.
>>  He is extremely thorough, an effective communicator, and is always a
>> pleasure to work with.
>>
>>  Making Jeff a committer will help us streamline the JAX-WS contributions.
>> And he will bring additional deep experience to the team.
>>
>>  Thanks,
>>
>>  Rich Scheuerle
>>  IBM Web Services
>>  Apache Axis2 ([EMAIL PROTECTED])
>>  512-838-5115 (IBM TL 678-5115)
> 
> 
> -- 
> Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] An approach for clustering Axis2

[Eran Chinthaka]

One simple question?

Why did u forget the replication of message contexts and operation
contexts, whilst replicating ConfigurationContexts and the others. IIRC,
operation context map is maintained in the config context.

Another point. Think of IN-IN-OUT mep. You first route the first IN
message to node A of the cluster. Afterwhile, before the second IN
message, node A goes down. How can you cater for this w/o catering for
the replication of operation contexts.
Well you might argue back and say, IN-IN-OUT mep is not the 90% case. If
thats the case take an RM scenario. From my very little knowledge on RM,
what if node A goes down, having serviced createSequence operation.
Don't we need message context replication from that.

Apologies if I'm missing sth here.

-- Chinthaka

Chamikara Jayalath wrote:
> Hi All,
> 
> As you know, sometime back that there were some discussion on clustering
> Axis2. Quite a set of ideas came up, specially from Rajith.
> 
> Me and Chathura Ekanayake thought of bringing this discussion back to
> life by coming up with a proposal to enable context replication in
> Axis2. Upon this we could come up with mechanisms to support failure
> recovery and load balancing.
> 
> Sorry about the long email. We thought a bit detailed description would
> give you a clear idea of our proposal.
> 
> The main point was to come up with a interface called ClusterManager.
> This would define a set of methods that an Axis2 instance working as a
> node in a cluster could use to share its state with other nodes. An
> implementation of the ClusterManager will be in a particular clustering
> technology.
> 
> At initiating Axis2 will check a property in the axis2.xml to find out
> weather its working as a node in a cluster. If it is, Axis2 will
> instantiate the ClusterManager object and call its methods whenever it
> needs to share information with other nodes in the cluster.
> 
> This proposal doesn't worry about replicating OperationContexts and
> MessageContexts. The main reason for this was the cost the replication
> of them would produce (But I guess we can discuss more on that). So here
> we only worry about the replication of ConfigurationContext,
> ServiceGroupContexts and ServiceContexts.
> 
> Here is the ClusterManager interface that we came up with. I've
> explained the usage of each method after that.
> 
> 
> 
> 
> public interface ClusterManager {
> 
> void init (ConfigurationContext context);
> void addContext (String contextId,String parentContextId,
> AbstractContext context);
> void removeContext (String contextId);
> void addProperty (String contextId, String propertyName, Object
> propertyValue);
> void removeProperty (String contextId, String propertyName);
> Object touchProperty (String contextId, String propertyName);
> void updateState ();
> void farmDescription (AxisDescription axisDescription);
> void removeDescriptionFromFarm (String axisDescriptionName);
> 
> }
> 
> 
> 
> 
> We assume that each Node in the cluster get born with the same
> configuration. So initially they will have similar axis2.xml files and
> similar repositories.
> 
> To make the methods simple we assumed that every context should come
> with a id which could be used to uniquely identify it within a given
> node. For a ServiceGroupContext this can be the serviceGroupContextId.
> For a service context this can be the combination of the service name
> and the id of the ServiceGroupContext which it belongs to.
> 
> The first method 'init' does the initiation work of the current Node.
> One task of it will be to join the current node into the cluster.
> 
> When a new context get added in a certain node, the 'addContext' method
> of it will be called. This method should inform the other Nodes about
> this newly added context and ask them to add similar contexts within them.
> 
> Similarly 'removeContext' method will be called when a context get
> removed from a certain Node. Other Nodes should be informed about this
> and they should be asked to remove the context with the same Id.
> 
> We belive that the state of a context is represented by its property
> bag. So replication of the state would simply mean the replication of
> the property bag of each context. The next three methods could be used
> for this.
> 
> As their names imply 'addProperty' and 'removeProperty' methods should
> inform the other nodes to add and remove properties respectively.
> 
> When the state of a property bag is suspected to have been changed that
> property should be touched. For this the touchProperty method have to be
> used. For example when the user ask for a certain property from the
> property bag (using the getProperty method of the abstract context)
> there is a probability of the state of that property be

[Axis2] Axis2 build break and commits

[Eran Chinthaka]

Hi all,

I can see Axis2 build is failing and I know Dims is working on that. But
I can see some commits going on, even when the build is failing.

I think we have a good practice not to commit anything when the build is
failing. So please make sure you don't commit when build is failing or
in other words test the whole build by "maven clean jar -o" before
committing your code to any module.

One problem if you do not adhere to this is that the job of the person
whose gonna fix the build will become more and more harder if he gets
more commits.

A humble request.

Thanks,
Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Axis2 build break and commits

[Eran Chinthaka]

Dims,

You got only half of the point I raised :).

Some one committing and the build failing is better than some one
committing whilst the existing code is breaking.

I know lot of people commit, with local paths hard coded, testing ports
changed, and build was successful in his/her machine.

What I mentioned was, before doing any changes, please check the current
code whether it is building successfully or not. If success, then do
your changes, check the build again and commit. People committing
changes, even when the existing code breaks is my concern :).


-- EC

Davanum Srinivas wrote:
> This time, i am the culprit. I broke the build. The check-in in
> question is this:
> http://svn.apache.org/viewcvs.cgi?view=rev&rev=430406
> 
> I'll try to fix it in another hour or so OR worst case revert it.
> 
> thanks,
> dims
> 
> On 8/11/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> I can see Axis2 build is failing and I know Dims is working on that. But
>> I can see some commits going on, even when the build is failing.
>>
>> I think we have a good practice not to commit anything when the build is
>> failing. So please make sure you don't commit when build is failing or
>> in other words test the whole build by "maven clean jar -o" before
>> committing your code to any module.
>>
>> One problem if you do not adhere to this is that the job of the person
>> whose gonna fix the build will become more and more harder if he gets
>> more commits.
>>
>> A humble request.
>>
>> Thanks,
>> Chinthaka
>>
>>
>>
>>
> 
> 




signature.asc
Description: OpenPGP digital signature

[Axis2] Identifying REST vs SOAP messages

[Eran Chinthaka]

Hi,

I have a slight problem in fully implementing AXIS2-1023. Question in
simple terms is : when a message comes to Axis servlet (assume the same
servlet handles both the REST and SOAP messages), how can we know
whether its a SOAP or a REST message *without* looking at the SOAP
message? (yes, I'm talking only about HTTP case).

If the message is SOAP 1.1, then SOAPAction header is always there. If
its SOAP 1.2 then SOAPAction *may* be in content type string, and spec
hasn't mandated that.

If its REST, then the content type can be anything.

Is there a better way of identifying this?

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

[Axis2][Vote] Brian DePradine as a committer

[Eran Chinthaka]

Hi all,

Brian DePradine was active in Axis2 development for some time and he had
made considerable amount of contributions to WS projects, especially Axis2.
His contributed patches can be seen here [1].

I'd like to propose him as a committer.

Here is my +1.

-- Chinthaka

[1] : http://tinyurl.com/zblr6



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Re: [jira] Commented: (AXIS2-993) org.apache.axis2.addressing.EndpointReference should explicitly save the WS-Addressing namespace

[Eran Chinthaka]

Brian De Pradine wrote:

>>
>> Brian,
>>
>> This is one of the problems I've been looking at for some time. IMO,
>> EndpointReference class better be independent of WS-A. We got the
>> attributed of the EPR class by looking at 2005/08 spec, but after
>> that it had nothing to do with that.
> 
> Why does the EndpointReference class need to be independent of the
> WS-Addressing
> namespace? This is the aspect of this discussion that I haven't
> understood yet.
> Considering that in axis2 ALL EPRs are represented using instances of
> this class
> it seems to me that the addressing namespace is an important attribute
> to capture.

My only concern is EPR is used everywhere and it doesn't need to contain
WS-Addressing namespace in it. Its required only when you
serialize/de-serialize it.

For example, when you formulate a request to be sent and when you are
doing request-response invocation over the same HTTP channle, you don't
need to know anything about WS-Addressing. And no WS-Addressing modules
are required.

Thats why I like to keep EPR class independent from any namespace. For
me its just a bean which encapsulates information about an endpoint.
Serializing it using WS-A rules or any other rules is not its problem.

Yes, I agree its a problem if where to keep the code, both of us agree
on other stuff :)

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Identifying REST vs SOAP messages

[Eran Chinthaka]

Hi Glen,

Glen Daniels wrote:

> I think the algorithm is as follows:
> 
> 1) check media-type.  If it's either of the well-defined ones for SOAP
> 1.2 (application/soap+xml, application/xop+xml), it's SOAP 1.2.

This is the problem. As I mentioned in my earlier mail also, content
type for SOAP 1.2 is optional. One can send a SOAP 1.2 message without
putting the content type as application/soap+xml. What can we do about that?

We can make it a must for users to send the content type, even if it is
SOAP 1.2.

- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Identifying REST vs SOAP messages

[Eran Chinthaka]

I think still everyone is trying to address the easier question,
forgetting the harder one.

Yes SOAP 1.1 can be detected from the SOAPAction. But since we must
support SOAP 1.2 specification, we can not mandate clients to have
application/soap+xml or application/xop+xml in their SOAP 1.2 requests.
So your Case2 algorithm violates the SOAP 1.2 spec.

I even check WS-I BP 1.1, but seems it only talks about SOAP 1.1.

My question is what we can do for that? Shall we mandate the users to
have one of the above content types?

-- Chinthaka

Ajith Ranabahu wrote:
> Hi,
> As per [1] if I understand it right, a SOAP 1.2 HTTP implementation
> must be able to process the media type "application/soap+xml" but
> clients may send messages with other compatible media types as well
> (something like text/xml).
> This whole behavior changes with the REST flag being on and off so
> this is what I think os the best way
> 
> Case 1: REST is off
> 1. If SOAPAction -> SOAP 1.1
> 2. Any other text compatible media type -> SOAP 1.2
> 
> Case 2: REST is on
> 1. If SOAPAction -> SOAP 1.1
> 2. applicatin/soap+xml -> SOAP 1.2
> 3. any other text compatible media type -> REST
> 
> [1] http://www.w3.org/TR/2003/REC-soap12-part2-20030624/#httpmediatype
> 
> Ajith
> 
> On 8/19/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
>> Hi Glen,
>>
>> Glen Daniels wrote:
>>
>> > I think the algorithm is as follows:
>> >
>> > 1) check media-type.  If it's either of the well-defined ones for SOAP
>> > 1.2 (application/soap+xml, application/xop+xml), it's SOAP 1.2.
>>
>> This is the problem. As I mentioned in my earlier mail also, content
>> type for SOAP 1.2 is optional. One can send a SOAP 1.2 message without
>> putting the content type as application/soap+xml. What can we do about
>> that?
>>
>> We can make it a must for users to send the content type, even if it is
>> SOAP 1.2.
>>
>> - Chinthaka
>>
>>
>>
>>
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Identifying REST vs SOAP messages

[Eran Chinthaka]

Davanum Srinivas wrote:
> Eran,
> 
> Let's code it up to look for the 2 media types and document that in
> bold blinking letters :)

Hehe, Already done something like that. Will send a note with the commit
and to the JIRA.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Identifying REST vs SOAP messages

[Eran Chinthaka]

Here is what I implemented.

This applies to
 - when REST is enabled in AxisServlet
 - and when a message comes through POST.

First check whether it has the content types text/xml or
application/x-www-form-urlencoded. If yes its a REST request else its a
SOAP.
Well, you might ask what about other content types for REST? What abt
MTOM with REST. They are not yet implemented, once its done, especially
MTOM, lets improve the logic.

See my comment in AXIS2-1023.

-- Chinthaka

Eran Chinthaka wrote:
> Davanum Srinivas wrote:
>> Eran,
>>
>> Let's code it up to look for the 2 media types and document that in
>> bold blinking letters :)
> 
> Hehe, Already done something like that. Will send a note with the commit
> and to the JIRA.
> 
> -- Chinthaka
> 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Build fail ?

[Eran Chinthaka]

Mr. Security is fixing it now :)

Ajith Ranabahu wrote:
> sorry for the missing prefix and the misspelled subject!
> 
> -- Forwarded message --
> From: Ajith Ranabahu <[EMAIL PROTECTED]>
> Date: Aug 23, 2006 12:53 AM
> Subject: Buid fail ?
> To: Axis developer list 
> 
> 
> The test org.apache.rahas.RahasSAMLTokenCertForHoKV1205Test  fails for
> me with a message saying "an Illegal key size or default parameters"
> 
> This is an online build so I suppose all jars are in their latest
> revisions. Any ideas ?
> 
> -- 
> Ajith Ranabahu
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Learning Axis & Hair Los

[Eran Chinthaka]

Let me add bit more to what Anne has said.

First I really appreciate your comments on this.

All the documentation we have in Axis2 and AXIOM were written by the
developers of the respective projects. We always didn't have enough time
to improve the docs, which I know is not a good excuse. We tried to
explain as much as possible from developer pov, but I admit that it is
not that successful. Couple of guy have now started writing some
articles to various places on the web.

I'd happy to get feedback like this and appreciate if someone can help
us to improve the docs. Even though we have written some good piece of
code, its you people that are using it.

So can you people help us to improve the docs and we will give any
support from technical content. Robert is another guy who had all sorts
of troubles in understanding how it works and he has a better knowledge.
Perhaps he might help too with docs.

If anyone of you have time to help the community writing docs, please go
ahead, write them, create a JIRA and attach them. If you have questions,
feel free to ask them either in axis-dev and/or axis-user lists.

Thanks,
Chinthaka

Anne Thomas Manes wrote:
> Here's a tutorial on AXIOM: http://ws.apache.org/axis2/1_0/OMTutorial.html
> 
> (The developers are busy fixing bugs -- unfortunately, the
> documentation will come later. But please continue to provide
> constructive criticism. Perhaps you could compile a list of things you
> found unintelligible and create a JIRA requesting they by improved.)
> 
> Anne
> 
> On 8/22/06, M. Goodell <[EMAIL PROTECTED]> wrote:
>>
>>
>> First of all let me preface what I am about to say by stating clearly:
>>
>> I really appreciate the work that goes into open source projects like
>> Axis.
>> I know this is a "labor of love" in many respects and people choose to do
>> this with no direct monetary compensation whatsoever. To all of you
>> dedicated passionate developers on Axis2 & other open source projects I'm
>> sure I speak for thousands when I say Thank You!!
>>
>> With that said, over the past years as I have worked with various open
>> source projects and have found one common problem with most of them:
>>
>> The problem: Documentation and reference material.
>>
>> I have found Axis2 be the same way. Please allow a couple of examples:
>>
>> 1. In the users guide that demonstrates how to build a web service
>> using the
>> Axis2s primary APIs there is the sample code
>>
>> public void ping(OMElement element){} //IN-ONLY operation, just
>> accepts the
>> OMElement and do some processing.
>> public OMElement echo(OMElement element){}//IN-OUT operation, accepts an
>> OMElement and // sends back the same again
>>
>> The questions that popped up in my mind after reading this were:
>>
>> 1. What's an OMElement?
>> 2. What's an IN-ONLY operation?
>> 3. What's an IN-OUT operation?
>> etc . . .
>>
>> Then below the code example is this statement:
>>
>> "As you can see, the two operations are very simple and need no
>> explanations
>> on what they do"
>>
>> Yes, the operations in and of themselves are not complex at all but
>> there is
>> some very foundational information missing here. i.e. items 1,2 & 3
>>
>> It seems, to me anyway, much of the documentation assumes familiarity
>> with
>> concepts and technologies used. In this case AXIOM.
>>
>> 2. The services.xml file example as demonstrated in the users guide is
>> another item I would like to point out. I have looked for the
>> reference to
>> what each element is such as a DTD description etc. But no such luck.
>> Very
>> frustrating! Where does one go to get this information??
>>
>> Much of the documentation is assembled in this fashion. Moreover, I have
>> seen posts in the newsgroups about the Axis documentation being
>> difficult to
>> follow and find information.
>>
>> In summary, what I, and perhaps others, are asking for is a more clearly
>> defined, logical, orderly & complete path to learning, in this case
>> AXIS2. I
>> am not afraid to read anything, I just need to know what and when. I
>> believe
>> good technical documentation should supply that opportunity and road map.
>>
>> Am I asking something from the open source community that simply does
>> not,
>> and never will exist?
>>
>> Will I need to await a text book on subject *hoping* it' not just a
>> rehash
>> of material already on the web?
>>
>> Do we need to spend the money on a commercial application and forget open
>> source? The documentation is in many cases better, hence a faster
>> ascent up
>> the learning curve.
>>
>> Finally, does anyone else share my frustration or do I simply need to
>> end my
>> 20+ career as a programmer and go work in a pet grooming shop for the
>> rest
>> of my days?
>>
>> (Don't answer that!)
>>
>> It just seems a shame and waste to see such useful technology not used
>> perhaps due in large part to proper explanation and systematic
>> exposure on
>> the part of those responsible for bringing it to the marketplace.
>>
>> I we

Re: [Axis2][Axiom]Axiom-***.jar not updated?

[Eran Chinthaka]

Ajith Ranabahu wrote:
> Hi Dims,
> Yes - essentially as good practice we will stick to the use of
> seperate jars. I'm not very sure how others will feel about dumping
> the combined jar though !

I'm ok with for using/generating separate jars. But I can not understand
how this can answer your initial concern.

I did a change in axiom, I think that being not reflected in the repo
was the problem, but that change affected both the api and impl(s). How
can separating those jars solve the problem?

> 
> Anyone has strong views about the combined jar ;)

Hehe.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2][Axiom]Axiom-***.jar not updated?

[Eran Chinthaka]

+1.

Ajith Ranabahu wrote:
> Hi,
> What happened was this
> 
> 1. Secpolicy module had axiom-combined jar as a dependency where as
> all other modules (I'm talking about maven modules in the Axis2 build)
> had the seperate Axiom jars.
> 
> 2. When you do a create-lib it copies dependancies of all the modules
> to the lib folder. Since there were the three seperate axiom jars and
> the combined axiom jar as dependancies 4 axiom jars were copied into
> the lib folder.
> 
> 3.Once you get to use that lib it wasn't predictable where the axiom
> classes get picked up. ant build picked it from the combined jar and
> IDEA picked it up from the seperate jars
> 
> So here is the outcome
> 
> 1. All Axis guys should make sure (Specially when new modules are
> introduced) that the dependancies are made to the three seperate jars
> and not the combined one (for axiom)
> 
> 2. If no one is using the combined axiom jar anymore we should not
> generate it as part of the build and remove any existing
> axiom-SNAPSHOT.jar from the repositories
> 
> I hope this makes it clear about all this business in the axiom build :)
> 
> Ajith
> 
> 
> On 8/26/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
>> Ajith Ranabahu wrote:
>> > Hi Dims,
>> > Yes - essentially as good practice we will stick to the use of
>> > seperate jars. I'm not very sure how others will feel about dumping
>> > the combined jar though !
>>
>> I'm ok with for using/generating separate jars. But I can not understand
>> how this can answer your initial concern.
>>
>> I did a change in axiom, I think that being not reflected in the repo
>> was the problem, but that change affected both the api and impl(s). How
>> can separating those jars solve the problem?
>>
>> >
>> > Anyone has strong views about the combined jar ;)
>>
>> Hehe.
>>
>> -- Chinthaka
>>
>>
>>
>>
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: Axis2/Woden Integration Scenario Explanation (Request for User Documentation)

[Eran Chinthaka]

[EMAIL PROTECTED] wrote:
> 
> Hi,
> 
> Is the integration available with Axis2 Version 1.0? (Axis2
> documentation doesn't say anything about it :-( )

No its not available with Axis2 1.0. But its in the nightly builds.

> 
> Am looking to generate Java code (using WSDL2Code) with WSDL 2.0 (HTTP
> Binding). Can you give me pointers to user documentation to use the feature?

use "-wv 2" option with wsdl2code tool. I'm not sure we completed code
gen for HTTP binding.

As Anne mentioned earlier also, we do not recommend to use WSDL 2.0 in
production systems still.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: WSS4J 2.0(?)

[Eran Chinthaka]

Another big +1 from me too.

I was really worried about the increasing number of modules within Axis2
project, but didn't take this up as people were busy with other
important issues. I'd like to add two more things to Ruchith's proposal.

1. Move Savan also to a sub-project out of Axis2

2. Write some integration tests in Axis2 to compensate the valuable
tests Ruchith had written to test the integrity of Axis2 client and
server. Whenever you do some random changes in Axis2, security tests
were failing as they were the only tests which tested the real
integration. Since these tests also will be moved with Rahas and
Rampart, we need to have some tests to compensate them

3. Need to have a gump like thingy setup to run all the tests in Axis2
and related projects and to bug whoever breaks the total build.

Any volunteers?

-- Chinthaka

Sanjiva Weerawarana wrote:
> On Thu, 2006-08-31 at 20:28 +0530, Ruchith Fernando wrote:
>> Basically how about pushing these up to be two new sub projects or the
>> Apache Web services project :
>>
>> Ramaprt - WS-Security and WS-SecureConversation implementation
>> Rahas - WS-Trust implementation
>>
>> This is similar to the way we have Sandesha (WS-RM impl), and they
>> will have their own release cycles etc. ?
> 
> Big +1 from me. I don't see any need to clutter up WSS4J with all this
> stuff - let's keep WSS4J at the level it is and add separate projects to
> cover the other functionality (which are Axis2 and Axiom coupled
> anyway).
> 
> Sanjiva.
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: WSS4J 2.0(?)

[Eran Chinthaka]

Ruchith Fernando wrote:
> Hi,
> 
> In the case of Axiom I think we can now consider it to be a very much
> general XML object model, and I believe it has many other users other
> than Axis2 and Axis2 related projects ... and it sure can be moved out
> of ws-commons (may be as a Apache TLP ??) and it probably will get
> more visibility and more ppl will use it.

Definite +1 for this. I know Tuscany and Abdera guys are using Axiom a
lot. Especially Abdera has nothing to do with Web services.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: WSS4J 2.0(?)

[Eran Chinthaka]

Ajith Ranabahu wrote:
> Hi,
> I'm also +1 on this move - it makes things modular and easy to handle.
> BTW I don't think you need to move the integration tests - they are
> *Axis2* integration tests and they should not go to any other project!

No, you miss something here Ajith. They are not mere integration tests.
They test how Rahas or Rampart or whatever works hand-in-hand. But that
includes Axis2 integration tests as well.
Thats the reason behind me mentioning that we need some test cases to
test the integration to compensate the removal of Security integration
tests. Read point #2 my earlier mail.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Refactoring WS Projects [ Was : Re: WSS4J 2.0(?)]

[Eran Chinthaka]

Jaliya Ekanayake wrote:
> Hi All,
> 
> Few thoughts from me.
> 
> We cannot expect people to use QoS projects like Kandula and Sandesha
> without axis1 or axis2 and also we can expect axiom and WSS4J to be used
> more independently. In addition they all come under WS* projects. So I
> would like to suggest this.
> 

Jaliya did u mean Axiom also should come under WS*? If yes, I do not
agree with you. I'd rather lean towards Ruchith's and Ajith's suggestion.
Axiom, XmlSchema can be projects useful even outside WS*.
If you mean the same thing, apologies in advance :). Just making sure we
all are in the same camp.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Refactoring WS Projects [ Was : Re: WSS4J 2.0(?)]

[Eran Chinthaka]

Unfortunately I do not agree with this.

Are you saying integration tests of Rampart and Axis2 should live in
Axis2? And you want to move Rampart out of Axis2?
For me these are two contradictory statements.

What if tomorrow, Sandesha, Kandula, Savan, etc., wants to have their
tests within Axis2? Do you agree?

The ideal solution I'd like to see is Axis2 project which has

1. the core of Axis2 which includes:

addressing
adb
adb-codegen
codegen
common
integration (without rampart, rahas test cases)
kernel
samples
webapp
wsdl
java2wsdl(we can move this out to commons)

2. The extension to Axis2 which are sub-projects of Axis2 which includes:
jaxbri
jaxws
jibx
saaj(having this in the core project is fine with me)
spring
tools
xmlbeans


3. Different sub projects under WS project for:
rahas
savan
security
sandesha
secpolicy

4. Promote Axiom and Xmlschema to separate TLPs.

-- Chinthaka




Ajith Ranabahu wrote:
> Hi,
> Nope I'm not missing anything :) I'm saying keep the integration tests
> as it is (I'm talking about the security tests in the integration
> module) and they can run having rampart as an external dependancy.
> That's it. You don't want to move them anywhere. If Axis2 code is not
> compatible with the latest rampart build (which now comes as an
> external dependancy), Axis2 build will fail!
> In my mind Axis2 integration tests belong in Axis2 and not anywhere
> else. We do have XMLBeans and Jibx tests that way.
> 
> Ajith
> 
> On 9/1/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
>> Ajith Ranabahu wrote:
>> > Hi,
>> > I'm also +1 on this move - it makes things modular and easy to handle.
>> > BTW I don't think you need to move the integration tests - they are
>> > *Axis2* integration tests and they should not go to any other project!
>>
>> No, you miss something here Ajith. They are not mere integration tests.
>> They test how Rahas or Rampart or whatever works hand-in-hand. But that
>> includes Axis2 integration tests as well.
>> Thats the reason behind me mentioning that we need some test cases to
>> test the integration to compensate the removal of Security integration
>> tests. Read point #2 my earlier mail.
>>
>> -- Chinthaka
>>
>>
>>
>>
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Axis2 next release (Axis2 1.1)

[Eran Chinthaka]

Davanum Srinivas wrote:
> +1 from me. Can we make it 1.5 instead of 1.1? There are just too many
> changes :)

+1 for the next release, whatever the number it is.

I'm sure lot of users in our users list will love to get a release.

I'm not sure about the timeline, but let's try !!

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: Axis2/Woden Integration Scenario Explanation (Timeline for WSDL2Code to support WSDL 2.0 HTTP Binding Extn?)

[Eran Chinthaka]

venkat wrote:
> 
> Resending the mail and looking forward for a reply at the earliest...
> 
> I tried the nightly builds and it seems to work fine for WSDL 2.0 with
> SOAP Binding. We are looking forward for the feature, WSDL2Code
> generating code given WSDL 2.0 with HTTP Binding. This will help us
> publish our WSDL 2.0 documents.
> 
> Are there any plans to implement this in the near future? 

Yes, we do.

> When is this expected to be done?

These days we are getting ready for Axis2 1.1. But we didn't consider
this to be implemented before the release. Most probably you will get
this post 1.1

-- Chinthaka




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] XmlSchema & Axiom for next Axis2 release

[Eran Chinthaka]

John Kaputin (gmail) wrote:
> Hi all,
> what plans does the Axis2 community have regarding XmlSchema and Axiom
> releases for the next release of Axis2 proposed for later this month?

Axiom release will, most probably, available by 15th Sep. XmlSchema,
there are some changes that are being done these days by Dims and
Jochen. I prefer if one of them can talk about it.
Anyway, we need to have a release on XmlSchema, before Woden and Axis2
releases.

Any volunteers for that?


> 
> At the weekly Woden chat we discussed doing a milestone release of Woden
> in time for the next Axis2 release, but as Woden depends on XmlSchema
> and Axiom we really need to build against the same releases used (or to
> be used) by the next Axis2 release.

John, I prefer if Woden also can depend on the latest Xmlschema stuff.
So +1 for deciding Woden release plans soon after XmlSchema release.

Thanks,
Chinthaka



signature.asc
Description: OpenPGP digital signature

[Axis2] Enabling listener to handle more than one EPR

[Eran Chinthaka]

Hi,

Current transport listener interface enables a listener to return only
one EPR per listener. But some listeners can handle more than one EPRs.
One of the examples is that the same servlet can be used to handle both
SOAP and REST messages, but can have different endpoints.

So this is a proposal to add a method to transport listener interface
which can return an array of EPRs.

public EndpointReference[] getEPRsForService(String serviceName, String
ip) throws AxisFault;

This will make the EndpointReference getEPRForService(String
serviceName, String ip) method to be redundant. So let's make that
method deprecated (can we remove it now itself?) and will be changing
all the internal classes to use the new method.

Please review and comment on this and the commit with this change will
follow soon.

Thanks,
Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Enabling listener to handle more than one EPR

[Eran Chinthaka]

David Illsley wrote:
> Eran,
> Can you explain to me how the user of this method will be able to tell
> the difference between e.g. a SOAP and a REST EPR?

Basically, the current behavior is you just ask the EPR from a listener.
Think of this scenario as well. One can map the same servlet to
different context paths. In that case servlet as the http transport
listener can handle more than one EPRs. The current method doesn't
facilitate it.

> 
> I'm a little nervous about making a change like this without fully
> understanding what and how the multiple EPRs can be used as if it's
> not totally clear it's a probable source of problems.
> 
> Also, are you intending to update the ListenerManager.getEPRforService
> method as well? If so, how will its users determine which EPR to use?

I will not update but rather deprecate it. This is especially useful
when a service lists out EPRs. Determining which EPR to use will be
transport dependent code. For example, one might getEPRs using this
method and generate proper binding within WSDL.

Thanks,
-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Enabling listener to handle more than one EPR

[Eran Chinthaka]

David Illsley wrote:
> On 12/09/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
>> David Illsley wrote:

>> I will not update but rather deprecate it. This is especially useful
>> when a service lists out EPRs. Determining which EPR to use will be
>> transport dependent code. For example, one might getEPRs using this
>> method and generate proper binding within WSDL.
> 
> ok, so if you deprecate that method presumably you'll remove it's use
> in ServiceContext and OutInAxisOperationClient? How will they
> determine which element in the array to use?

If a listener returns more than one EPR, any EPR is valid. So pick one.
I'd say the first one.

What that means is, if there is a servlet which returns following EPRs :

http://myip/myhome/services and
http://myip/anotherHome/services

then it should be able to handle any of them.

But we might want to special case REST EPRs. That's a different issue.



-- Chinthaka



signature.asc
Description: OpenPGP digital signature

[Axis2][Vote] Thilina as the release manager for Axis2 1.1

[Eran Chinthaka]

Hi,

I'd like to nominate Thilina Gunarathne as our new release manager for
Axis2 1.1. I'm sure he will have the luxury of releasing the most stable
Axis2 version so far :).

Here is my +1.

Thanks,
Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Enabling listener to handle more than one EPR

[Eran Chinthaka]

Derek Ho wrote:
> 
> Hi, Eran..., a servlet can be accessed via both http:// and https://.
> 
> So, the new method should support the generation of https:// based EPR
> as well, shouldn't it?
Yes, but only if the servlet (or the web container) is configured to
work like that and the listener is aware of it.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: errors in the Packaging step

[Eran Chinthaka]

Are u using Axis2 or Axis 1.x?

-- Chinthaka

SEOGCHAN OH wrote:
> Dear
> 
> Could anyone tell me in detail how to compile the skeleton file using
> ant? The skeleton file is automatically generated by using WSDL2Java.
> 
> I am following "Packaging" part in " Writing Web Services by Code
> Generating Skeleton" of user guide. The explanation of the user guide
> just simply said " compile the skeleton and the supporting classes",
> which is hard to understand.
> 
> Thank you in advance,
> 
> SC.




signature.asc
Description: OpenPGP digital signature

Re: [Axis2][Vote] Create a branch for the Axis2 1.1 release

[Eran Chinthaka]

Sanjiva Weerawarana wrote:
> On Wed, 2006-09-13 at 10:55 -0700, Bill Nagy wrote:
>> Hi all,
>>
>> I would like to propose that we create a branch in Subversion for the
>> 1.1 release (and all future releases) so that we can continue
>> development on the main trunk while the release is occurring.  This
>> would also enable us to make point fixes to each release without
>> requiring that users adopt a whole bag of new features (i.e. the next
>> release) in order to get bug fixes.  (I'm not saying that we will
>> backport all bug fixes, just that having the release branch would enable
>> us to do so.)
> 
> +1 from me but can we do that a bit closer to the release? Its easier to
> not have to merge too much stuff ..

+1 to Sanjiva's comment. I hope we don't want to make the life harder
for the people who are working hard for the release, by an effort to
make the life easier (is it?) to the rest.

Merging is, at least theorotically, a great idea and a concept. But when
conflicts are coming, practically its a nightmare.

And as Bill suggested, we can *not* do quick releases after minor fixes.
The release process of Axis2 is becoming problematic due to the
dependencies to other projects. So you can not decide at one point, at
least now, and release an Axis2 version. Simple example for you to
understand is releasing Axis2 with SNAPSHOTs. Hope everyone who involved
during past releases can remember the pain we had when once we released
Axis2 with a SNAPSHOT.

Please understand that I'm not opposing Bill's idea. But I know the pain
we are/were going thru whenever we are/were releasing.

-- Chinthaka

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




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Thread model for handlers

[Eran Chinthaka]

David Illsley wrote:
> Hi all,
> I've just been reviewing the AddressingOutHandler and noticed that it
> sets an instance variable in the invoke method which it then uses
> later in another method. I've reviewed the architecture docs and the
> Handler Javadoc but neither tell me if this is ok or not.
> 
> An investigation of the Phase code suggests to me that it is not -
> that for a given service there is a single instance of a Handler and
> so instance variables should not be used as the same instance may be
> invoked simultaneously from multiple threads. Is this correct and/or
> is there any documentation about this that I've missed?
If there is something like that, I do accept all the complaints and
please feel free to correct it.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2][Vote] Create a branch for the Axis2 1.1 release

[Eran Chinthaka]

Whilst agreeing with Dims, here are few more points.

We always can branch after a release, as we *always* create a tag, just
before the release. But so far, I've never seen we releasing a quick fix
after a release, using branches, in Apache WS projects. So I don't think
we have a problem in that.

Creating branches before the release : The code will be frozen for a
small number of days. Creating branch will help people to improve the
code during that time. But what who decides which improvement should go
only to the branch or to both? The committer or the release manager
(RM)? I hope its the RM.

Then we are asking him to do more work in addition to that tons of work
he has while releasing. He has to carefully analyze, *each* commit done
to the branch. Just be a RM once, you will realize how difficult it is.

We are talking about pausing the development for couple of days vs more
hazzle to the RM. Why can't we help him for the release by testing the
artifacts in the mean time :).

BTW, the subject says this is a vote. But the vote has moved away from
the original proposal. Do we wanna start a new vote or forget this (;) )?

-- Chinthaka

Davanum Srinivas wrote:
> +1 to creating a branch. *PLEASE* note that the branch for a release
> is the prerogative of the Release Manager and he/she chooses when to
> cut the branch.
> 
> thanks,
> dims
> 
> On 9/14/06, Nicholas L Gallardo <[EMAIL PROTECTED]> wrote:
>>
>>
>> Ajith,
>>
>> Branching before would allow others to continue longer term
>> development items while the final fixes are being applied to the
>> upcoming release.
>>
>> Regards,
>>
>>
>> Nicholas Gallardo
>>  WebSphere  -  WebServices Development
>>  [EMAIL PROTECTED]
>>  Phone: 512-838-1182
>>  Building: 901 / 5G-016
>>
>>
>>
>>
>>
>>
>>
>>  "Ajith Ranabahu" <[EMAIL PROTECTED]>
>>
>> 09/14/2006 04:11 PM
>>
>>
>> Please respond to
>>  axis-dev@ws.apache.org
>>
>>
>> To axis-dev@ws.apache.org
>>
>> cc
>>
>>
>> Subject Re: [Axis2][Vote] Create a branch for the Axis2 1.1 release
>>
>>
>>
>>
>>
>>
>>
>>
>> Hi guys,
>>  If I understand right the branching usually happens at the same time 
>> of a release (or slightly after) and is usually used to fix issues in
>> that particular release. We can definitely use a branch before the
>> release but is there any particular reason why we need a branch before
>> the release ?
>>
>>
>>  --
>>  Ajith Ranabahu
>>
> 
> 
> 




signature.asc
Description: OpenPGP digital signature

[ANN] Apache AXIOM 1.1 Released

[Eran Chinthaka]

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

we are proud to announce the release of Version 1.1 of Apache AXIOM!
(Download : http://ws.apache.org/commons/axiom/download.cgi )

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!

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
==

* Improved XML serialization
* DOM Hash implementation
* Improved MTOM handling
* Improved tree handling with multiple partial built elements
* Numerous bug fixes

If you like to contribute to AXIOM please help us to shape AXIOM. Any
contribution in the form of coding, testing, submitting improvements to
the documentation, and reporting bugs are always welcome.

Project Mailing List : commons-dev@ws.apache.org

Thanks for your interest in Apache AXIOM!


-The Apache AXIOM Development Team




signature.asc
Description: OpenPGP digital signature

[AXIOM][Axis2] Sharing experiences while releasing Axiom

[Eran Chinthaka]

Hi,

I had little bit of trouble, this time than any of the previous times,
while releasing Axiom.

It could have been better if the maven 1 to maven 2 migration was
completed before the release. In Axiom we release two artifacts (binary
and source) and I wrote two scripts for it, using maven1. But these were
not converted (AFAIK, I do not know if there are any as there were no
documentation). Since the folder structure was changed significantly
most of the scripts found in maven.xml were not working.

So when I was trying to release I couldn't use maven1 or maven2 for it,
which made me to waste extra time to fix the maven.xml.

Then came problems with site generation. For that, since maven2
structure enables resources in different folders (apt, resources, xdoc),
it was difficult to change maven1 to generate the site. And maven2
didn't support plain htmls to be put in the site. Meaning, if I put an
html, it will just show it without formatting them or adding left pane
and applying maven templates. If that has to happen, all the docs should
be converted either to apt or xdoc format. This would have been worse if
this happened during an Axis2 release as it has lots of documents.

Please do not take this as a blame. I also like the movement from maven1
to maven2, which has advantages like faster builds, etc.,
(FYI : Build time in Axiom is now 33 seconds with maven2 vs 1 min and 18
sec with maven1. And I can observe tests are running extremely fast)

But we must make sure we can do everything we did with maven1 also to be
done with maven2. Mind you, Axis2 has lots of scripts written in
maven.xmls in different places. I'd prefer if these are also converted
at once when the conversion happens.

So this is what I prefer to see when the conversion happens, in addition
to the pom.xml and changed folder structure:

1. converting or making sure *all* the documents are properly published
whilst generating the site
2. make sure *all* the scripts are working

Thanks,
Eran Chinthaka



signature.asc
Description: OpenPGP digital signature

Do we need to create branches prior to releases? [Was : [Axis2][Vote] Create a branch for the Axis2 1.1 release]

[Eran Chinthaka]

Hi Bill,

Bill Nagy wrote:
> Hi all,
> 
> There's actually a good description of the why and how's of creating a
> release branch in the Subversion book
> (http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.branchmerge.commonuses.patterns.release)

You've missed one important point there.

It says "developers need to keep writing new features while
quality-assurance teams take time to test supposedly-stable versions of
the software".

In Axis2 or any other Apache project, who are these quality assurance
people? They non-other than devs itself. So If devs have contributed
enough to this release, I hope they don't have enough time to implement
new features than testing the release :)


> 
> I don't understand why folks are saying that figuring out what goes
> where is tricky or that the work is that difficult.  I agree with dims
> that the RM should be in charge of creating the branch for the release
> -- that branch is then the RM's responsibility.  The RM gets to decide
> which bug fixes (or features I suppose) get added to the branch after it
> is made.
Seems one of us has not got Dims' point. IIUC, what he says is RM has
the "authority" to decide to create a branch or not AND if he creates it
he can decide when and how. What that means is he should be able to not
to create a branch, if he wants and then freeze the code and do the
release and then create the branch. Dims, I understood your statement
like that and that's why I agreed with it.


> 
> The RM, however, has no more of a vote than anyone else as to what gets
> placed into the trunk.  Bug fixes that are made to the release branch
> should most likely be committed to the trunk as well, but the RM doesn't
> have to be the one that does it.  (If another committer made the change
> to the release branch, then they should probably also commit the change
> to the trunk.)  
This is one of the problems I'm referring. When RM starts his release
process, and if some one commits to the release branch saying this
should go in to the release, RM is totally lost. RM might wanna decide
that it's known bug and go ahead with the release. But the committer
acts on his or her own discretion. When I vote for the RM, I give full
right him to decide about the code and what goes in the release.

> Moving changes between branches with subversion is
> relatively trivial, and, unless the release drags on, I can't imagine
> that the code bases will diverge that much.

Does this mean, if the release time is short you are happy even without
branches? Seems we are agreeing now. We only have four days between code
freeze and the release. And we all fight for that four days. Isn't it?

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] Axis2 release progress (Axis2 1.1)

[Eran Chinthaka]

Thilina,

Since it's easier to keep track of this using wiki, I added the progress
here (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.1)

-- Chinthaka

Thilina Gunarathne wrote:
> Hi All,
> As per the vote and later postpone message, we are planning to have
> the Axis2 1.1 release on 29th September 2006.
> 
> 
> - Release progress of Axis2's dependent projects,
>   - Axiom: Already Done
>   - XmlSchema : positive, Hopefully in the week starting from 18th Sep.
>   - Woden : positive
>   - Neethi2 - positive. Please update us about the *progress* of Axis2
> integration.
>   - Jibx - still no news. Please update us about the progress.
> 
> 
> - Still there are few blockers, and I am sure that we can fix them
> before 25th Sep.
> 
> - Need status of certain modules within Axis2. These modules are
> currently not part of the nightly build snapshots.
>   - JaxWs
>   - Jaxbri
>   - Jibx
>   - Spring
> 
> If we do not get satisfactory feedback, I might have to do the release
> without the above modules.
> 
> I would like to do the code freeze by 25th September. Please give us
> your fullest contribution to make this release happen.
> 
> Thanks
> Thilina
> 




signature.asc
Description: OpenPGP digital signature

Re: [AXIOM][Axis2] Sharing experiences while releasing Axiom

[Eran Chinthaka]

Seems every one is silent as you need to feel it to know the problem :).

Anyway another point I'd like to raise here.

As I mentioned earlier,  maven2 requires documents to be in either xodcs
format or apt format to be tightly integrated in to the site generated.
But if we convert all the docs to this format, then we can not include
the docs inside the binary release, as user can not read apt or xdocs.
To make users to read the docs in the release, we can make the docs in
to html. But in that case those docs will not be properly integrated,
when we generate the site.

What can we do for this? The only option available for me now is to
exclude docs in the distribution :(.

Thanks,
Chinthaka

Eran Chinthaka wrote:
> Hi,
> 
> I had little bit of trouble, this time than any of the previous times,
> while releasing Axiom.
> 
> It could have been better if the maven 1 to maven 2 migration was
> completed before the release. In Axiom we release two artifacts (binary
> and source) and I wrote two scripts for it, using maven1. But these were
> not converted (AFAIK, I do not know if there are any as there were no
> documentation). Since the folder structure was changed significantly
> most of the scripts found in maven.xml were not working.
> 
> So when I was trying to release I couldn't use maven1 or maven2 for it,
> which made me to waste extra time to fix the maven.xml.
> 
> Then came problems with site generation. For that, since maven2
> structure enables resources in different folders (apt, resources, xdoc),
> it was difficult to change maven1 to generate the site. And maven2
> didn't support plain htmls to be put in the site. Meaning, if I put an
> html, it will just show it without formatting them or adding left pane
> and applying maven templates. If that has to happen, all the docs should
> be converted either to apt or xdoc format. This would have been worse if
> this happened during an Axis2 release as it has lots of documents.
> 
> Please do not take this as a blame. I also like the movement from maven1
> to maven2, which has advantages like faster builds, etc.,
> (FYI : Build time in Axiom is now 33 seconds with maven2 vs 1 min and 18
> sec with maven1. And I can observe tests are running extremely fast)
> 
> But we must make sure we can do everything we did with maven1 also to be
> done with maven2. Mind you, Axis2 has lots of scripts written in
> maven.xmls in different places. I'd prefer if these are also converted
> at once when the conversion happens.
> 
> So this is what I prefer to see when the conversion happens, in addition
> to the pom.xml and changed folder structure:
> 
> 1. converting or making sure *all* the documents are properly published
> whilst generating the site
> 2. make sure *all* the scripts are working
> 
> Thanks,
> Eran Chinthaka
> 




signature.asc
Description: OpenPGP digital signature

[AXIOM] Releasing Axiom 1.1.1

[Eran Chinthaka]

Hi all,

The released version of Axiom 1.1 was compiled on jdk15. But we have a
minimum requirement to support jdk14. We can not simply correct this
error by replacing jars as the distributables are already reflected on
mirrors and it is not allowed to replace jars in maven repos.

So I will be releasing Axiom 1.1.1 today, asap. Sorry for the
inconvenience caused.

Thanks,
Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [AXIOM] Releasing Axiom 1.1.1

[Eran Chinthaka]

Will do. but I have not tested wstx-3.0.1

-- Chinthaka

 Original Message 
Subject: [AXIOM] Releasing Axiom 1.1.1
Date: Mon, 18 Sep 2006 12:13:57 +0530
From: Eran Chinthaka <[EMAIL PROTECTED]>
Reply-To: axis-dev@ws.apache.org,   [EMAIL PROTECTED]
To: [EMAIL PROTECTED],  axis-dev@ws.apache.org

David Illsley wrote:
> Hi,
> I noticed over the weekend that Axiom 1.1 has the woodstox dependency as:
>  stax.impl.groupid=woodstox
>  stax.impl.artifactid=wstx
>  stax.impl.version=asl-3.0.0
> 
> and Axis2 head has:
>  stax.impl.artifactid=wstx
>  stax.impl.groupid=woodstox
>  stax.impl.version=asl-3.0.1
> 
> Would it be possible/appropriate to bring Axiom up to the 3.0.1 level
> so the dependencies are the same for Axiom 1.1.1 and Axis2 1.1?
> 
> Cheers,
> David
> 
> On 18/09/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> The released version of Axiom 1.1 was compiled on jdk15. But we have a
>> minimum requirement to support jdk14. We can not simply correct this
>> error by replacing jars as the distributables are already reflected on
>> mirrors and it is not allowed to replace jars in maven repos.
>>
>> So I will be releasing Axiom 1.1.1 today, asap. Sorry for the
>> inconvenience caused.
>>
>> Thanks,
>> Chinthaka
>>
>>
>>
>>
> 
> 




signature.asc
Description: OpenPGP digital signature

[ANN] Axiom 1.1.1 Released

[Eran Chinthaka]

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

we are proud to announce the release of Version 1.1.1 of Apache AXIOM!
(Download : http://ws.apache.org/commons/axiom/download.cgi )

NOTE: This is a bug-fix release: AXIOM 1.1 release was compiled in JDK1.5, when 
we have a minimum requirement of jdk 1.4 compatible
distributables. There are no new features or fixes in this release other than 
being compiled on JDK 1.4. The original release note follows.

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!

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.

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
==

* Improved XML serialization
* DOM Hash implementation
* Improved MTOM handling
* Improved tree handling with multiple partial built elements
* Numerous bug fixes

Thanks for your interest in Apache AXIOM!


-The Apache AXIOM Development Team




signature.asc
Description: OpenPGP digital signature

[ANN] Apache XmlSchema 1.1 Released !!

[Eran Chinthaka]

http://ws.apache.org/commons/XmlSchema/

we are proud to announce the release of Version 1.1 of Apache XmlSchema!
(Download : http://ws.apache.org/commons/XmlSchema/download.cgi )

XMLSchema is a lightweight schema object model that can be used to
manipulate and generate XML schema representations. It has no external
dependencies and can be easily integrated into an existing project.

You are welcome to kick the tires and get XMLSchema on the move. If you
like to help us shape XMLSchema any contribution in the form of coding,
testing, submitting improvements to the documentation, and reporting
bugs are always welcome.

Thanks for your interest in XMLSchema!

- The XMLSchema Development Team




signature.asc
Description: OpenPGP digital signature

(Yet Another) Build Failure !!

[Eran Chinthaka]

Hi,

I experience another build failure in Axis2. I doubt these are after 
Dennis' series of commits. The first failure was from org.*.jibx.Test. 
When I commented out that test, again there was a failure in > 
/modules/security/target/interop/work/src/org/apache/axis2/security/InteropScenarioClient.java.


Dennis can you please look in to this.

One more thing. You have introduced following new test to 
MessageReceiverTemplate.




This is not working as expected. I think what you wanted to do was to 
skip if usedbmethod is not set. But the correct way to do that is




This change had broken ADB unwrapping code.

I have this change locally, but can not commit as I get the above test 
failure.


-- Chinthaka

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

[Axis2] (Yet Another) Build Failure !!

[Eran Chinthaka]

Hi,

I experience another build failure in Axis2. I doubt these are after 
Dennis' series of commits. The first failure was from org.*.jibx.Test. 
When I commented out that test, again there was a failure in > 
/modules/security/target/interop/work/src/org/apache/axis2/security/InteropScenarioClient.java.


Dennis can you please look in to this.

One more thing. You have introduced following new test to 
MessageReceiverTemplate.




This is not working as expected. I think what you wanted to do was to 
skip if usedbmethod is not set. But the correct way to do that is




This change had broken ADB unwrapping code.

I have this change locally, but can not commit as I get the above test 
failure.


-- Chinthaka

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

Re: [Axis2] Allowing users to set their own replyTo value

[Eran Chinthaka]

Jaliya Ekanayake wrote:

Yes, we can do this using one-way messages.
However, when we use axis2 client inside a container we don't need to 
use the replyTo generated by axis2, rather we can use the endpoint that 
is already there.

How can we do this?


You need to register a new TransportListener from whatever the container 
you are in. For example, if you are running Axis2 inside jetty, then you 
need to register jetty listener as your http transport listener (you 
will have to implement the TransportListener on that). Axis2 will ask 
from the transport listener for an EPR, given a service name.


-- Chinthaka

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

Re: [Axis2] Allowing users to set their own replyTo value

[Eran Chinthaka]

David Illsley wrote:

In general I consider RM to be a QOS and as such should be able to be
applied without modifying the application.

Totally agreed!!



I also don't think that the generally understood semantic for
isUseSeperateListner is what you described. I'd be really surprised if
any sizeable portion of users thought it means anything outer than use
a separate connection for the response (don't use the back channel) as
that's the only way I've seen it documented.


David, its not only that. this is how I interpret isUseSeperateListner 
and hope this will match with what is implemented as well.


isUseSeperateListner means, please use a different channel as mentioned 
by David, BUT, please manage the second channel also for me.
Meaning, if isUseSeperateListner is true then Axis2 engine should also 
start a listener to receive the response depending on the replyTo address.


So isUseSeperateListner serves two things.

-- Chinthaka

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

Re: [Axis2] Allowing users to set their own replyTo value

[Eran Chinthaka]

Hi Chamikara,

Before you do the change, can you please be kind enough to summarize the 
change you gonna do?


Thanks,
Chinthaka

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

Re: Error occurred while testing the CodeGen Tool

[Eran Chinthaka]

Thanks Anne.

Can we please add these links to our jibx document?

In addition to that I can see a link to jibx-example.html from 
/xdocs/1_1/jibx/jibx-codegen-integration.html. But I can not see a 
jibx-example.html inside xdocs. Dennis, do you like to fix it?


Thanks,
Chinthaka

Anne Thomas Manes wrote:

See http://ws.apache.org/axis2/1_0/jibx/jibx-codegen-integration.html
and http://jibx.sourceforge.net/tutorial/binding-tutorial.html.
The binding file specifies how to map Java object to XML.

Anne

On 9/26/06, Evanthika Amarasiri <[EMAIL PROTECTED]> wrote:


 Hi,
 I was testing the Code Generator tool with and gave the command
"WSDL2Java.bat -uri
C:\WSO2-Projects\Axis2\Nightly_builds\axis2-std-SNAPSHOT-src\modules\samples\wsdl\Axis2SampleDocLit.wsdl 


-o C:\WSDLJavaTool\output -d jibx" and I got the following exception.

 Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: jibx binding option requires -bindingfile 
{file

path} parameter
 at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) 


 at
org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
 at
org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
 Caused by: java.lang.RuntimeException: jibx binding option requires
-bindingfile {file path} parameter
 at
org.apache.axis2.wsdl.codegen.extension.JiBXExtension.engage(JiBXExtension.java:52) 


 at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177) 


 ... 2 more

 Seems that the command requests the parameter -bindingfile along with 
jibx.

Can some one please tell me what this refers to?

 Thanks,
 Evanthika



-
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] Allowing users to set their own replyTo value

[Eran Chinthaka]

Hang on a bit.

Ok, I agree to include this property. But we need to do following while 
implementing it.


1. Once this property is set, user _MUST_ set a replyTo EPR
2. When this property is set and when user sets a replyTo epr, what if 
the reply never comes back to the same Callback? Then we need to handle 
this properly.
3. How will RM or anyone who sets the replyTo epr hand over the response 
message to the Callback object?


Thanks,
Chinthaka

Chamikara Jayalath wrote:

Hi Chinthaka,

OK.

As u mentioned in ur previous mail currently the semantics of 
isUseSeperateListner=true has two things.


1. Don't use the back channel of the request message to build the response.
2. Mr. Axis2,  please manage the second channel for me.

Now what I want it someway to only give the first semantic. I.e. the 
second channel will be managed by my own manner (for e.g. RM polling).


I believe this is a general requirement.

My sugestion is to introduce a new property to the options object named 
DONT_USE_AXIS2_LISTNER (please suggest a different name if this sounds bad).


If this property is not set execution will be done as it is currently 
implemented. But if it is set to 'true' Axis2 will not start its listner 
and will allow user to set what ever the replyTo value he wants.


Hope this clarifies.

Chamikara
 

On 9/27/06, *Eran Chinthaka* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


Hi Chamikara,

Before you do the change, can you please be kind enough to summarize
the
change you gonna do?

Thanks,
Chinthaka

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





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

Re: [Axis2] Allowing users to set their own replyTo value

[Eran Chinthaka]

Thanks Chamikara for the explanation.

And +1 from me for the implementation. Please add a note to the 
Options.setProperty() method about this with the name of the property.


-- Chinthaka

Chamikara Jayalath wrote:

Hi Chinthaka,

Please see below.

On 9/27/06, *Eran Chinthaka* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


Hang on a bit.

Ok, I agree to include this property. But we need to do following while
implementing it.

1. Once this property is set, user _MUST_ set a replyTo EPR



Ok.

2. When this property is set and when user sets a replyTo epr, what if
the reply never comes back to the same Callback? Then we need to handle
this properly.


When user set this property  he  explicitly knows that somebody else 
will be managing the delivering of the message to the callback. If that 
mechanism fails it has no difference from a failure of the current 
'Axis2 Listner' scenario. I.e. the callback will never be called.


3. How will RM or anyone who sets the replyTo epr hand over the response
message to the Callback object?



In the polling case, Sandesha2 implementation will be doing an 
axisEngine.reveive () call for the reply message obtained through 
polling, allowing it to be delivered to the users callback.


Chamikara


Thanks,
Chinthaka

Chamikara Jayalath wrote:
 > Hi Chinthaka,
 >
 > OK.
 >
 > As u mentioned in ur previous mail currently the semantics of
 > isUseSeperateListner=true has two things.
 >
 > 1. Don't use the back channel of the request message to build the
response.
 > 2. Mr. Axis2,  please manage the second channel for me.
 >
 > Now what I want it someway to only give the first semantic. I.e. the
 > second channel will be managed by my own manner (for e.g. RM
polling).
 >
 > I believe this is a general requirement.
 >
 > My sugestion is to introduce a new property to the options object
named
 > DONT_USE_AXIS2_LISTNER (please suggest a different name if this
sounds bad).
 >
 > If this property is not set execution will be done as it is currently
 > implemented. But if it is set to 'true' Axis2 will not start its
listner
 > and will allow user to set what ever the replyTo value he wants.
 >
 > Hope this clarifies.
 >
 > Chamikara
 >
 >
 > On 9/27/06, *Eran Chinthaka* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
 > mailto:[EMAIL PROTECTED]>>> wrote:
 >
 > Hi Chamikara,
 >
 > Before you do the change, can you please be kind enough to
summarize
 > the
 > change you gonna do?
 >
 > Thanks,
 > Chinthaka
 >
 >
-

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


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





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

Re: 'latest' dir is now renamed to '1_1' in axis2 xdocs

[Eran Chinthaka]

Is there a particular reason why this is not kept as "latest" and move 
to 1_1 when we release? (At the same time I can not see a latest folder 
anymore in the svn). That approach will enable people to work always 
with the "latest" documents.


The only advantage I can think of creating 1_1 folder is links 
management. But if we manage links with relative urls, which is the way 
it should be done, then even that is not a problem.


The best approach, IMHO, that could have done was to leave it as latest 
and when we release, move the whole thing to 1_1 and update the 
navigation.xml to update the navigation pane.


Keeping the latest folder as it is will make sure users will always 
commit to the same folder.


-- Chinthaka

Chatra Nakkawita wrote:

Hi,

Just a note to let you know that the latest dir in the 
https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/ is 
now renamed as 1_1.


This was done as part of updating/creating documents for upcoming Axis2 
1.1 release and to  make sure that all the links in terms of Axis2 1.1 
documents work. The documents for this release are been worked on 
currently. Any document updates in terms of Axis2 1.1 version needs to 
be made on 
https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/1_1.


Once Axis2 1.1 is released, we will create a latest dir (which will 
start off as a copy of the final 1_1 dir, to make sure that we use an 
up-to-date documents version) which will serve as the working document 
directory. Which means that after 1.1 release what ever updates in terms 
of the worked on Axis2 version will be made on the new 'latest' dir.


Thanks & regards,

Chatra



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

Re: 'latest' dir is now renamed to '1_1' in axis2 xdocs

[Eran Chinthaka]

Hmm, seems everyone is agreeing. So who opposed this earlier? :D

Chatra Nakkawita wrote:
+1 from me too. Like you saidI agree that any changes of a previous 
release should be made in the branch itself.


And yes, this is not the first time we've had this arguement :-)

Chatra

On 9/29/06, *Afkham Azeez* <[EMAIL PROTECTED] > 
wrote:


I fully agree with Deepal. Maintaining two versions of the
documentation on the trunk is an adhoc way of version management.
When SVN does such a good job, why should we go for such an adhoc
structure? We never do this for the code, so why special treatment
for the docs? As Deepal said, the correct way of doing this should
be cutting a branch in SVN after the 1.1 release, and any
documentation bugs in 1.1 should be fixed in that branch (and most
probably, also in the trunk). BTW, I think this is not the first
time this has been argued on this list :D

Azeez


On 9/29/06, *Deepal Jayasinghe* <[EMAIL PROTECTED]
> wrote:

Hi Chatra and all,

Well , I know we had the same kind of structure for previous
releases as
well . But I am -1 on keeping two doc folders.  And I can not
name any
other Apache project which use this kind of document structure.
In the
meantime keeping duplication data make unnecessary  complication ,
  - if we find error in one document ,  need to change them in two
location. Is that good habit (I dont think so)
  - If some one new to Axis2 , and if he download Axis2 what
kind of doc
structure will he get ? if I download Axis2 today do I need to know
about the previous version docs. (I know its useful to have them
in the
web site , but not in the code base)

And remember , we use "SVN" and after each release we cut a
branch , so if
some one want to update old doc , go and update them in the
branch (if you
think it is really necessary, o.w just update that in the
current SVN)

Specially I dont like to have version related stuff , in the
current code
base , if we have we should remove them.

Finally , this is the first time I -1 in this mailing list ,
that is b'coz
I honestly dont like that  :).

Thanks
Deepal



Chatra Nakkawita wrote:
>  Hi,
>
>  Just a note to let you know that the latest dir in the
>
https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/

is
>  now renamed as 1_1.
>
>  This was done as part of updating/creating documents for
upcoming Axis2
>  1.1 release and to  make sure that all the links in terms of
Axis2 1.1
>  documents work. The documents for this release are been worked on
>  currently. Any document updates in terms of Axis2 1.1 version
needs to
>  be made on
>
https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/1_1

.
>
>  Once Axis2 1.1 is released, we will create a latest dir (which
will
>  start off as a copy of the final 1_1 dir, to make sure that we
use an
>  up-to-date documents version) which will serve as the working
document
>  directory. Which means that after 1.1 release what ever
updates in terms
>  of the worked on Axis2 version will be made on the new
'latest' dir.
>
>  Thanks & regards,
>
>  Chatra
>
>
>
-
>  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]





-- 
Thanks
Afkham Azeez 






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

[Axis2] Adding revision number while resolving issues

[Eran Chinthaka]

Hi,

When you fix a bug and resolve a JIRA, let's make it a best practice to
include the revision number in the comment you put while resolving the
JIRA.

I'm now trying to fix a bug related elementFormDefault="qualified", but
seems this was fixed earlier by Ajith. But when I use the current build
I get the same error. So I wanted to see what he has done to re-fix it
but I have no clue which version to look for.

I've seen Dims doing this, and once in a while I also did it. But shall
we all make it a best practice and do that always? A humble request.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature