[ANN][Axis2] Apache Axis2/C 0.92 Released

[Samisa Abeysinghe]

Hi All,

We are pleased to announce the release of Apache Axis2/C version 0.92.
You can download this release from
http://ws.apache.org/axis2/c/download.cgi

We welcome your early feedback on this implementation. Please send your 
feedback to [EMAIL PROTECTED]


Major Changes Since Last Release

  1. Completed MTOM implementation with multiple attachment support and 
non-optimized case

  2. Completed service client API with send robust and fire and forget
  3. Added "message" to description hierarchy
  4. Archive based deployment Model (for services and modules)
  5. Code generation for WSDL using Java WSDL2Code tool
  6. ADB support (with Java WSDL2Code tool)
  7. WS-Security usernameToken support
  8. Initial implementation of the XML Schema parser (To be used in 
WSDL parser and REST support)
  9. Initial implementation of WSDL parser (To be used in dynamic 
invocation)
 10. Changed double pointer environment parameters into pointer 
parameters to improve efficiency


Key Features

  1. AXIOM, an XML object model optimized for SOAP 1.1/1.2 Messages. 
This has complete XML infoset support.
  2. Support for One-Way Messaging (In-Only) and Request Response 
Messaging (In-Out)

  3. Module Architecture, mechanism to extend the SOAP processing model
  4. Context hierarchy
  5. Directory based deployment model
  6. Raw XML providers
  7. WS-Addressing, both the submission (2004/08) and final (2005/08) 
versions

  8. Transports supports: HTTP
   * Both simple axis server and Apache2 httpd module o SSL 
client transport

  9. Service Groups
 10. Service client and operation client APIs
 11. REST support (POST case)
 12. Module version support
 13. Archive based deployment Model
 14. MTOM support
 15. WSDL Code Generation Tool for Stub and skeletons (based on Java 
tool) New

   * Axis Data Binding - ADB New
 16. Security module, usernameToken support New

Un-Implemented Architecture Features (TBD in 1.0)

  1. Sessions scoping for Application, SOAP, Transport and Request levels
  2. Different character encoding support
  3. REST (REpresentational State Transfer) Support (GET case)
  4. Dynamic client invocation (given a WSDL, consume services dynamically)

Un-Implemented Architecture Features (TBD post 1.0)

  1. Security module with encryption and signing
  2. Server side Web Service Policy support
  3. C2WSDL
  4. WSDL2C

Thanks for your interest in Axis2C

-- Apache Axis2C Team --



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

Re: [Vote][Axis2] Rajith Attapattu as a committer

[Samisa Abeysinghe]

+1
Samisa...

Davanum Srinivas wrote:


+1

On 7/14/06, Srinath Perera <[EMAIL PROTECTED]> wrote:


+1 .. welcome !!!
Thanks
Srinath

On 7/14/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
> 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
>
>
>
>


--

Srinath Perera:
   http://www.cs.indiana.edu/~hperera/
   http://www.bloglines.com/blog/hemapani

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

[Axis2][ANN] Apache Axis2/C 0.93 Released

[Samisa Abeysinghe]

We are pleased to announce the release of Apache Axis2/C version 0.93.
You can download this release from
http://ws.apache.org/axis2/c/download.cgi

Key Features

  1. AXIOM, an XML object model optimized for SOAP 1.1/1.2 Messages.
This has complete XML infoset support.
  2. Support for one-way messaging (In-Only) and request response
messaging (In-Out)
  3. Description hierarchy (configuration, service groups, services,
operations and messages)
  4. Directory based deployment model
  5. Archive based deployment model
  6. Context hierarchy (corresponding contexts to map to each level of
description hierarchy)
  7. Raw XML message receiver
  8. Module architecture, mechanism to extend the SOAP processing model
  9. Module version support
 10. Transports supports: HTTP
   o Both simple axis server and Apache2 httpd module for server side
   o Client transport with ability to enable SSL support
 11. Service client and operation client APIs
 12. REST support (HTTP POST case)
 13. WS-Addressing, both the submission (2004/08) and final (2005/08)
versions
 14. MTOM/XOP support
 15. Code generation tool for stub and skeleton generation for a given
WSDL (based on Java tool)
   o Axis Data Binding (ADB) support
 16. Security module with UsernameToken support
 17. REST support (HTTP GET case) - New
 18. Dynamic invocation support (based on XML schema and WSDL
implementations) - New

Major Changes Since Last Release

  1. REST support for HTTP GET case
  2. XML Schema implementation
  3. Woden/C implementation that supports both WSDL 1.1 and WSDL 2.0
  4. Dynamic client invocation (given a WSDL, consume services dynamically)
  5. Numerous improvements to API and API documentation
  6. Many bug fixes, especially, many paths of execution previously
untouched were tested along with
 Sandesha2/C implementation

TODOs Remaining for 1.0

  1. Complete API documentation and API improvements
  2. Fix major memory leaks
  3. Test codegen for both ADB and none cases
  4. Put in place a comprehensive functional test framework
  5. WSDL2C tool


We welcome your early feedback on this implementation.
Thanks for your interest in Axis2C

-- Apache Axis2C Team --



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

[Axis2] Codegen tool command line options

[Samisa Abeysinghe]

I have few problems with codegen command line options.

I would like it to have some getopt (see man page) like syntax. However 
there are some problems here.


First:
It is the usual convention that we use -- for long options. Long options 
are any option that has more than one char. e.g. ss, sd
Either we have to come up with single char alternatives to them or have 
to change the syntax to --


Second:
If I use -lc it breaks, I have to use -l c

Third:
We have getopt like implementation in Java. e.g. Xalan has 
src/org/apache/xalan/xsltc/cmdline/getopt/GetOpt.java

We can use this and improve command line option parsing

Fourth:
Without something like getopt, we cannot drop the need for -uri in the 
current syntax (I think there a Jira requesting to drop -uri option)


Thoughts please...
Samisa...

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

Re: [Axis2] Codegen tool command line options

[Samisa Abeysinghe]

Ajith Ranabahu wrote:

Hi,
Lemme add my thoughts here.



First:
It is the usual convention that we use -- for long options. Long options
are any option that has more than one char. e.g. ss, sd
Either we have to come up with single char alternatives to them or have
to change the syntax to --


The problem with always having 1 character short options is that they
become less descriptive and gets confusing soon. And it is not nice to
have them use the long version always. Perhaps we can go into an Axis
1.1 like options where uppercase and lowercase letters are used in
places of conflict [1]. However we have come long way with these
options and it will not be nice to break the whole thing by reverting
all the option names. We would have to do deprecate - drop cycle.


Second:
If I use -lc it breaks, I have to use -l c


Yes - the for the current commandline options parsers the parameters
need to be seperated by a space. I'm not sure whether this greatly
affects usability (linux/unix lovers may not agree with me on that ;))
but we can definitely improve the parser to take that into account.

Well I was looking into the parser to improve it. This is where I 
concluded that we need GetOpt like thing.

The point is when we have both -lc -ss  as options, then it converts to
   option l with arg c
   option s with arg s
However we treat ss as one option, so while the parser logic could be 
improved, it becomes overly complex.


As a solution to the concern that you have raised against the use of --, 
we can hide the user from -- by treating

-ss as -s a;  -sd as -s d; -sn as -s n and -ssi as -s si internally.
This again is complex logic, but I hope we may live with it.


Third:
We have getopt like implementation in Java. e.g. Xalan has
src/org/apache/xalan/xsltc/cmdline/getopt/GetOpt.java
We can use this and improve command line option parsing


There is this thing called commons commandline [2]. I have tried
several times to put that in but did not get time to do it. I'm not
sure how suitable the xerces thing would be (It may give us a direct
dependancy on xerces that we do not want) so I guess something like
the commons CLI would be the right thing.
Well I was thinking copying GetOpt.java from Xalan and improving to that 
to match our needs (Should be OK as it is the same licence). I had a 
look at CLI, but for me, it is too complex for our requirement.


I could look into GetOpt.java and improve it, however to do that, I need 
to know the number of args expected by each command line option 
mentioned in
CommandLineOptionConstants.WSDL2JavaConstants. Could you please let me 
know those numbers?


Thanks,
Samisa...



Fourth:
Without something like getopt, we cannot drop the need for -uri in the
current syntax (I think there a Jira requesting to drop -uri option)


Well you can :) But it'll rather be better to go ahead with commons
CLI and use the capabilities of that to deal with it.





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

Re: [ANN][Axis2]Axis2 1.2 Released

[Samisa Abeysinghe]

Axis2/C team used to vote on the feature list but form 0.96 release 
onwards, we vote on the release artifacts before the release.
Gives room for the commiters who are voting for the release to test the 
actual release and then vote.


Samisa...

Glen Daniels wrote:

+1, David.  I think both this and the recent branch/change conventions 
thread are pointing towards a slightly more formal process for getting 
releases out, which I think is a good thing.


--Glen

David Illsley wrote:


Jeremy,
 From watching a number of WS-Commons and Axis2 releases, it appears
that neither project votes on release binaries in line with the way
the Incubator does things, we seem to simply vote on the principle of
having a release soon with a given feature-set. I don't believe that
in and of itself that's a problem...

However, we've now had a couple of Axiom and Axis2 releases in the
recent past where the need for an x.y.z + 0.0.1 release has become
apparent within days of a release (the most recent at [1]). The impact
of lack of community testing on real Release Candidates is, imo
showing up in clear fashion.

Given that, I'm thinking of proposing that we adopt the incubator
method of publishing a real Release Candidate build + associated SVN
revision number that we vote on, rather than voting on "having a
release soon".

N.B. This isn't meant as criticism of anyone, but an observation that
the current method seems to be producing less that ideal results.

Thoughts/Comments/Suggestions?
David

[1] http://issues.apache.org/jira/browse/AXIS2-2607

On 30/04/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:


Hi Dims,

I will do it soon , I can create a tag with my local changes.

Thanks
Deepal

Davanum Srinivas wrote:

> Deepal,
>
> Looks like one of the release steps got missed :(
>
> -- dims
>
> On 4/30/07, Alex Boisvert <[EMAIL PROTECTED]> wrote:
>
>>
>> Has a SVN tag been created for Axis2 1.2 ?   I do not see one in the
>> usual
>> place:
>>
>> [EMAIL PROTECTED]:~/svn/axis2$ svn ls
>> http://svn.apache.org/repos/asf/webservices/axis2/tags/java
>> rampart_1_1/
>> v0.94/
>> v0.95/
>> v1.0/
>> v1.1/
>> v1.1.1/
>>
>> thanks,
>> alex
>>
>>
>>
>
>

--
Thanks,
Deepal

"The highest tower is built one brick at a time"



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







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







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

[ANN] Axis2/C 1.0.0 Released

[Samisa Abeysinghe]

Apache Axis2/C Team is pleased to announce the release of Apache Axis2/C 
version 1.0.0

You can download this release from
http://ws.apache.org/axis2/c/download.cgi

Key Features

  1. Support for one-way messaging (In-Only) and request response 
messaging (In-Out)
  2. Client APIs: Easy to use service client API and more advanced 
operation client API

  3. Transports supported: HTTP
a. Inbuilt HTTP server called simple axis server
b. Apache2 httpd module called mod_axis2 for server side
c. IIS module for server side
d. Client transport with ability to enable SSL support
e. libcurl based client transport
  4. Module architecture, mechanism to extend the SOAP processing model
  5. WS-Addressing support, both the submission (2004/08) and final 
(2005/08) versions, implemented as a module

  6. MTOM/XOP support
  7. AXIOM, an XML object model optimized for SOAP 1.1/1.2 messages; 
This has complete XML infoset support

  8. XML parser abstraction
a. Libxml2 wrapper
b. Guththila pull parser support
  9. Both directory based and archive based deployment models for 
deploying services and modules
 10. Description hierarchy providing access to static data of Axis2/C 
runtime (configuration, service groups, services, operations and messages)
 11. Context hierarchy providing access to dynamic Axis2/C runtime 
information(corresponding contexts to map to each level of description 
hierarchy)

 12. Message receiver abstraction
a. Inbuilt raw XML message receiver
 13. Code generation tool for stub and skeleton generation for a given 
WSDL (based on Java tool)

a. Axis Data Binding (ADB) support
 14. Transport proxy support
 15. REST support (more POX like) using both HTTP POST and GET
 16. Comprehensive documentation
a. Axis2/C Manual

Major Changes Since Last Release

  1. Many Bug Fixes
  2. IIS module for server side
  3. libcurl based client transport
  4. Improvements to overall API to make it more user friendly, stable 
and binary compatible

  5. Transport proxy support
  6. Memory leak fixes  


We welcome your early feedback on this implementation.
Thank you for your interest in Axis2/C.

-- Apache Axis2/C Team --



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

[Axis2] Engaging modules at runtime.

[Samisa Abeysinghe]

Forwarding with correct prefix.

 Original Message 
Subject:Engaging modules at runtime.
Date:   Mon, 7 May 2007 13:10:03 +0530
From:   Saminda Abeyruwan <[EMAIL PROTECTED]>
Reply-To:   axis-dev@ws.apache.org
To: axis-dev@ws.apache.org



Hi,

AxisConfiguration has the following methods,

 public void engageModule(AxisModule axisModule, AxisConfiguration 
axisConfig)

   throws AxisFault {
   engageModule(axisModule);
   }   --- > [1]

   private void engageModule(AxisModule module) throws AxisFault {...} 
--> [2]


What is the purpose of [1]. Wouldn't it better to modify the access 
modifier of [2] to *public* and remove [1].


Thank you

Saminda


--
Saminda Abeyruwan

Software Engineer
WSO2 Inc. - www.wso2.org <http://www.wso2.org>

--
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services 
Developers' Portal)


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

Re: Eventing

[Samisa Abeysinghe]

[EMAIL PROTECTED] wrote:


Hi

  I need to have support for events in my webservice.
  Can anybody suggest how to do that?
 


Try Savan http://ws.apache.org/savan/source-repository.html with Axis2

Samisa...


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

Re: [Axis2] What's next - 1.2.1 or 1.3?

[Samisa Abeysinghe]

It would be great if you could ship the WSDL2C related changes we have 
done to svn head with 1.2.1.

I hope Amila would be aware of the changes that I am talking about.

Thanks,
Samisa...

Paul Fremantle wrote:


There are some changes to the mail transport required in a 1.2.1 release.

Deepal has the details.

Paul

On 5/12/07, Asankha C. Perera <[EMAIL PROTECTED]> wrote:


Dims

I would want two fixes we asked for in Axiom to be released if an Axis2
1.2.1 goes out soon.. One is on the UUIDGenerator used by Axis2 - that
creates non-unique IDs which I think is critical even for Axis2

I do not think a 1.3 right now with the changes taking place in the
trunk would be good, especially for dependent projects like Synapse..
and think its better to take some time to complete the cleanup and
refactoring which is taking place, and then make 1.3..

asankha

Davanum Srinivas wrote:
> Folks,
>
> Can we make a case for a 1.2.1? (Real soon?) I guess we should cut it
> from the 1.2 branch. It should have absolutely minimal changes from
> 1.2. For example the unwrapping changes for ADB that Amila checked in
> today comes to mind. If Michele confirms the fix for the
> AUTO_RELEASE_CONNECTION related changes that can be ported as well.
> What else do we absolutely need to fix? If the list grows too long, it
> may be better to just stick to trunk and do a 1.3 very soon (but not
> as fast as we can cut 1.2.1). Anyways, what do you all think? Are
> there changes needed by Rampart and/or Sandesha and/or Synapse and/or
> Tuscany etc that dictate that we should do a quick 1.2.1? WDYT?
>
> thanks,
> dims
>

-
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: Rest APIs

[Samisa Abeysinghe]

[EMAIL PROTECTED] wrote:


Hi

 


Can anybody help me enable rest APIs in my webservices?


http://ws.apache.org/axis2/1_2/rest-ws.html

Axis2 HTTP endpoints can handle both REST and SOAP by default, unless 
you explicitly disable it using disableREST parameter in axis2.xml conf 
file.


HTH.

Samisa...

--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa


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

Re: Rest APIs

[Samisa Abeysinghe]

keith chapman wrote:

Hi Samitha,

Are you using Axis2-1.1.1? from your axis2.xml it looks like so. The 
code fragment that saminda 

Samisa not saminda ;)

had given works on Axis2-1.2 and not 1.1.
BTW, just a minor note. In http://ws.apache.org/axis2/1_2/rest-ws.html, 
there is no mention on how to enable REST on server side. Yes it is 
enabled by default, but would be great if that is mentioned, along with 
info on how to disable REST.


Thanks,
Samisa...



Can you confirm on your version please.

Thanks,
Keith.

On 5/25/07, [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>* 
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:



Hi
Following is my axis2.xml entries by default.


false


false


false

It seems axis2.war is coming by default with rest API's disabled.

When I am trying to access
http://localhost:8080/axis2/rest/Version/getVersion through
browser i am
getting the following error "Please enable REST support in
WEB-INF/conf/axis2.xml and WEB-INF/web.xml"

-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>]
Sent: Friday, May 25, 2007 7:43 AM
To: axis-dev@ws.apache.org <mailto:axis-dev@ws.apache.org>
Subject: Re: Rest APIs

[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> wrote:
>
> Hi
>
>
>
> Can anybody help me enable rest APIs in my webservices?
>
http://ws.apache.org/axis2/1_2/rest-ws.html

Axis2 HTTP endpoints can handle both REST and SOAP by default, unless
you explicitly disable it using disableREST parameter in axis2.xml
    conf
file.

HTH.

Samisa...

--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa


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



The information contained in this electronic message and any
attachments to this message are intended for the exclusive use of
the addressee(s) and may contain proprietary, confidential or
privileged information. If you are not the intended recipient, you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately and destroy all copies of this
message and any attachments.

WARNING: Computer viruses can be transmitted via email. The
recipient should check this email and any attachments for the
presence of viruses. The company accepts no liability for any
damage caused by any virus transmitted by this email.

www.wipro.com <http://www.wipro.com>

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




--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/ 



--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa


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

Re: Axis2 Architecture problems. ... not any more ;)

[Samisa Abeysinghe]

Eran Chinthaka wrote:

6. About faults, yes I also agree with you for some extent. When Deepal
initially put that we had some discussions on that.
  

"Why there is a separate flow to handle the Faults?"
With my understanding, the handers to be invoked when there is a fault, 
could be different form the handlers that could be invoked when there is 
no fault.
(Going by the definition, a flow is a collection of phases and a phase 
is a collection of handlers). Now it is questionable if it is really 
necessary to have different handlers for fault path or the same set of 
handlers could deal with both fault cases and non fault cases.


Samisa...

--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa


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

Re: Axis2 Architecture problems. ... not any more ;)

[Samisa Abeysinghe]

Ajith Ranabahu wrote:


However we may be able to improve a bit of the code :) Since the
handlers are stateless replicating them would not mean anything
(shouldn't make a difference). 

+1. I too agree.

Should we able to create a read-only
List implementation where only one of the handler instances exist in
the engine ?

Looking at the logic:
   ArrayList outPhases = new ArrayList();
   outPhases.addAll((ArrayList) executionChain.clone());
   outPhases.addAll((ArrayList) msgContext.getConfigurationContext()
   .getAxisConfiguration().getGlobalOutPhases().clone());
   msgContext.setExecutionChain(outPhases);

It does not look like we do any changes to the list after cloning. Hence 
would be better off to drop cloning.


Samisa...

--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa


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

Re: Axis2 Stack Comparison

[Samisa Abeysinghe]

[EMAIL PROTECTED] wrote:


Hi

 


I have seen

 

http://wiki.apache.org/ws/StackComparison that Axis2 
<http://wiki.apache.org/ws/StackComparison%20that%20Axis2> is 
supporting WS-Eventing and no modules is mentioned there.


 


Does that mean axis2 supports WS-Eventing by itself?


WS-Eventing is implemented as a module, similar to WS-Security and WS-RM.
Please see http://ws.apache.org/savan/source-repository.html for source.

Samisa...


--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa


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

Re: Axis2 Architecture problems.

[Samisa Abeysinghe]

Sanjiva Weerawarana wrote:

Deepal Jayasinghe wrote:

The main reason behind handler chain clone was to support dynamic
modification of the chain, that is some one can change the current
handler chain while he is processing the message. So we clone the
template handler chain and store that in the message context.


This particular feature I've always felt is YAGNI. AFAIK we don't have 
a single use-case for this right now .. so why don't we introduce a 
flag "cloneHandlerChain" which is false by default and we document it 
and tell people to set a parameter (globally or in services.xml) to 
set it if they want the thing cloned.
Absolutely +1 for the flag. I too was trying to find a use case for but 
could not find any.


Samisa...

--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa


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

Re: [Vote][Axis2] Charitha Kankanamge as a committer

[Samisa Abeysinghe]

On 6/6/07, *Deepal Jayasinghe* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


I would like to propose Charitha Kankanamge as an Apache
Axis2/Java committer.


+1.

Samisa...

--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa


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

Re: Plan for the hackathon

[Samisa Abeysinghe]

To add something, APR people have defined a set of guidelines for 
versioning: http://apr.apache.org/versioning.html
Though APR is a C project, there would be somethings to take form that - 
specially API compatibility with respect to version numbers. What could 
be broken and what should not be broken form major, minor to patch 
versions would help to keep backward compatibility that some users are 
complaining about.


Samisa...

Ajith Ranabahu wrote:

Hi all,
I am sure the Axis2ers around the world are excited about the
hackathon that is about to start tomorrow [Well today - (Monday 11th
June) :)] Unfortunately I can only come for half the days but I'm sure
any major decision will be reported to the list and the irc will be
live as usual (I will participate in the sessions remotely as far as
possible) However more importantly we need to outline the objective
and layout the things we plan to attack.

I will outline some items I felt as important to address while
browsing the Jira list. Others are welcome to jump in and correct me
in any place that I've missed. Again I believe the objective of this
hackathon is to fix whatever is broken in the existing functionality
rather than adding or discussing new features.

1. Exception handling
 Number of issues have been reported about incorrect exception
handling, irrelavant exceptions being thrown etc. So it seems that
this is something we need to look at more carefully and correct.

2 .WSDL2WS and ADB issues
 There are number of 'edge cases' reported about WSDL2WS - specially
against the ADB binding. While some of these will fall into new
features, I suppose we should address all the issues that are against
the existing features and make it work for some of those edge cases.

3. Java2WSDL issues
There are some blockers reported about Java2WSDL. I believe Java2WSDL
works ok for most of the cases but there seems to be some cases we
need to answer. Both for WSDL2WS and Java2WSDL, they are the two most
'visible' components for the users and that makes it important

4. Misc
There are a ton of small issue that does not specifically fall into a
broad category. I'm hoping we can cover most of them by the time we
end up fixing the major issues but we could tackle whatever is
remaining once the major issues are covered.

5. Documentation
While we will not sit and write the user guide once more at this
occasion I see this as a time we can add some of the missing javadocs
to the source (and also correct some header problems. I see a Jira
that says some license headers are not proper)

Anything else we can try to tackle in this limited time frame?

Ajith Ranabahu

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





--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa


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

Re: New Axis2/C user

[Samisa Abeysinghe]

Shanmuc wrote:

Hi group,

   I am new to the axis2/c framework. Can anybody guide me through on how to
use the Axis2/c framework to write my own operation for peforming client,
server interactions.

I do not understand clearly the programming technique given in the home
page. Please can somebody guide me to write a new operstion and to steps to
execute ;)
  
Please have a look at the quick start guide at 
http://ws.apache.org/axis2/c/docs/axis2c_manual.html#quick_start.


Also please subscribe to axis-c-user list, more info on how to subscribe 
can be found here: http://ws.apache.org/axis2/c/lists_issues.html
If you find any problems with quick start guide, you can raise the 
issues over the axis2-c-user list.


Thanks,
Samisa...

Thanks in Advance.

~Shanmugam
  



--
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services 
Developers' Portal)


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

Re: [Axis2][VOTE]Axis2 1.3 release artifacts (#take3)

[Samisa Abeysinghe]

+1.
Thanks,
Samisa...

Ruchith Fernando wrote:

+1

Thanks,
Ruchith

On 8/10/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote:
  

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all,

I have uploaded Axis2 1.3 (take3) into my Apache home location [1]
again . As a result of we found a few issues in 1.3 take2 I had to
upload the artifacts again and call for a new vote. I will keep open
the vote for 72 hrs from now and will do the Axis2 1.3 release on
Monday 13th Aug 2007.

You can find both IntelliJ idea and Eclipse plugin artifacts in the
tools folder [2]

Please try to cover the following areas when testing.
- - Code generation
- - Sessions
- - Web application
- - In different application servers
- - Both JDK 1.5 and JDK 1.4
- - Java2WSDL
- - POJOs
- - And whatever the JIRA we have marked as fixed.

You can find maven2 repository under my home directory as well [3]. I
have host the web site for 1.3 in [4] please have a look at that as well

I will do the final release on Friday (10th Aug 2007), here is my +1
for the release date as well as for release artifacts.


[1] : http://people.apache.org/~deepal/axis2/1.3-take3/
[2] : http://www-lk.wso2.com/~deepal/1.3-tools/
[3] : http://people.apache.org/~deepal/axis2/1.3-take3/m2-repo/
[4] : http://www-lk.wso2.com/~deepal/axis2/


P.S : Please note that I need to have two more PMC vote to go ahead
with the release, so please give us the support by voting for the release.


Thanks
Deepal
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGvFhvjOGcXNDx0CARAh+4AJ49M1d86/v39C6Z0WnMcxsK5RgF3QCdGD8d
43gXJ+tvuyHhc/nI1t1u1fw=
=sqos
-END PGP SIGNATURE-


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






  



--
Samisa Abeysinghe : WSO2 WSF/C
"http://wso2.org/projects/wsf/c?WSO2 Web Services Framework/C - Open source C library for providing and consuming Web services";


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

Re: [Vote][Axis2] Sumedha Rubasinghe as a committer

[Samisa Abeysinghe]

+1.

Samisa...

Lahiru Sandakith wrote:


+1

On 3/20/07, *Deepal Jayasinghe* <[EMAIL PROTECTED] 
> wrote:


Hi All,

I would like to propose Sumedha Rubasinghe as an Apache Axis2/Java
committer. He has contributed Axis2 , AXIOM a lot specially
implementing
SAAJ module. In addition to that he is very active in the
community and
giving him a commitership will encourage him to contribute more
and more
into the project.

Following are the list of JIRAs that he has summited patches.
https://issues.apache.org/jira/browse/SANDESHA2-50
https://issues.apache.org/jira/browse/WSCOMMONS-147
https://issues.apache.org/jira/browse/WSCOMMONS-152
https://issues.apache.org/jira/browse/WSCOMMONS-156
https://issues.apache.org/jira/browse/WSCOMMONS-157
https://issues.apache.org/jira/browse/WSCOMMONS-176
https://issues.apache.org/jira/browse/AXIS2-2199
https://issues.apache.org/jira/browse/AXIS2-2283
https://issues.apache.org/jira/browse/AXIS2-2331
https://issues.apache.org/jira/browse/AXIS2-1956


Here is my +1 for making Samudha as a commiter.

Thanks,
Deepal




-
To unsubscribe, e-mail: [EMAIL PROTECTED]

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





--
Regards
Lahiru Sandakith 




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

Re: Extensions to Axis2/Java deployment engine

[Samisa Abeysinghe]

Would OSGi would be more useful to "end users" or to those who want to 
"embed" and "bundle" Axis2?


Samisa...

Asankha C. Perera wrote:

Saminda

Thanks for the detailed reply.. Please see my comments below, I will 
only take the top 5 points for each list I asked for to keep this 
discussion short, as I believe these are in the order of importance/use
1. When aar/mar behavior is mimicked in an OSGi bundle, these bundles 
be able to live in different class spaces.
   ex: If the bundles needed different hibernate versions they can be 
easily plug into different class spaces.

I see this as a good use for the "end users"!


2. We will be able to have multiple version of Axis2 instancres 
running inside same JVM.

   This require the need of minimizing System properties.
But you really will need to change ports/queues etc to really run two 
axis2 versions. (i.e. there is no way two instances can share the same 
http/s port, or the JMS queue or check for email on the same account 
etc..). So the probability of this use and the value would be less. So 
this is not a good candidate for position # 2.
3. Axis2 will be able to initiate same transport with different 
versions.
   This will require proper integration of OSGi services. I haven't 
touched this area yet, otherwise whole situation will be overwhelming.
See comment above.. again this is not something and "end user" will 
see much value in.. its like being able to deploy the same transport 
twice - at the same time. Also transports would be tied to axis2 
versions, and if you have a newer version, its probably much better 
than a previous one anyway.. so again I don't see this as a good 
candidate for position # 3
4.  OSGi life-cycle support. This will give the ability to 
start/stop/install/update/uninstall bundles.
ex: I have myModule.jar which would mimic myModule.mar. We will 
be able use the above actions to to manipulate the AxisModule as we 
need.
What most end users would do is write services.. and I believe they 
already can do some amount of life cycle management.. can you tell me 
what "new" improvements this will give?
5.  Once a user has written a bundle (which mimic 
aar/mar/transport/etc), they just need to upload them into a "Axis2 
bundle repository", where the community can search them and install 
them into there system, without shutting down the running system.
Typically a "user" written aar file is not really shared AFAIK.. but 
this is possible even as they are already.. as for the mar's - the 
most famous ones are rampart, sandesha/mercury etc.. which are 
"released".



=
In Synapse point of view.

1. Mediators can be written as OSGi bundles. When you start the 
bundle, the proper factory is called and build the relevant object 
model.
This is irrelevant, you will not just "add a mediator" at runtime.. 
but you can configure or update your sequence etc at runtime, and you 
can do it now itself (e.g. WSO2 ESB)
2. Different version of same mediator is highly possible. i.e two 
mediator can live in two different class spaces.
Again, this is highly unlikely, since a newer version is better 
improved or fixes a bug of an older version, also you will not be able 
to configure two mediators as they register a unique QName in the 
configuration.
3. You will be able to remove Sun service providers facility of 
loading extension to bundles, which will be support in all Java 
implementations.
This maybe good, but does not itself show much advantage, as we can do 
the Sun service provider with a bit of custom code in any JDK anyway..

4. Synapse guys like embedded devices ?
Not me.. but Synapse is being embedded.. but I don't see how this has 
relevance


thanks
asankha

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





--
Samisa Abeysinghe

http://people.apache.org/~samisa/


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

Re: Extensions to Axis2/Java deployment engine

[Samisa Abeysinghe]

Ruwan Linton wrote:


Also just wanted to make sure, what is the advantage of being OSGi 
with Java 7 which promises to provide versionning via JAM (Java 
Application Modules)


How long would it be before "everyone" adopts 1.7?

Samisa...

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

Re: org.apache.axis2.AxisFault: Couldn't find repository location 'repository'

[Samisa Abeysinghe]

Dini Omar wrote:

Hi all,

I am trying to engage the rampart module but for some reason it is not 
being found. Here is the directory structure that i have (src is the 
project root)


/src/com.alp.ccs21.soapgw.gw <http://com.alp.ccs21.soapgw.gw>
/src/lib
/src/repository/modules/rampart-1.3.mar

And here is the code to engage rampart

ConfigurationContext ctx = 
ConfigurationContextFactory.createConfigurationContextFromFileSystem("repository", 
null);


As the "repository" directoy is in the same folder as the project 
root, i was expecting it to be found  but i am getting this error.
   


org.apache.axis2.AxisFault: Couldn't find repository location 'repository'
at 
org.apache.axis2.deployment.FileSystemConfigurator.(FileSystemConfigurator.java:67)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:180)

at com.alp.ccs21.soapgw.gw.ToDHLCli.readFiles(ToDHLCli.java:399)


I am doing this wrong?


Try giving the full path.

Samisa...



Thanks






--
Samisa Abeysinghe

http://people.apache.org/~samisa/


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

Re: [Axis2] Online Java docs for 1.4 release is missing... & proposal to remove pre 1.0 docs..

[Samisa Abeysinghe]

Thilina Gunarathne wrote:

http://ws.apache.org/1_4/api/index.html link gives a 404...

On a similar note, how about removing the pre 1.0 documentation from 
the web site and redirecting them to new docs. Search engines still 
points to these outdated older docs (0.93) for some queries way before 
pointing to the new docs..


+1 for removing old docs.

Samisa...



thanks,
Thilina

--
Thilina Gunarathne - http://thilinag.blogspot.com



--
Samisa Abeysinghe

http://people.apache.org/~samisa/


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

Re: [VOTE] Andreas Veithen as a WS committer

[Samisa Abeysinghe]

+1.

Samisa...

Paul Fremantle wrote:

+1 from me. Andreas has done an excellent job on the transports and
many other aspects of Synapse and he has also contributed effectively
here on this mailing list.

Paul

On Mon, Sep 22, 2008 at 12:18 PM, Sanjiva Weerawarana
<[EMAIL PROTECTED]> wrote:
  

+1!

Asankha C. Perera wrote:


Folks

Andreas Veithen has been an active committer of the Apache Synapse project
from February, and has helped improve, add and enhance the transport
implementations that grew under the Synapse project for Apache Axis2. Now as
we move some of these transports into WS-Commons, I propose that Andreas be
granted Karma in the WS project to help continue this work

asankha


  

--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

Blog: http://sanjiva.weerawarana.org/


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







  



--
Samisa Abeysinghe

http://people.apache.org/~samisa/


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

Re: [DISCUSS] Axis2 as TLP

[Samisa Abeysinghe]

Jochen Wiedmann wrote:

On Tue, Oct 28, 2008 at 4:02 AM, Glen Daniels <[EMAIL PROTECTED]> wrote:

  

* Axis2 - becomes a TLP for both Java and C versions, with
Axis2-specific components underneath as subprojects.  So Rampart,
Sandesha, Savan, Kandula



I'd discourage a common TLP for both Java and C versions.

I know this is the usual behaviour in a lot of other projects (Xerces,
Log4j, to name a few). However, I think that the most important aspect
of a TLP is a community. A community = one community, not two
communities. IMO, the common denominator between Axis C and Axis Java
is quite small and not worth bothering. Otherwise we'd simply have the
next umbrella.
  


-1. They share the same architecture. They do the same this, only the 
implementation is different. And they are supposed to work with each 
other, interop in other words, so they have lot in common.


It is a fact that, you can interop being disjoint projects. However, we 
even use the WSDL2Code tool to generate code. If Axis2/Java becomes a 
separate TLP and can an Axis2/C comittor do changed to that tool?


Samisa...


Jochen


  



--
Samisa Abeysinghe

http://people.apache.org/~samisa/


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

Re: [DISCUSS] Axis2 as TLP

[Samisa Abeysinghe]

Davanum Srinivas wrote:

Eran,

Clearly you did not read my previous emails. *PLEASE* read them and
then we can continue.

For example, I said "1. The proposal was to split Axis2+Anything that
Axis2 Uses+Anything that is built on Axis2 into a separate TLP."

Also, i said this before, but repeat it again, The current status quo
sucks. What we have is not working.
- Really bad web sites
- Really bad status of JIRA issues
- Really bad track record of making releases periodically
- There are many disjoint islands
- The set of projects mentioned above is totally disjoint from other
projects in WS PMC.
  


How can a TLP solve all these? If people are who they are now, even 
after making Axis2 a TLP, the bad websites and bad release cycles will 
remain.
On the other hand, if we cannot sync the releases of Axis2's sub 
projects, then irrespective of Axis2 being a TLP, it would turn out to 
be a useless project. Because one of Axis2's key strenghts is the set of 
sub projects it has.


So IMHO, what is more important is to solve the above problems. However, 
I doubt if TLP would be a solution for that.


Samisa...

What we have is broken, We are not the only ones in this situation,
this has happened before at Apache with XML and Jakarta PMC's. Please
go and look at the history and how the projects are faring now after
becoming logical/smaller footprint PMCs. Please go ask them or ask the
board@ or ask members if you don't believe, let's learn from their
experiences.

*IF* people who are on the current projects that are not in the "
Axis2+Anything that Axis2 Uses+Anything that is built on Axis2" list
want to tell us something, they should chime in and tell us what they
think and we'll take a vote.

Right now it's just a few of us who are just repeating the same things
over and over again without even reading what the other person is
saying.

thanks,
dims

On Thu, Oct 30, 2008 at 6:07 PM, Eran Chinthaka
<[EMAIL PROTECTED]> wrote:
  

On Thu, Oct 30, 2008 at 5:42 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote:


Chinthaka,

What are the problems that will be created? Please enumerate them. How
is it being handled / smoothed over now and what would change
specifically to make the cooperation not happen.
  

Problems :

1. Another member will have to waste time on doing PMC work
2. We will lose the tight dependency between Axis2 and related projects like
Axiom, Neethi, Sandesha, etc.,

There are numerous things like this that will happen.



If you can point your finger to specific scenarios. We can see if we
can come up with specific solutions. (Say common svn area where both
committers can have access).
  

Let me back up. What is broken in the current layout that mandates us to go
for different TLPs?




Also, Don't mind me, i repeat my mantra for the n-th time again. Those
who are actively working on a day to day basis should be taking the
decisions. What we are doing is not working and i propose we try
something new to see if it will work.
  

My point is exactly this. Why do we waste time on going to fix something
which is not broken? Let's get back to work ;)






  



--
Samisa Abeysinghe

http://people.apache.org/~samisa/


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

Re: [DISCUSS] Axis2 as TLP

[Samisa Abeysinghe]

Davanum Srinivas wrote:

Samisa,

You have hit the nail on the head. People are who they are. Right now
the umbrella is so vast that everyone is able to hide behind others.
There is no accountability. When there is a smaller group of active
people, There will be better accountability to each other and to the
board and to our end users.

There are tactics that we can employ for example, we should make a new
single release including all projects including XmlSchema, Rampart and
Sandesha with Axis2. But still make extra releases of say Sandesha2 as
necessary as well separately for Sandesha. You will ask, why can't we
do this today and i'll say that these kind of tactics work better with
a TLP like focus.
  
IMHO, sometimes, even getting an Axis2 release out of the door becomes a 
rolling stone, and takes so much time. I am not really sure how it would 
be to combine all those efforts together.


Some of the long running and trivial issues like the crappy web site can 
be easily solved, give some cycles. Even I can volunteer to do that. 
However, you have to consider the long tail, if at all a TLP is to be 
taken up. Even it might be a good idea to make Axis3 yes 3 a TLP, but 
not Axis2. Becase Axis2 as a TLP would not be the same as the Axis2 as 
it used to be, both in technical fronts as well as in non-technical fronts.


Thanks,
Samisa...


thanks,
dims

On Fri, Oct 31, 2008 at 4:28 AM, Samisa Abeysinghe
<[EMAIL PROTECTED]> wrote:
  

Davanum Srinivas wrote:


Eran,

Clearly you did not read my previous emails. *PLEASE* read them and
then we can continue.

For example, I said "1. The proposal was to split Axis2+Anything that
Axis2 Uses+Anything that is built on Axis2 into a separate TLP."

Also, i said this before, but repeat it again, The current status quo
sucks. What we have is not working.
- Really bad web sites
- Really bad status of JIRA issues
- Really bad track record of making releases periodically
- There are many disjoint islands
- The set of projects mentioned above is totally disjoint from other
projects in WS PMC.

  

How can a TLP solve all these? If people are who they are now, even after
making Axis2 a TLP, the bad websites and bad release cycles will remain.
On the other hand, if we cannot sync the releases of Axis2's sub projects,
then irrespective of Axis2 being a TLP, it would turn out to be a useless
project. Because one of Axis2's key strenghts is the set of sub projects it
has.

So IMHO, what is more important is to solve the above problems. However, I
doubt if TLP would be a solution for that.

Samisa...


What we have is broken, We are not the only ones in this situation,
this has happened before at Apache with XML and Jakarta PMC's. Please
go and look at the history and how the projects are faring now after
becoming logical/smaller footprint PMCs. Please go ask them or ask the
board@ or ask members if you don't believe, let's learn from their
experiences.

*IF* people who are on the current projects that are not in the "
Axis2+Anything that Axis2 Uses+Anything that is built on Axis2" list
want to tell us something, they should chime in and tell us what they
think and we'll take a vote.

Right now it's just a few of us who are just repeating the same things
over and over again without even reading what the other person is
saying.

thanks,
dims

On Thu, Oct 30, 2008 at 6:07 PM, Eran Chinthaka
<[EMAIL PROTECTED]> wrote:

  

On Thu, Oct 30, 2008 at 5:42 PM, Davanum Srinivas <[EMAIL PROTECTED]>
wrote:



Chinthaka,

What are the problems that will be created? Please enumerate them. How
is it being handled / smoothed over now and what would change
specifically to make the cooperation not happen.

  

Problems :

1. Another member will have to waste time on doing PMC work
2. We will lose the tight dependency between Axis2 and related projects
like
Axiom, Neethi, Sandesha, etc.,

There are numerous things like this that will happen.




If you can point your finger to specific scenarios. We can see if we
can come up with specific solutions. (Say common svn area where both
committers can have access).

  

Let me back up. What is broken in the current layout that mandates us to
go
for different TLPs?





Also, Don't mind me, i repeat my mantra for the n-th time again. Those
who are actively working on a day to day basis should be taking the
decisions. What we are doing is not working and i propose we try
something new to see if it will work.

  

My point is exactly this. Why do we waste time on going to fix something
which is not broken? Let's get back to work ;)






  

--
Samisa Abeysinghe

http://people.apache.org/~samisa/


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

Re: [DISCUSS] Axis2 as TLP

[Samisa Abeysinghe]

Deepal jayasinghe wrote:

Hi Sanjiva:

Sanjiva Weerawarana wrote:


Deepal, so just so I understand - are you saying you *don't* want to
keep Axiom with Axis2?
  

I'm not sure about Deepal, but I don't in fact think keeping Axiom
under the Axis2 project (yes, even despite the acronym :)) makes
sense.  In my version of the "new world order", Axis2 and the
components that are *Axis2-specific* (i.e. cannot profitably be used
outside Axis2) should be in the Axis2 project.  The stuff that is
reusable and more generally focused (i.e. Axiom, Neethi, XmlSchema,
etc) should IMO remain in WS so it can continue to be shared.

If we're talking about moving Axiom/Neethi/etc., then it really is
pretty much s/Web Services/Axis2/g and I wouldn't be in favor of that.


+1 .I understand what you mean , yes they should not come under Axis2 ,
and in fact we should try to get Axiom as a TLP (im not sure about Neethi).
  


Why not Neethi a TLP if AXIOM is so?


Samisa...


Deepal
  

--Glen

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






  



--
Samisa Abeysinghe

http://people.apache.org/~samisa/


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

Re: ADB test failure

[Samisa Abeysinghe]

I get a wired error building adb-codegen. Can someone please advise?

I am on Java 1.6

D:\svn\branches\axis2-1.6\modules\adb-codegen>mvn clean install 
-Dtest=false -DfailIfNoTests=false

[INFO] Scanning for projects...
[INFO] 


[INFO] Building Apache Axis2 - ADB Codegen
[INFO]task-segment: [clean, install]
[INFO] 


[INFO] [clean:clean]
[INFO] Deleting directory 
D:\svn\branches\axis2-1.6\modules\adb-codegen\target
[INFO] snapshot org.apache.axis2:axis2-adb:SNAPSHOT: checking for 
updates from apache-ws-snapshots2
[INFO] snapshot org.apache.axis2:axis2-adb:SNAPSHOT: checking for 
updates from apache.snapshots
[INFO] snapshot org.apache.axis2:axis2-codegen:SNAPSHOT: checking for 
updates from apache-ws-snapshots2
[INFO] snapshot org.apache.axis2:axis2-codegen:SNAPSHOT: checking for 
updates from apache.snapshots
[INFO] Setting property: classpath.resource.loader.class => 
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.

[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [remote-resources:process {execution: legal-files}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [antrun:run {execution: process-resources}]
[INFO] Executing tasks
[copy] Copying 7 files to 
D:\svn\branches\axis2-1.6\modules\adb-codegen\target\classes

[INFO] Executed tasks
[INFO] [compiler:compile]
[INFO] Compiling 17 source files to 
D:\svn\branches\axis2-1.6\modules\adb-codegen\target\classes
[INFO] 


[ERROR] BUILD FAILURE
[INFO] 


[INFO] Compilation failure
Failure executing javac,  but could not parse the error:
'javac' is not recognized as an internal or external command,
operable program or batch file.



Failure executing javac,  but could not parse the error:
'javac' is not recognized as an internal or external command,
operable program or batch file.


[INFO] 


[INFO] For more information, run Maven with the -e switch
[INFO] 


[INFO] Total time: 8 seconds
[INFO] Finished at: Tue Aug 25 05:33:48 IST 2009
[INFO] Final Memory: 14M/28M
[INFO] 


D:\svn\branches\axis2-1.6\modules\adb-codegen>

Thanks,
Samisa...

Amila Suriarachchi wrote:

yes, there was a commons-logging.properties file.

thanks Andreas.

Amila.


On 8/21/09, Andreas Veithen  wrote:
  

That is strange, because normally commons-logging should fall back to
JDK1.4 logging if log4j is not found. Maybe there is a
commons-logging.properties that slipped in somehow. Did you test the
build on a fresh working copy of Axis2?

Andreas

On Fri, Aug 21, 2009 at 12:04, Amila
Suriarachchi wrote:


I could run all the tests sucessfully by adding log4j dependency to parent
pom.xml.

I am wondering why it is not the case otherwise.

thanks,
Amila.




--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

  



  

Re: [Axis2] Removing old client side code from main source tree

[Samisa Abeysinghe]

IMHO, for the benefit of the users, if deprecation and obsoleting 
policies are defined, it would be great.
I mean, say you define a time period for obsoleting a deprecated 
feature, rather than obsoleting in an ad-hoc manner, so that all know 
how long a deprecated feature would be there before they can migrate to 
the new one.

Thanks,
Samisa...

Deepal Jayasinghe wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all;

As you know in the current SVN we have our old client side codes (Call
, InOutMEPClient etc..) and no body is using those, in fact they are
marked as deprecated.
So what if we move them to scratch area , keeping them in the main
source tree make no sense to me :)

here is my +1 for moving them away from Axis2 main tree , and I like
to do that before next release.



- --
Thanks,
Deepal

~Future is Open~
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEECFljOGcXNDx0CARAhNuAJ48vDhyQZLeE+ttK91Cfk4AqZR78QCeIWci
58/HlGJewGnSEJz7S99Owug=
=+vOj
-END PGP SIGNATURE-



 

[ANN][Axis2] Apache Axis2/C 0.91 Released

[Samisa Abeysinghe]

Hi All,

We are pleased to announce the release of Apache Axis2/C version 0.91.
You can download this release from
http://ws.apache.org/axis2/c/download.cgi

Key Features

 1. AXIOM, an XML object model optimized for SOAP 1.1/1.2 messages. This has 
complete XML infoset support.
 2. Support for One-Way Messaging (In-Only) and Request Response Messaging 
(In-Out)
 3. Module architecture, mechanism to extend the SOAP processing model
 4. Context hierarchy
 5. Directory based deployment model
 6. Raw XML providers
 7. WS-Addressing, both the submission (2004/08) and final (2005/08) versions
 8. Transports: HTTP
* Both simple axis server and Apache2 httpd module
* SSL client transport - New
 9. Service Groups - New
10. Service client and operation client APIs - New
11. REST support (POST case) - New
12. Module version support - New
13. MTOM support - New

Other notes

 1. Interoperability tested with Axis2/Java for XML in/out client and services
 2. Addressing 1.0 interoperability

Major changes since last release

 1. Full Addressing 1.0 support
 2. Improved fault handling model
 3. SSL client transport
 4. MTOM implementation
 5. Implementation of easy to use service client and operation client APIs for 
client side programming
 6. REST support (POST case)
 7. Module version support
 8. Service groups
 9. Numerous bug fixes since last release

Un-Implemented Architecture Features (TBD in 1.0)

 1. Sessions scoping for application, SOAP, transport and request levels
 2. Different character encoding support
 3. Dynamic invocation
 4. Archive based deployment Model

Un-Implemented Architecture Features (TBD post 1.0)

 1. WSDL code generation tool for stub and skeletons (based on Java tool)
 2. Security module
 3. REST (REpresentational State Transfer) support (GET case)
 4. Web Services policy support
 5. Axis2 Web application (Web App)

We welcome your early feedback on this implementation.
Thanks for your interest in Axis2C

-- Apache Axis2C Team --

[Axis2] C code generation using codegen tool - whre to put the code?

[Samisa Abeysinghe]

Hi All,
   Dimutu, one of the contributors to Axis2/C has developed some code 
to generate C code using the Java codegen tool.
   I initially thought this should go to Axis2/C svn. However, I see 
that there is a CSharpEmitter.java in Java svn. So I thought we could 
also place the C specific code too to the Java svn.


There would be the following Java classes to be added:
codegen/emitter:
CEmitter.java

codegen/writer:
CHeaderWriter.java  CSourceWriter.java  HeaderWriter.java

Also the templates to be added to template/c

Please let me know if you guys are OK to add this to Java svn. Also we 
have the property file to be added. Should we also add that to Java svn?


P.S. The rationale behind adding this source to Java svn is that the 
users would have built in C code gen capability. The alternative is to 
have this code in C svn, were the users would have to build a separate 
jar to get the job done.


Thanks,
Samisa...




 Original Message 
Subject:[axis2]c code generation using wsdl2java
Date:   Wed, 17 May 2006 16:19:52 +0530
From:   Dimuthu <[EMAIL PROTECTED]>
Reply-To:   Apache AXIS C Developers List 
To: axis-c-dev@ws.apache.org



Hi,
 I m working on axis2-c client side code generation using wsdl2java 
tool with the help of Ajith. I attach the current version to the jira. 
It's capable of generating stub code with xml in/out model.
To generate the code use the option 
-Dorg.apache.axis2.codegen.config=/org/apache/axis2/wsdl/codegen/codegen-config.properties 
with the c_codegen.jar  file in the classpath



Regards
Dimuthu



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

Re: [Axis2] C code generation using codegen tool - whre to put the code?

[Samisa Abeysinghe]

Here is the Axis2/C Jira that has the source attachment: 
http://issues.apache.org/jira/browse/AXIS2C-162

Should I create a separate Jira under Axis2(Java) project?

Thanks,
Samisa...

Sanjiva Weerawarana wrote:


On Fri, 2006-05-19 at 08:35 +0600, Samisa Abeysinghe wrote:
 


Hi All,
   Dimutu, one of the contributors to Axis2/C has developed some code 
to generate C code using the Java codegen tool.
   I initially thought this should go to Axis2/C svn. However, I see 
that there is a CSharpEmitter.java in Java svn. So I thought we could 
also place the C specific code too to the Java svn.


There would be the following Java classes to be added:
codegen/emitter:
CEmitter.java

codegen/writer:
CHeaderWriter.java  CSourceWriter.java  HeaderWriter.java

Also the templates to be added to template/c

Please let me know if you guys are OK to add this to Java svn. Also we 
have the property file to be added. Should we also add that to Java svn?
   



+1 from me.

While we're at it, can we move the wsdl2code project into its own WS
subproject? I'm not sure exactly what its Axis2 deps are but can it
simply depend on specific revision of the core jar (or whatever it
needs)? That will make it much easier for Axis2/C for example to ship
the codegen tool as its own tool as well. 


Sanjiva.


-
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] C code generation using codegen tool - whre to put the code?

[Samisa Abeysinghe]

Done.
Samisa...

Davanum Srinivas wrote:


Samisa,

You have commit privs...So please go ahead and commit the changes.

thanks,
dims

On 5/19/06, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:


Here is the Axis2/C Jira that has the source attachment:
http://issues.apache.org/jira/browse/AXIS2C-162
Should I create a separate Jira under Axis2(Java) project?

Thanks,
Samisa...

Sanjiva Weerawarana wrote:

>On Fri, 2006-05-19 at 08:35 +0600, Samisa Abeysinghe wrote:
>
>
>>Hi All,
>>Dimutu, one of the contributors to Axis2/C has developed some code
>>to generate C code using the Java codegen tool.
>>I initially thought this should go to Axis2/C svn. However, I see
>>that there is a CSharpEmitter.java in Java svn. So I thought we could
>>also place the C specific code too to the Java svn.
>>
>>There would be the following Java classes to be added:
>>codegen/emitter:
>>CEmitter.java
>>
>>codegen/writer:
>>CHeaderWriter.java  CSourceWriter.java  HeaderWriter.java
>>
>>Also the templates to be added to template/c
>>
>>Please let me know if you guys are OK to add this to Java svn. Also we
>>have the property file to be added. Should we also add that to Java 
svn?

>>
>>
>
>+1 from me.
>
>While we're at it, can we move the wsdl2code project into its own WS
>subproject? I'm not sure exactly what its Axis2 deps are but can it
>simply depend on specific revision of the core jar (or whatever it
>needs)? That will make it much easier for Axis2/C for example to ship
>the codegen tool as its own tool as well.
>
>Sanjiva.
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>


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








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

Re: [Axis2] C code generation using codegen tool - whre to put the code?

[Samisa Abeysinghe]

Dennis Sosnoski wrote:


Sanjiva Weerawarana wrote:


On Fri, 2006-05-19 at 10:25 +0530, Ajith Ranabahu wrote:
 


As for moving the codegen tool out, I'm not really sure we should be
doing that right now. One issue I see in that is the use of core Axis2
components inside the codegen module where there is a tight dependency
on Axis2 components such as the Axis service. Yet the codegen is
supposed to be "independent" to a certain extent and it surely belongs
in a seperate project.
  



So why not do it? All we need is to depend on the axis2-core jar right?
We can pick up a specific version of that from a maven repo and make it
work. I'm not seeing a negative reason for moving it out ...
 

We now have the data binding frameworks (at least JiBX, XMLBeans, and 
JAXB) decoupled from the codegen module for classloading purposes, but 
still tightly coupled in terms of the code. That means the couplings 
go both ways - codegen depends on the Axis2 core code, and the Axis2 
data binding modules depend on codegen. The situation with ADB and 
JaxMe is even worse, since these haven't been made into separate 
plugin modules for the codegen yet 
(http://issues.apache.org/jira/browse/AXIS2-558 and 
http://issues.apache.org/jira/browse/AXIS2-559). As long as there are 
these strong dependencies there appears to be little to gain by moving 
codegen into a separate project.


These difficulties aside, I don't really see a lot of benefit in 
moving this to a separate project. In the case of Axiom and TcpMon the 
coupling problems were much less and the use case for the code as 
separate entities much better, I'd think. Do you see other uses for 
the code generation beyond Axis2C? 


We could codegen for PHP, for PHP binding build on top of Axis2C.
Thanks,
Samisa...

It seems to me like it's only useful for SOAP frameworks, and those 
all have their own code generation implementations.


I'd think the needs of the C code generation can be handled by just 
adding a target to the build that generates a zip with the jars needed 
for codegen. That would certainly make it easier for me and the other 
developers working on the codegen than having it as a separate project.


 - Dennis

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

Axis2] Axis2 architecture implementation in C

[Samisa Abeysinghe]

FYI:

On Mon, 2005-09-26 at 22:18 +0600, Samisa Abeysinghe wrote:


Hi All,
Damitha, Nandika and myself have started to prototype AXIOM as a first 
step towards getting Axis2/C going.
Axis2 Java is nearly at a 1.0alpha and now we have a clean design of 
AXIOM, so we have started work on the C version.
In the Java front Axis2 effort ran in parallel with Axis 1.2 (and now 
1.3) efforts. Hence I believe that in C front also, Axis2 effort could 
run in parallel with 1.6 efforts.
We have started the effort by committing in some code on OM. You can 
checkout the c branch by using:

svn co https://svn.apache.org/repos/asf/webservices/axis2/trunk/c/
 

Re: [axis2] VOTE : *Description

[Samisa Abeysinghe]

What about the package name then? Are we going to retain "description"?
As the argument goes, as it is not meta data, "description" does not 
sound correct.


Tanks,
Samisa...

Glen Daniels wrote:

For the record, I continue to really dislike 
ServiceDescription/OperationDescription as class names for these 
things.  Consider Deepal's message below - the Service"Description" is 
the place you get the ClassLoader from!  It contains metadata, sure, 
but in a real way it IS the runtime representation of the service 
itself.  As such, I think these classes should be what we originally 
called them at the F2F:


AxisService
AxisOperation

This seems much more logical to me.  The AxisService, for instance, is 
the Java representation of everything Axis needs to know about this 
service at runtime - it's not just a "Description".


Also right now it's a little confusing in that AxisConfiguration is 
the corresponding class to ConfigurationContext, and all the others 
are *Description... it would be nice to have it consistent.


This was discussed before:

http://marc.theaimsgroup.com/?l=axis-dev&m=112666988223509&w=2

But I couldn't find an actual VOTE where we decided to make the change 
from AxisService -> ServiceDescription(can anyone point me to it?) 
so I'd like to have a VOTE for the record.  So here we go


PROPOSAL :

Make the hierarchy as follows:

s/ServiceDescription/AxisService/
s/OperationDescription/AxisOperation/
s/ServiceGroupDescription/AxisServiceGroup/

Here's my +1.

--Glen

Yves Langisch wrote:


Deepal,

Thanks, I'll give it a try.

Yves

On Tue, 2005-10-25 at 09:21 +0600, Deepal Jayasinghe wrote:


Hi Yvess;

The correct way is get the ServiceDescription from , MessageContxt 
and then you can get the correct classloader for that service (which 
has all you lib files) from serviceDescription

ClassLoader cl = sd.getClassLoader();

next you can load the properties you want.


Thanks,
Deepal

~Future is Open~

- Original Message - From: "Yves Langisch" <[EMAIL PROTECTED]>
To: 
Sent: Monday, October 24, 2005 7:42 PM
Subject: [Axis2] Access a resource inside of a Axis2 archive




Hi

I've a Axis2 archive file (.aar) which contains several libraries in
the /lib folder.  In my *PortSkeleton class I'm looking for a way to
load a properties file that is in one of this libs. I tried with
this.getClass().getResource("my.properties") (also with
"lib/my.properties") without success. How can I achieve this?

Thanks
Yves

Re: [AXIS2] Nominate Roy Wood and Dustin Amrhein to COMMITTER

[Samisa Abeysinghe]

+1.

Samisa...

Davanum Srinivas wrote:

+1

On 8/16/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote:
  

+1.

Thanks
Deepal


I would like to nominate Dustin Amrhein and Roy Wood to committer status.

Dustin is an active contributor to the metadata module.
Dustin proposed the MetaDataQuery functionality in June 2006 (AXIS2-872).
He has provided solutions to many deep issues including object
representation, annotation
validation, SWA attachment parameter support, classloading and
performance caching.
His contributions to the jaxws module include JAXWS executor work,
JAXWS marshalling fixes and async timeout work.
He has provided patches for 35 JIRA issues.

Roy has been an active contributor to Axis2 since September 2006.
He contributed the initial code for collecting annotation and
reflective class information (AXIS2-1195, etc)
This was the foundation of the metadata module.
Roy works closely with Jeff Barrett to maintain and improve the
metadata layer code.
Roy has contributed patches for a variety of issues in the jaxws
module, include changes that helped
us achieve JAX-WS CTS compliance with Geronimo.
Altogether Roy has contributed patches for 27 JIRA issues.

Thanks !
Rich Scheuerle
IBM Web Services
Apache Axis2 ([EMAIL PROTECTED])
512-838-5115 (IBM TL 678-5115)

  

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






  



--
Samisa Abeysinghe : WSO2 WSF/C
"http://wso2.org/projects/wsf/c?WSO2 Web Services Framework/C - Open source C library for providing and consuming Web services";


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

[Axis2] [ANN] Apache Axis2/C 1.1.0 Released

[Samisa Abeysinghe]

Apache Axis2/C Team is pleased to announce the release of Apache Axis2/C
version 1.1.0
You can download this release from:
   http://ws.apache.org/axis2/c/download.cgi

Key Features

  1. Support for one-way messaging (In-Only) and request response
messaging (In-Out)
  2. Client APIs: Easy to use service client API and more advanced
operation client API
  3. Transports supported: HTTP
 * Inbuilt HTTP server called simple axis server
 * Apache2 httpd module called mod_axis2 for server side
 * IIS module for server side
 * Client transport with ability to enable SSL support
 * Basic HTTP Authentication
 * libcurl based client transport
  4. Module architecture, mechanism to extend the SOAP processing model
  5. WS-Addressing support, both the submission (2004/08) and final
(2005/08) versions, implemented as a module
  6. MTOM/XOP support
  7. AXIOM, an XML object model optimized for SOAP 1.1/1.2 messages;
This has complete XML infoset support
  8. XML parser abstraction
 * Libxml2 wrapper
 * Guththila pull parser support
  9. Both directory based and archive based deployment models for
deploying services and modules
 10. Description hierarchy providing access to static data of Axis2/C
runtime
 (configuration, service groups, services, operations and messages)
 11. Context hierarchy providing access to dynamic Axis2/C runtime
information
 (corresponding contexts to map to each level of description hierarchy)
 12. Message receiver abstraction
 * Inbuilt raw XML message receiver
 13. Code generation tool for stub and skeleton generation for a given
WSDL
 (based on Java tool)
 * Axis Data Binding (ADB) support
 14. Transport proxy support
 15. REST support (more POX like) using both HTTP POST and GET
 16. Comprehensive documentation
 * Axis2/C Manual
 17. WS-Policy implementation called Neethi/C, with WS-SecurityPolicy
extension
 18. TCP Transport, for both client and server side

Major Changes Since Last Release

  1. WS-Policy implementation
  2. TCP Transport
  3. Improvements to Guththila parser to improve performance
  4. Improvements to Java tool, WSDL2C, that generates C code
  5. Basic HTTP Authentication
  6. Memory leak fixes
  7. Many bug fixes

We welcome your early feedback on this implementation.
Thank you for your interest in Axis2/C

-- Apache Axis2/C Team --




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

Re: JAX-WS code generation

[Samisa Abeysinghe]

Amila Suriarachchi wrote:

JAX-WS support was added to the wsdl2java tool as a Soc project. you
can generate
jax-ws code using  -l jaxws option
  

-l jaxws or -d jaxws?

Samisa...

--
Samisa Abeysinghe

http://people.apache.org/~samisa/


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

Re: Prioritized list of 1.4 things to do

[Samisa Abeysinghe]

Glen Daniels wrote:

Hi folks:

Deepal and I just did a quick prioritization pass on the list at [1]. 
Please take a look and see if it matches your view of the world.  We 
tried to be pretty simple about it, marking things on a three-level 
scale where 1 = critical, 2 = important, and 3 = nice to have.


Couple of quick things to note - 1) we didn't consider how easy/hard 
these things are; so some of the 3's are going to be 5-minute quick 
fixes which can get done any time.  2) some of the priorities are 
about making sure we finish discussion/design on things - so even if 
it's a (1) that doesn't necessarily mean we'll change any code, just 
that we MUST have the conversation soon.


What is the difference between
" (1) Review and improve build targets (docs, tests, dists)" vs.  " (2) 
Build cleanup". I thought they were the same or at least could have done 
in parallel.


Also, I thought documents should be (1) as well. Even though documents 
have improved a great deal over time, the flow of the documentation 
could be improved a great deal IMHO. And it is always good to do it 
sooner than later.



Thanks,
Samisa...


Thanks,
--G & D

[1] http://wiki.apache.org/ws/FrontPage/Axis2/post-1%2e3-plans

-
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: [VOTE] Sanjaya Karunasena as an Axis2 commiter

[Samisa Abeysinghe]

+1

Samisa...

robert lazarski wrote:

+1

Robert

On Nov 14, 2007 1:15 PM, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
  

+1

~Thilina


On Nov 14, 2007 12:28 PM, R J Scheuerle Jr <[EMAIL PROTECTED]> wrote:


+1

 Rich Scheuerle
 IBM Web Services
 Apache Axis2 ([EMAIL PROTECTED])
 512-838-5115 (IBM TL 678-5115)

 Damitha Kumarage <[EMAIL PROTECTED]> wrote on 11/14/2007 01:49:15 AM:



 > +1.
 > Damitha
 > Deepal Jayasinghe wrote:
 >
 > >Hi all,
 > >
 > >Sanjaya Karunasena has done enough work to become as a commiter , he has
 > >implemented fastinforset [FI] support in Axis2. And giving he commiter
 > >access will encourage him to contribute some more to the project and
 > >will make our job easier [no need to commit the patches].
 > >
 > >Here my +1 for Sanjaya as an Axis2 commiter.
 > >
 > >Thanks
 > >Deepal
 > >
 > >
 > >
 > >-
 > >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]
 >

  


--
Thilina Gunarathne  - http://thilinag.blogspot.com


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





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


  



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

Re: [AXIS2 1.1.1] OutOfMemoryError: Java heap space when engaging addressing on Stub

[Samisa Abeysinghe]

Fabrice Airault wrote:


hello,

I have a bug with my client (stub) when i use 
stub._getServiceClient().engageModule(new QName("addressing"));
After 2650 request i have "Exception in thread "main" 
java.lang.OutOfMemoryError: Java heap space"


If i don't use engageModule(new QName("addressing")); there is no 
problem.


You can find my code (stub is created with wsld2java) and
 Exception.


I am not sure what the exact problem is. However, is it possible for you 
to try the same with 1.3 release?


Samisa...


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

Re: [Axis2][VOTE] Axis2 1.4 FINAL

[Samisa Abeysinghe]

+1.
Samisa...

Deepal Jayasinghe wrote:

+1 indeed.

Thank you!
Deepal

Folks,

After all the excitement of the past few days :) We almost forgot the 
release


Please review:
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/

The m2 repository is here:
http://people.apache.org/~dims/axis2-1.4/FINAL/m2-repo/

SVN Info:
revision is 651268 on 
https://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_4


Here's my +1 to declaring the above dist as Axis2 1.4 FINAL.

Thanks,
dims

PS: Here are links to the individual Zip/Jar/Mar files:
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-bin.zip 

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-docs.zip 

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-src.zip 

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-war.zip 

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/modules/addressing/1_4/addressing-1.4.mar 

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/modules/soapmonitor/1_4/soapmonitor-1.4.mar 

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-aar-maven-plugin-1.4.jar 

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-ant-plugin-1.4.jar 

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-eclipse-codegen-wizard-1.4.zip 

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-eclipse-service-archiver-wizard-1.4.zip 

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-idea-plugin-1.4.zip 

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-java2wsdl-maven-plugin-1.4.jar 

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-mar-maven-plugin-1.4.jar 

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-wsdl2code-maven-plugin-1.4.jar 







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





--
Samisa Abeysinghe

http://people.apache.org/~samisa/


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

Re: [Axis2][VOTE] Axis2 1.4 FINAL - Take #2

[Samisa Abeysinghe]

Davanum Srinivas wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Quick Rev after an IM with Glen, updated the following zip's (svn 
revision - 651843)


axis2-1.4-bin.zip
axis2-1.4-src.zip
axis2-1.4-docs.zip
axis2-1.4-war.zip


I downloaded these form 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/. I 
could only unzip src zip, but not the other three. :(

Could you please double check these files.

Thanks,
Samisa...



- -- dims

Davanum Srinivas wrote:
| Folks,
|
| Firstly, Many thanks to Dan Kulp for reviewing the previous cut. I've
| moved the old directory away (to FINAL-TAKE1 under
| http://people.apache.org/~dims/axis2-1.4/) and placed the new files.
|
| So please review:
| http://people.apache.org/~dims/axis2-1.4/FINAL/dist/
|
| The m2 repository is here:
| http://people.apache.org/~dims/axis2-1.4/FINAL/m2-repo/
|
| SVN Info:
| revision is 651799 on
| https://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_4
|
| Here's my +1 to declaring the above dist as Axis2 1.4 FINAL.
|
| Thanks,
| dims
|
| PS: Here are links to the individual Zip/Jar/Mar files:
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-bin.zip 


|
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-docs.zip 


|
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-src.zip 


|
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-war.zip 


|
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/modules/addressing/1_4/addressing-1.4.mar 


|
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/modules/soapmonitor/1_4/soapmonitor-1.4.mar 


|
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-aar-maven-plugin-1.4.jar 


|
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-ant-plugin-1.4.jar 


|
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-eclipse-codegen-wizard-1.4.zip 


|
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-eclipse-service-archiver-wizard-1.4.zip 


|
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-idea-plugin-1.4.zip 


|
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-java2wsdl-maven-plugin-1.4.jar 


|
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-mar-maven-plugin-1.4.jar 


|
| 
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-wsdl2code-maven-plugin-1.4.jar 


|
|
| PPS: FYI, The Apache SVN is down for an outage/maintainenance. You can
| see the diffs on axis-cvs mailing list if you are
| curious.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)

iD8DBQFIE2rMgNg6eWEDv1kRAqzkAKDSL0+ix4r3iCx3+OGSbihuu8hfQgCZAbHD
slM8oKYC+fAzOnD3P9iDSh4=
=39st
-END PGP SIGNATURE-

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





--
Samisa Abeysinghe

http://people.apache.org/~samisa/


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

Re: [Axis2][VOTE] Axis2 1.4 FINAL - Take #2

[Samisa Abeysinghe]

I tested on bin pack on Windows. Here is my +1.

Samisa...

Ruwan Linton wrote:
+1 from me, tested with Synapse and seem to work fine. (tested the 
maven artifacts)


Thanks,
Ruwan

On Sun, Apr 27, 2008 at 4:16 PM, Davanum Srinivas <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

here are the file sizes

- -rw-rw-r--  1 dims  dims  20275257 Apr 27 10:17 axis2-1.4-bin.zip
- -rw-rw-r--  1 dims  dims  14223068 Apr 27 10:24 axis2-1.4-docs.zip
- -rw-rw-r--  1 dims  dims  12646856 Apr 27 10:31 axis2-1.4-src.zip
- -rw-rw-r--  1 dims  dims  22065939 Apr 27 10:43 axis2-1.4-war.zip



Samisa Abeysinghe wrote:
| Davanum Srinivas wrote:
| Quick Rev after an IM with Glen, updated the following zip's (svn
| revision - 651843)
|
| axis2-1.4-bin.zip
| axis2-1.4-src.zip
| axis2-1.4-docs.zip
| axis2-1.4-war.zip
|
|> I downloaded these form
|>
http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/
<http://people.apache.org/%7Edims/axis2-1.4/FINAL/dist/ws/axis2/1_4/>.
I
|> could only unzip src zip, but not the other three. :(
|> Could you please double check these files.
|
|> Thanks,
|> Samisa...
|
|
| -- dims
|
| Davanum Srinivas wrote:
| | Folks,
| |
| | Firstly, Many thanks to Dan Kulp for reviewing the previous
cut. I've
| | moved the old directory away (to FINAL-TAKE1 under
| | http://people.apache.org/~dims/axis2-1.4/
<http://people.apache.org/%7Edims/axis2-1.4/>) and placed the new
files.
| |
| | So please review:
| | http://people.apache.org/~dims/axis2-1.4/FINAL/dist/
<http://people.apache.org/%7Edims/axis2-1.4/FINAL/dist/>
| |
| | The m2 repository is here:
| | http://people.apache.org/~dims/axis2-1.4/FINAL/m2-repo/
<http://people.apache.org/%7Edims/axis2-1.4/FINAL/m2-repo/>
| |
| | SVN Info:
| | revision is 651799 on
| |
https://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_4
| |
| | Here's my +1 to declaring the above dist as Axis2 1.4 FINAL.
| |
| | Thanks,
| | dims
| |
| | PS: Here are links to the individual Zip/Jar/Mar files:
| |
|

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-bin.zip

<http://people.apache.org/%7Edims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-bin.zip>
|
| |
| |
|

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-docs.zip

<http://people.apache.org/%7Edims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-docs.zip>
|
| |
| |
|

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-src.zip

<http://people.apache.org/%7Edims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-src.zip>
|
| |
| |
|

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-war.zip

<http://people.apache.org/%7Edims/axis2-1.4/FINAL/dist/ws/axis2/1_4/axis2-1.4-war.zip>
|
| |
| |
|

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/modules/addressing/1_4/addressing-1.4.mar

<http://people.apache.org/%7Edims/axis2-1.4/FINAL/dist/ws/axis2/modules/addressing/1_4/addressing-1.4.mar>
|
| |
| |
|

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/modules/soapmonitor/1_4/soapmonitor-1.4.mar

<http://people.apache.org/%7Edims/axis2-1.4/FINAL/dist/ws/axis2/modules/soapmonitor/1_4/soapmonitor-1.4.mar>
|
| |
| |
|

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-aar-maven-plugin-1.4.jar

<http://people.apache.org/%7Edims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-aar-maven-plugin-1.4.jar>
|
| |
| |
|

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-ant-plugin-1.4.jar

<http://people.apache.org/%7Edims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-ant-plugin-1.4.jar>
|
| |
| |
|

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-eclipse-codegen-wizard-1.4.zip

<http://people.apache.org/%7Edims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-eclipse-codegen-wizard-1.4.zip>
|
| |
| |
|

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-eclipse-service-archiver-wizard-1.4.zip

<http://people.apache.org/%7Edims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-eclipse-service-archiver-wizard-1.4.zip>
|
| |
| |
|

http://people.apache.org/~dims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-idea-plugin-1.4.zip

<http://people.apache.org/%7Edims/axis2-1.4/FINAL/dist/ws/axis2/tools/1_4/axis2-idea-plugin-1.4.zip>
|
| |
  

Estimated Complexity field in Jira

[Samisa Abeysinghe]

I find that we have a field called "Estimated Complexity" in our Jira.
I propose that we use this field to mark issues to help people pick what
to fix based on their expertise. Specially helps with new contributions.
I find that the Harmony project is using this. The possible values are:

   * Unknown
   * Novice
   * Moderate
   * Advanced
   * Guru
   * Needs James Gosling


I know we traverse through Jiras before a release to pick what to be 
fixed. We may take a moment to mark this field as well.


Thoughts please...

Samisa...

--
Samisa Abeysinghe

http://people.apache.org/~samisa/

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

Re: AXIS2 1.4: Client problems when changing form plain XML to SOAP-style messages: Disallowed element found in envelope:Envelope..

[Samisa Abeysinghe]

Robert Ribnitz wrote:

Hello Sanjiva,

my basic porblem is the general lack of documentation; in the 
examples, there is a "SOAP with Attachments" example, but there is no 
example on how to use a plain SOAP message.


What about the echo sample? If you already have the SOAP envelope, all 
you have to do is to extract the body and return.


Samisa...


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

Re: [ANN] Apache Synapse ESB 1.2 released

[Samisa Abeysinghe]

Wouldn't  it be nice to mention that Synapse is based on Apache Axis2 in 
this release note?


Even the binary zip pack does not have a CREDITS file. :( I did not 
check the source pack.


Thanks,
Samisa...

Ruwan Linton wrote:

The Apache Synapse team is pleased to announce the release of
version 1.2 of the Open Source Enterprise Service Bus (ESB).

Apache Synapse is an lightweight and easy-to-use Open Source
Enterprise Service Bus (ESB) available under the Apache Software License
v2.0. Apache Synapse allows administrators to simply and easily configure
message routing, intermediation, transformation and logging task 
scheduling,

etc.. The runtime has been designed to be completely asynchronous,
non-blocking and streaming.

The Apache Synapse project and the 1.2 release can be found here:
  http://synapse.apache.org

Apache Synapse offers connectivity and integration with a range of
legacy systems, XML-based services and SOAP Web Services. It supports
non-blocking HTTP and HTTPS using the Apache HTTPCore 
(http://hc.apache.org)

components, as well as supporting JMS (v1.0 and higher) and a range of
file systems and FTP sources including SFTP, FTP, File, ZIP/JAR/TAR/GZ
via the Apache VFS project 
(http://commons.apache.org/vfs/filesystems.html).

At the same time Synapse 1.2 release adds the support for the Financial
Information eXchange (FIX) <http://www.fixprotocol.org/> an industry 
driven messaging standard through
QuickFixJ <http://www.quickfixj.org/>, Hessian binary web service 
protocol <http://hessian.caucho.com/>, as well as other functional,
stability and performance improvements. Synapse supports 
transformation and
routing between protocols without any coding via configurable virtual 
services.


Synapse provides first class support for standards such as WS-Addressing,
Web Services Security (WSS), Web Services Reliable Messaging (WSRM),
Throttling and caching, configurable via WS-Policy upto message level,
as well as efficient binary attachments (MTOM/XOP).

The 1.2 release contains a set of enhancements based on feedback from
the user community, including:

* Support for Hessian binary web service protocol
* FIX (Financial Information eXchange) protocol for messaging
* WS-Reliable Messaging support with WSO2 Mercury
  <http://wso2.org/projects/commons/mercury>
* Support for re-usable database connection pools for DB
  report/lookup mediators
* Support for GZip encoding and HTTP 100 continue
* Natural support for dual channel messaging with WS-Addressing
* Cluster aware sticky load balancing support
* Non-blocking streaming of large messages at high concurreny with
  constant memory usage
* Support for an ELSE clause for the Filter mediator
* Ability to specify XPath expressions relative to the envelope or
  body
* Support for separate policies for incoming/outgoing messages
* Support for a mandatory sequence before mediation


The combination of XML streaming and asynchronous support for HTTP and 
HTTPS

using Java NIO ensures that Synapse has very high scalability under load.
Performance tests show that Synapse can scale to support thousands of
concurrent connections with constant memory on standard server hardware.

Apache Synapse ships with over 50 samples
(http://synapse.apache.org/Synapse_Samples.html)
designed to demonstrate common integration patterns "out-of-the-box",
along with supporting sample services, and service clients that
demonstrate these scenarios. Apache Synapse is configured using a
straightforward XML configuration syntax
(http://synapse.apache.org/Synapse_Configuration_Language.html).

Apache Synapse is openly developed by a community that welcomes all
forms of input, ranging from suggestions and bug reports to patches and
code contributions. Your comments and feedback on the project and release
are welcomed.

The Apache Synapse code and binaries are available from the website
at http://synapse.apache.org

Thanks
The Apache Synapse Team

--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform" 



--
Samisa Abeysinghe

http://people.apache.org/~samisa/


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

[Axis2] Axis 2 Source drop

[Samisa Abeysinghe]

Hi Folks,
    Is there any way that I could get a source drop of Axis2 rather than through svn?
Thanks,
Samisa...
		Do you Yahoo!? 
The all-new My Yahoo! – What will yours do?

Deploy problems - please help

[Samisa Abeysinghe]

I get a SOAP fault when trying to deploy wsdd with AdminClient.

No clue why this is happening. I have the classes on my CLASSPATH. Appriciate 
any help.

Details below.

Thanks,
Samisa...

Processing file ca/deploy.wsdd
Exception: AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: java.lang.reflect.InvocationTargetException
 faultActor:
 faultNode:
 faultDetail:
{http://xml.apache.org/axis/}stackTrace:AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: java.lang.reflect.InvocationTargetException
 faultActor:
 faultNode:
 faultDetail:

java.lang.reflect.InvocationTargetException
at 
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:223)
at 
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:130)
at
org.apache.axis.encoding.DeserializationContextImpl.endElement(DeserializationContextImpl.java:1053)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown 
Source)
at 
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at
org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:218)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:568)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:427)
at 
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:701)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:93)
at 
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:144)
at org.apache.axis.client.Call.invokeEngine(Call.java:2688)
at org.apache.axis.client.Call.invoke(Call.java:2671)



__ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 

[jira] Created: (AXIS2-1165) Codegen tool does not understand -lc, but only -l c

[Samisa Abeysinghe (JIRA)]

Codegen tool does not understand -lc, but only -l c
---

 Key: AXIS2-1165
 URL: http://issues.apache.org/jira/browse/AXIS2-1165
 Project: Apache Axis 2.0 (Axis2)
  Issue Type: Improvement
Affects Versions: 1.0
Reporter: Samisa Abeysinghe
Priority: Minor


Would be nice to have support for -lc. In other words, drop the mandatory need 
for space between option and option arg. I mean the space could be there but 
even if the space is not there it should work

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Created: (AXIS2-1166) Document all options available to codegen tool

[Samisa Abeysinghe (JIRA)]

Document all options available to codegen tool
--

 Key: AXIS2-1166
 URL: http://issues.apache.org/jira/browse/AXIS2-1166
 Project: Apache Axis 2.0 (Axis2)
  Issue Type: Improvement
Affects Versions: 1.0
Reporter: Samisa Abeysinghe


If I run the codegen tool with -h option, the help message given does not show 
all the options/possibilities available. 
e.g. -f not shown; also C is not mentioned under -l

I think all options mentioned in CommandLineOptionConstants.WSDL2JavaConstants 
should be covered by usage message.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Created: (AXIS2-1812) Running ant in quickstart sample folder fails to deploy the sample

[Samisa Abeysinghe (JIRA)]

Running ant in quickstart sample folder fails to deploy the sample
--

 Key: AXIS2-1812
 URL: http://issues.apache.org/jira/browse/AXIS2-1812
 Project: Apache Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: samples
Affects Versions: 1.1
Reporter: Samisa Abeysinghe


The README.txt in samples/quickstart tells me that I should run "ant 
generate.service" or just "ant" in the folder to build the service.
But when I do so, I get an error.
BUILD FAILED
/home/samisa/downloads/axis2-1.1/samples/quickstart/build.xml:23: 
/home/samisa/downloads/axis2-1.1/samples/quickstart/${env.AXIS2_HOME}/lib not 
found.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Created: (AXIS2-1813) googlespellcheck sample fails to compile

[Samisa Abeysinghe (JIRA)]

googlespellcheck sample fails to compile


 Key: AXIS2-1813
 URL: http://issues.apache.org/jira/browse/AXIS2-1813
 Project: Apache Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: samples
Affects Versions: 1.1
Reporter: Samisa Abeysinghe


I ran ant in samples/googlespellcheck as the README.txt told me to.
However I got a compilation error:

samples/googlespellcheck]$ ant
Buildfile: build.xml

clean:
   [delete] DEPRECATED - Use of the implicit FileSet is deprecated.  Use a 
nested fileset element instead.

prepare:
[mkdir] Created dir: 
/home/samisa/downloads/axis2-1.1/samples/googlespellcheck/build
[mkdir] Created dir: 
/home/samisa/downloads/axis2-1.1/samples/googlespellcheck/build/classes
[mkdir] Created dir: 
/home/samisa/downloads/axis2-1.1/samples/googlespellcheck/build/lib

run.client:

client.codegen-stub:
 [java] org.apache.axis2.wsdl.codegen.CodeGenerationException: Error 
parsing WSDL
 [java] at 
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:180)
 [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:710)
 [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178)
 [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84)
 [java] at 
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
 [java] at org.apache.tools.ant.Task.perform(Task.java:364)
 [java] at org.apache.tools.ant.Target.execute(Target.java:341)
 [java] at org.apache.tools.ant.Target.performTasks(Target.java:369)
 [java] at 
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
 [java] at 
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
 [java] at 
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
 [java] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
 [java] at 
org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)
 [java] at 
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
 [java] at org.apache.tools.ant.Task.perform(Task.java:364)
 [java] at org.apache.tools.ant.Target.execute(Target.java:341)
 [java] at org.apache.tools.ant.Target.performTasks(Target.java:369)
 [java] at 
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
 [java] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
 [java] at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
 [java] at 
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
 [java] at org.apache.tools.ant.Main.runBuild(Main.java:668)
 [java] at org.apache.tools.ant.Main.startAnt(Main.java:187)
 [java] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
 [java] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
 [java] Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: 
Error parsing WSDL
 [java] at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:114)
 [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
 [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
 [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 [java] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 [java] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 [java] at java.lang.reflect.Method.invoke(Method.java:585)
 [java] at 
org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:202)
 [java] at 
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:134)
 [java] ... 24 more
 [java] Caused by: javax.wsdl.WSDLException: WSDLException: 
faultCode=INVALID_WSDL: IO Error: java.net.ConnectException: Connection refused
 [java] at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(CodeGenerationEngine.java:273)
 [java] at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:97)
 [java] ... 32 more
 [java] Caused by: java.net.ConnectException: Connection refused
 [java] at java.net.PlainSocketImpl.socketConnect(Native Method)
 [java] at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 [java] at 
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 [java] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 [java] at java.net.Socket.connect(Socket.java:507)
 [java] at java.net.Socket.connect(Socket.java:457)
 [java] at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
 [java] at

[jira] Commented: (AXIS2-1812) Running ant in quickstart sample folder fails to deploy the sample

[Samisa Abeysinghe (JIRA)]

[ 
http://issues.apache.org/jira/browse/AXIS2-1812?page=comments#action_12455170 ] 

Samisa Abeysinghe commented on AXIS2-1812:
--

Running "ant generate.service"  in the following folders give the same error:
quickstartadb
quickstartaxiom
quickstartjibx
quickstartxmlbeans

> Running ant in quickstart sample folder fails to deploy the sample
> --
>
> Key: AXIS2-1812
> URL: http://issues.apache.org/jira/browse/AXIS2-1812
> Project: Apache Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: samples
>Affects Versions: 1.1
>Reporter: Samisa Abeysinghe
>
> The README.txt in samples/quickstart tells me that I should run "ant 
> generate.service" or just "ant" in the folder to build the service.
> But when I do so, I get an error.
> BUILD FAILED
> /home/samisa/downloads/axis2-1.1/samples/quickstart/build.xml:23: 
> /home/samisa/downloads/axis2-1.1/samples/quickstart/${env.AXIS2_HOME}/lib not 
> found.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Created: (AXIS2-1814) doc/servicelifecycleguide.html mentioned in samples/servicelifecycle/README.txt is missing

[Samisa Abeysinghe (JIRA)]

doc/servicelifecycleguide.html mentioned in samples/servicelifecycle/README.txt 
is missing
--

 Key: AXIS2-1814
 URL: http://issues.apache.org/jira/browse/AXIS2-1814
 Project: Apache Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: samples
Affects Versions: 1.1
Reporter: Samisa Abeysinghe


The samples/servicelifecycle/README.txt file mentions a 
doc/servicelifecycleguide.html document. This is nither in the binary 
distribution nor in the seperate document download. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Created: (AXIS2-1815) Exception when trying userguide samples

[Samisa Abeysinghe (JIRA)]

Exception when trying userguide samples
---

 Key: AXIS2-1815
 URL: http://issues.apache.org/jira/browse/AXIS2-1815
 Project: Apache Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: samples
Affects Versions: 1.1
Reporter: Samisa Abeysinghe


I tried to deploy services in the userguide folder of samples.
Here are the steps that I followed.
1. Extract axis2 1.1 binary zip download
2. cd to samples/userguide
3. run ant
4. cd to bin
5. run axis2server.sh

Then I get the following exception. This is a very simple user scenarion for 
binary distribution and one would not expect an exception here. 

Exception:

INFO: Deploying Web service  sample-WsaMappingService.aar
org.apache.axis2.deployment.DeploymentException: Processing Operations Modules 
logging module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: Processing Operations 
Modules logging module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed
at 
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:139)
at 
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:528)
at 
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:196)
at 
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:227)
at 
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:174)
at 
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:88)
at 
org.apache.axis2.deployment.FileSystemConfigurator.loadServices(FileSystemConfigurator.java:129)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:72)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:180)
at 
org.apache.axis2.transport.SimpleAxis2Server.main(SimpleAxis2Server.java:86)
Caused by: org.apache.axis2.deployment.DeploymentException: Processing 
Operations Modules logging module is invalid or has not been deployed; nested 
exception is:
org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed
at 
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:329)
at 
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:91)
at 
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:133)
... 9 more
Caused by: org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed
at 
org.apache.axis2.deployment.ServiceBuilder.processModuleRefs(ServiceBuilder.java:496)
at 
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:250)
... 11 more
Caused by: org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed
at 
org.apache.axis2.deployment.ServiceBuilder.processModuleRefs(ServiceBuilder.java:488)
... 12 more
Dec 3, 2006 10:39:23 PM org.apache.axis2.deployment.DeploymentEngine doDeploy
SEVERE: Invalid service  sample-MyServiceWithModule.aar due to Processing 
Operations Modules logging module is invalid or has not been deployed; nested 
exception is:
org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging module is 
invalid or has not been deployed; nested exception is

[jira] Commented: (AXIS2-487) XMLBeans truncates dateTime values

[Samisa Abeysinghe (JIRA)]

[ 
http://issues.apache.org/jira/browse/AXIS2-487?page=comments#action_12369853 ] 

Samisa Abeysinghe commented on AXIS2-487:
-

.NET clients aparently send Date Time values with 7 digit millisecond values, 
but Axis2 replies with the millisecond value trucated to 3 digits

> XMLBeans truncates dateTime values
> --
>
>  Key: AXIS2-487
>  URL: http://issues.apache.org/jira/browse/AXIS2-487
>  Project: Apache Axis 2.0 (Axis2)
> Type: Bug
>   Components: databinding
> Reporter: Ajith Harshana Ranabahu
> Assignee: Ajith Harshana Ranabahu

>
> XMLbeans seems to handle the datetimes by truncating the last part of the 
> datetime value and hence effectively the data value is changed!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (AXIS2-486) Axis2 Client does not validate the content type of incoming messages

[Samisa Abeysinghe (JIRA)]

[ 
http://issues.apache.org/jira/browse/AXIS2-486?page=comments#action_12369854 ] 

Samisa Abeysinghe commented on AXIS2-486:
-

Axis2 C server response did not contain Content-Type, but the Java clients 
could understand the response irrespective of content type.
However, going by the HTTP spec, there should be some validation based on 
Content-Type.

> Axis2 Client does not validate the content type of incoming messages
> 
>
>  Key: AXIS2-486
>  URL: http://issues.apache.org/jira/browse/AXIS2-486
>  Project: Apache Axis 2.0 (Axis2)
> Type: Bug
>   Components: transports
> Reporter: Thilina Gunarathne

>
> Axis 2 client does not validate the content type of the incoming messages.. 
> It accepted messages without any content type

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Created: (AXIS2-612) MTOM sample server side does not send a fault on error

[Samisa Abeysinghe (JIRA)]

MTOM sample server side does not send a fault on error
--

 Key: AXIS2-612
 URL: http://issues.apache.org/jira/browse/AXIS2-612
 Project: Apache Axis 2.0 (Axis2)
Type: Bug

  Components: samples, build,site  & docs  
Reporter: Samisa Abeysinghe


I am using 1.0 RC2.

I am tyring to get the Axis2/C implementation of MTOM to work with Axis2/Java.
When I send a message with errors, the Java server does not tell me anthing on 
what went wrong.
 It would be helpful if it were to send me a fault. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Created: (AXIS2-615) Binary std release should have buld system for sample sources

[Samisa Abeysinghe (JIRA)]

Binary std release should have buld system for sample sources
-

 Key: AXIS2-615
 URL: http://issues.apache.org/jira/browse/AXIS2-615
 Project: Apache Axis 2.0 (Axis2)
Type: Bug

  Components: samples, build,site  & docs  
Reporter: Samisa Abeysinghe


I am using 1.0 RC2, and I want to play around with the MTOM sample.
However I havent got the build system for sample sources.

It would be great if we could have some ant based build system for samples



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Created: (AXIS2-202) WSDL2Java gives an error if -o paramater is missing

[Samisa Abeysinghe (JIRA)]

WSDL2Java gives an error if -o paramater is missing
---

 Key: AXIS2-202
 URL: http://issues.apache.org/jira/browse/AXIS2-202
 Project: Apache Axis 2.0 (Axis2)
Type: Bug
  Components: wsdl  
Versions: 0.91
 Environment: Windows XP
Reporter: Samisa Abeysinghe


If I run the tool witout -o it gives me the following error:

E:\wsdls>java org.apache.axis2.wsdl.WSDL2Java -uri InteropTest.wsdl
Exception in thread "main" java.lang.RuntimeException: Cannot codegenerate! 
WSDL file is missing!
at 
org.apache.axis2.wsdl.codegen.CodeGenConfiguration.(CodeGenConfiguration.java:81)
at 
org.apache.axis2.wsdl.codegen.CodeGenConfiguration.(CodeGenConfiguration.java:71)
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:56)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:29)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:23)

But if I run 

java org.apache.axis2.wsdl.WSDL2Java -o test -uri InteropTest.wsdl it runs

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Created: (AXIS2-228) java.io.IOException: No such file or directory if folder pointed by -o option is missing

[Samisa Abeysinghe (JIRA)]

java.io.IOException: No such file or directory if folder pointed by -o option 
is missing


 Key: AXIS2-228
 URL: http://issues.apache.org/jira/browse/AXIS2-228
 Project: Apache Axis 2.0 (Axis2)
Type: Bug
  Components: wsdl  
Versions: 0.92
Reporter: Samisa Abeysinghe


I used the following command:
java -cp 
../axis2/java/target/lib/axis2-0.92.jar:../axis2/java/target/lib/axis-wsdl4j-1.2.jar:../axis2/java/target/lib/stax-api-1.0.jar:../axis2/java/target/lib/commons-logging-1.0.3.jar:../axis2/java/target/lib/log4j-1.2.8.jar:../axis2/java/target/lib/xbean-2.0.0-beta1.jar
 org.apache.axis2.wsdl.WSDL2Code -uri 
../axiscpp/ws-axis/c/c/deploy/wsdls/bench.wsdl -o out -d 0

and got the following error:

Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: 
org.apache.axis2.wsdl.codegen.CodeGenerationException: java.io.IOException: No 
such file or directory
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:104)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:30)
Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: 
java.io.IOException: No such file or directory
at 
org.apache.axis2.wsdl.codegen.emitter.MultiLanguageClientEmitter.emitStub(MultiLanguageClientEmitter.java:161)
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:97)
... 1 more
Caused by: java.io.IOException: No such file or directory
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:850)
at 
org.apache.axis2.wsdl.util.FileWriter.createClassFile(FileWriter.java:64)
at 
org.apache.axis2.wsdl.codegen.writer.ClassWriter.createOutFile(ClassWriter.java:109)
at 
org.apache.axis2.wsdl.codegen.emitter.MultiLanguageClientEmitter.writeClass(MultiLanguageClientEmitter.java:503)
at 
org.apache.axis2.wsdl.codegen.emitter.MultiLanguageClientEmitter.writeInterface(MultiLanguageClientEmitter.java:379)
at 
org.apache.axis2.wsdl.codegen.emitter.MultiLanguageClientEmitter.emitStubBinding(MultiLanguageClientEmitter.java:278)
at 
org.apache.axis2.wsdl.codegen.emitter.MultiLanguageClientEmitter.emitStubAutomatic(MultiLanguageClientEmitter.java:307)
at 
org.apache.axis2.wsdl.codegen.emitter.MultiLanguageClientEmitter.emitStub(MultiLanguageClientEmitter.java:155)
... 2 more


Wen I create the out folder manually and run, then it works

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Created: (AXIS2-229) When using -d 0 option (that is codegen with no data binding), it has no meaning to generate databinding code

[Samisa Abeysinghe (JIRA)]

When using -d 0 option (that is codegen with no data binding), it has no 
meaning to generate databinding code
-

 Key: AXIS2-229
 URL: http://issues.apache.org/jira/browse/AXIS2-229
 Project: Apache Axis 2.0 (Axis2)
Type: Improvement
  Components: wsdl  
Versions: 0.92
Reporter: Samisa Abeysinghe
Priority: Minor


With -d 0 option (that is no data binding) I see that some code is generated in 
the databinding subdolder.

I get some code similar to :
public  static org.apache.axis2.om.OMElement  
toOM(org.apache.axis2.om.OMElement param){
//Just return the object as it is. it's supposed to be an OMElement
return param;
  }

public static org.apache.axis2.om.OMElement 
fromOM(org.apache.axis2.om.OMElement param,
   java.lang.Class type){
   //Just return the OMElement as it is
   return param;
  }

What is the use of having this param echo code here?


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Created: (AXIS2-230) I wish the codegen tool generated code was indented nicely

[Samisa Abeysinghe (JIRA)]

I wish the codegen tool generated code was indented nicely
--

 Key: AXIS2-230
 URL: http://issues.apache.org/jira/browse/AXIS2-230
 Project: Apache Axis 2.0 (Axis2)
Type: Wish
  Components: wsdl  
Versions: 0.92
Reporter: Samisa Abeysinghe
Priority: Trivial


I wish the codegen tool generated code was indented nicely so that it improves 
redability and understandability of the generated code.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (AXIS2-230) I wish the codegen tool generated code was indented nicely

[Samisa Abeysinghe (JIRA)]

[ 
http://issues.apache.org/jira/browse/AXIS2-230?page=comments#action_12329950 ] 

Samisa Abeysinghe commented on AXIS2-230:
-

If it is more jars, then better drop the idea ;-)

> I wish the codegen tool generated code was indented nicely
> --
>
>  Key: AXIS2-230
>  URL: http://issues.apache.org/jira/browse/AXIS2-230
>  Project: Apache Axis 2.0 (Axis2)
> Type: Wish
>   Components: wsdl
> Versions: 0.92
>     Reporter: Samisa Abeysinghe
> Priority: Trivial

>
> I wish the codegen tool generated code was indented nicely so that it 
> improves redability and understandability of the generated code.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (AXIS2-3342) WSDL2C.bat and WSDL2C.sh should be bundled with Axis2/Java

[Samisa Abeysinghe (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557166#action_12557166
 ] 

Samisa Abeysinghe commented on AXIS2-3342:
--

+1.



> WSDL2C.bat and WSDL2C.sh should be bundled with Axis2/Java
> --
>
> Key: AXIS2-3342
> URL: https://issues.apache.org/jira/browse/AXIS2-3342
> Project: Axis 2.0 (Axis2)
>  Issue Type: Wish
> Environment: Windows and UNIX
>Reporter: Michael Mole
>Priority: Minor
>
> The WSDL2Java code generation tool includes a set of .bat and .sh files for 
> using the tool.  However the equivalent WSDL2C.bat and WSDL2C.sh are not 
> bundled with Axis2Java.  I keep my own local copies and have to copy them 
> into the Axis2Java bin directory every time I download a new Axis2Java 
> version.  It would be nice if they were included.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (AXIS2-3813) Axis2 1.2 service does not understand soapenv:mustUnderstand

[Samisa Abeysinghe (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599680#action_12599680
 ] 

Samisa Abeysinghe commented on AXIS2-3813:
--

Have you tested this with the latest release?

> Axis2 1.2 service does not understand soapenv:mustUnderstand
> 
>
> Key: AXIS2-3813
> URL: https://issues.apache.org/jira/browse/AXIS2-3813
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
> Environment: Axis2 1.2 Windows XP Axis2 service deployed on WebSphere 
> Application Server v 6.1.0.15
>Reporter: Abhay
>
> When the soap request contains soapenv:mustUnderstand="1" (which means web 
> service is bound to read the security attribute) then Axis2 service fails to 
> read the security attribute. I have also found something interesting going on 
> here when I pass the SOAP request with soapenv:MustUnderstand="1" then AXIS2 
> service is able to read the message properly. The only difference between two 
> calls is the use of 'm'  or 'M'  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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