You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Deepal Jayasinghe <de...@opensource.lk> on 2007/03/20 11:38:16 UTC

[Axis2] Axis2 1.2 release prograss

Hi All;

As I mentioned in [1] most of the features are in complete state (of
course some of them as experimental features) so we are ready to go
ahead with 1.2 release :) . The status of the feature items are listed
below and there are few items that I would like to see the status
(specially JAX-WS ) , so please update the list on their progress.

About the release I would like to release Axis2 1.2 RC1 on this Friday
(24^th March) and do the testing , depending on the JIRAs and other
issue will decide whether we need some other RC or not. And release
Axis2 1.2 on April first week (if every thing went well).

- WSDL 2.0 fully support – DONE
(Reading , writing and codegen)

- POJO – annotation – DONE 
  (Almost complete but need more testing)
- REST Annotation 
  (I forget this item , what do we need to do here , is that some kind of custom annotation for REST ?)
- JAX-WS integration
 (Please update the list )
- JAX-WS -annotation
 (I hope we do have JAX-WS annotation support , any way please update the list)
- Un-wrapping (Response) - DONE
- ADB - missing schema support - DONE
- Move security and Sawan module from Axis2 trunk -DONE
- Maven2 support – Almost done (dims are we in good position on mvn2)
- JASON support - DONE
- Binary serialization – almost done
- Geronimo Integration 
 (Lasantha pls update the list )
- Jax-ws option for code gen (Jaxbri as the db) – Wont implement
- Custom File cache mechanism – Thilina ?
- Multiple services support in code gen (WSDL with multiple services) -DONE
- HTTP code generation (both WSDL 1.1 and 2.0) -DONE
- i18n support – Won't implement
- Fix/update helper mode - DONE

In addition to above major features we have fixed numerous JIRA issues
and have added new features as well (Custom deployers , Message
formatters , Builders etc etc.)

How abt JAX-WS release , is that going to follow a separate release
cycle or will that be release with Axis2 ?

So what do you think about the release plan , is that ok if I go ahead
with that and do the RC1 end of this week :)

[1] - http://marc.info/?l=axis-user&m=116900551522771&w=2

Thanks
Deepal



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Re: [Axis2] Axis2 1.2 release prograss

Posted by Amila Suriarachchi <am...@gmail.com>.
On 3/20/07, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
>
> Deepal Jayasinghe wrote:
> >
> > - WSDL 2.0 fully support – DONE
> > (Reading , writing and codegen)
>
> Do we have ?wsdl2 support also? If not that needs to be on the list.
>
> > - REST Annotation
> >   (I forget this item , what do we need to do here , is that some kind
> of custom annotation for REST ?)
>
> Basically we need a way for the developer to tell us what HTTP operation
> to support for each Java method. Furthermore, some hints on the URL path
> etc.- basically everything that's possible in the WSDL 2.0 binding. Keith,
> maybe we can work out a set of annotations to map into WSDL 2.0? Then
> it'll be easy to impl; just map them to the corresponding WSDL 2.0 HTTP
> binding properties and everything else will "just work" ;-).
>
> > - Un-wrapping (Response) - DONE
> > - ADB - missing schema support - DONE
>
> What about the nice names for parameters instead of param69 etc.? I think
> that's a blocker for 1.2!


it is done

> So what do you think about the release plan , is that ok if I go ahead
> > with that and do the RC1 end of this week :)
>
> +1!
>
> Sanjiva.
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Director; Open Source Initiative; http://www.opensource.org/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] Axis2 1.2 release prograss

Posted by keith chapman <ke...@gmail.com>.
Hi Chinthaka,

I have fixed AxisService2WSDL2 (almost rewrote it). Its working now. The
only problem we will have is, if the user asks for the original WSDL. The
WSDL generated from the axisService is an approximate (woden returns some
default values for the parameters when there is no value specified) of the
original WSDL. so ?wsdl2 works now.

Thanks,
Keith

On 3/22/07, Eran Chinthaka <ch...@opensource.lk> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sanjiva Weerawarana wrote:
> > Deepal Jayasinghe wrote:
> >>
> >> - WSDL 2.0 fully support – DONE
> >> (Reading , writing and codegen)
> >
> > Do we have ?wsdl2 support also? If not that needs to be on the list.
>
> I don't think we can do ?wsdl for WSDL 2.0, as Woden hasn't got a
> serializer yet (I am trying to get a student to work on it as a Google
> SoC project).
> But we can show if user had put a wsdl in to the service archive.
> Please do not suggest to use the AxisService2OM, as it was buggy. I hope
> it is better to have nothing, rather than showing a wrong one.
>
>
> Thanks,
> Chinthaka
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGAfs/jON2uBzUhh8RAuGrAJ9In04JW0czruPUP+HPYTfAdXXlfQCdEzYZ
> IG05+UKhH5qD+uk7kUiQLJQ=
> =U5x8
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


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

Re: [Axis2] Axis2 1.2 release prograss

Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sanjiva Weerawarana wrote:
> Deepal Jayasinghe wrote:
>>
>> - WSDL 2.0 fully support – DONE
>> (Reading , writing and codegen)
> 
> Do we have ?wsdl2 support also? If not that needs to be on the list.

I don't think we can do ?wsdl for WSDL 2.0, as Woden hasn't got a
serializer yet (I am trying to get a student to work on it as a Google
SoC project).
But we can show if user had put a wsdl in to the service archive.
Please do not suggest to use the AxisService2OM, as it was buggy. I hope
it is better to have nothing, rather than showing a wrong one.


Thanks,
Chinthaka
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGAfs/jON2uBzUhh8RAuGrAJ9In04JW0czruPUP+HPYTfAdXXlfQCdEzYZ
IG05+UKhH5qD+uk7kUiQLJQ=
=U5x8
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Re: [Axis2] Axis2 1.2 release prograss

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Deepal Jayasinghe wrote:
> 
> - WSDL 2.0 fully support – DONE
> (Reading , writing and codegen)

Do we have ?wsdl2 support also? If not that needs to be on the list.

> - REST Annotation 
>   (I forget this item , what do we need to do here , is that some kind of custom annotation for REST ?)

Basically we need a way for the developer to tell us what HTTP operation 
to support for each Java method. Furthermore, some hints on the URL path 
etc.- basically everything that's possible in the WSDL 2.0 binding. Keith, 
maybe we can work out a set of annotations to map into WSDL 2.0? Then 
it'll be easy to impl; just map them to the corresponding WSDL 2.0 HTTP 
binding properties and everything else will "just work" ;-).

> - Un-wrapping (Response) - DONE
> - ADB - missing schema support - DONE

What about the nice names for parameters instead of param69 etc.? I think 
that's a blocker for 1.2!

> So what do you think about the release plan , is that ok if I go ahead
> with that and do the RC1 end of this week :)

+1!

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

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Re: [Axis2] Axis2 1.2 release prograss

Posted by Thilina Gunarathne <cs...@gmail.com>.
> - Custom File cache mechanism – Thilina ?
Will not be implemented for the 1.2..
> - Multiple services support in code gen (WSDL with multiple services) -DONE
> - HTTP code generation (both WSDL 1.1 and 2.0) -DONE
> - i18n support – Won't implement
AFAIK we already have some support for this.. What is the thing which
we are not going to  implement  :)
> - Fix/update helper mode - DONE
>
> In addition to above major features we have fixed numerous JIRA issues
> and have added new features as well (Custom deployers , Message
> formatters , Builders etc etc.)
>
> So what do you think about the release plan
+1 for the plan..

We might also need to decide the list of maven module that we are
going to release this time and the list of things which we are going
to include in the axis2-1.2.jar.. Also we might need to decide the set
of libraries that will go the axis2-dist-bin...

Are we planning to cut a branch for this release.. From my past
experience 1.1 branch helped us lot to get to the 1.1.1 release...

thanks,
-- 
Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [Axis2] Axis2 1.2 release prograss

Posted by Thilina Gunarathne <cs...@gmail.com>.
> - Custom File cache mechanism – Thilina ?
Will not be implemented for the 1.2..
> - Multiple services support in code gen (WSDL with multiple services) -DONE
> - HTTP code generation (both WSDL 1.1 and 2.0) -DONE
> - i18n support – Won't implement
AFAIK we already have some support for this.. What is the thing which
we are not going to  implement  :)
> - Fix/update helper mode - DONE
>
> In addition to above major features we have fixed numerous JIRA issues
> and have added new features as well (Custom deployers , Message
> formatters , Builders etc etc.)
>
> So what do you think about the release plan
+1 for the plan..

We might also need to decide the list of maven module that we are
going to release this time and the list of things which we are going
to include in the axis2-1.2.jar.. Also we might need to decide the set
of libraries that will go the axis2-dist-bin...

Are we planning to cut a branch for this release.. From my past
experience 1.1 branch helped us lot to get to the 1.1.1 release...

thanks,
-- 
Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Re: [Axis2] Axis2 1.2 release prograss

Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
On Tue, 2007-03-20 at 11:05 +0000, Michele Mazzucco wrote:
> I think first of all you need to fix the script which creates nightly
> builds, which is broken. 

I've also tried to build axis2 from the svn, but the process fails (see
below)

1961 [main] ERROR org.apache.axis2.deployment.ServiceDeployer  - The
SendImageService service, which is not valid, caused Processing
Operations Modules with an error of The following error occurred during
schema generation: prefix cannot be "null" when creating a QName; nested
exception is:
    [junit]     java.lang.IllegalArgumentException: prefix cannot be
"null" when creating a QName; nested exception is:
    [junit]     org.apache.axis2.deployment.DeploymentException: The
following error occurred during schema generation: prefix cannot be
"null" when creating a QName; nested exception is:
    [junit]     java.lang.IllegalArgumentException: prefix cannot be
"null" when creating a QName; nested exception is:
    [junit]     org.apache.axis2.deployment.DeploymentException:
Processing Operations Modules with an error of The following error
occurred during schema generation: prefix cannot be "null" when creating
a QName; nested exception is:
    [junit]     java.lang.IllegalArgumentException: prefix cannot be
"null" when creating a QName; nested exception is:
    [junit]     org.apache.axis2.deployment.DeploymentException: The
following error occurred during schema generation: prefix cannot be
"null" when creating a QName; nested exception is:
    [junit]     java.lang.IllegalArgumentException: prefix cannot be
"null" when creating a QName
    [junit] org.apache.axis2.deployment.DeploymentException: Processing
Operations Modules with an error of The following error occurred during
schema generation: prefix cannot be "null" when creating a QName; nested
exception is:
    [junit]     java.lang.IllegalArgumentException: prefix cannot be
"null" when creating a QName; nested exception is:
    [junit]     org.apache.axis2.deployment.DeploymentException: The
following error occurred during schema generation: prefix cannot be
"null" when creating a QName; nested exception is:
    [junit]     java.lang.IllegalArgumentException: prefix cannot be
"null" when creating a QName; nested exception is:
    [junit]     org.apache.axis2.deployment.DeploymentException:
Processing Operations Modules with an error of The following error
occurred during schema generation: prefix cannot be "null" when creating
a QName; nested exception is:
    [junit]     java.lang.IllegalArgumentException: prefix cannot be
"null" when creating a QName; nested exception is:
    [junit]     org.apache.axis2.deployment.DeploymentException: The
following error occurred during schema generation: prefix cannot be
"null" when creating a QName; nested exception is:
    [junit]     java.lang.IllegalArgumentException: prefix cannot be
"null" when creating a QName
    [junit]     at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:103)
    [junit]     at
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:104)
    [junit]     at
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:173)
    [junit]     at
org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:76)
    [junit]     at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:561)
    [junit]     at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:202)
    [junit]     at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:286)
    [junit]     at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:191)
    [junit]     at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:109)
    [junit]     at
org.apache.axis2.deployment.FileSystemConfigurator.loadServices(FileSystemConfigurator.java:127)
    [junit]     at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:78)
    [junit]     at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:187)
    [junit]     at
org.apache.axis2.jaxws.utility.SimpleServer.init(SimpleServer.java:43)
    [junit]     at
org.apache.axis2.jaxws.utility.SimpleServer.start(SimpleServer.java:53)
    [junit]     at
org.apache.axis2.jaxws.framework.StartServer.testStartServer(StartServer.java:31)
    [junit]     at org.apache.axis2.jaxws.framework.JAXWSTest
$1.setUp(JAXWSTest.java:183)
    [junit]     at junit.extensions.TestSetup
$1.protect(TestSetup.java:20)
    [junit]     at
junit.framework.TestResult.runProtected(TestResult.java:124)
    [junit]     at junit.extensions.TestSetup.run(TestSetup.java:25)
    [junit]     at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:325)
    [junit]     at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:536)
    [junit] Caused by: org.apache.axis2.deployment.DeploymentException:
Processing Operations Modules with an error of The following error
occurred during schema generation: prefix cannot be "null" when creating
a QName; nested exception is:
    [junit]     java.lang.IllegalArgumentException: prefix cannot be
"null" when creating a QName; nested exception is:
    [junit]     org.apache.axis2.deployment.DeploymentException: The
following error occurred during schema generation: prefix cannot be
"null" when creating a QName; nested exception is:
    [junit]     java.lang.IllegalArgumentException: prefix cannot be
"null" when creating a QName
    [junit]     at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:362)
    [junit]     at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:98)
    [junit]     ... 20 more
    [junit] Caused by: org.apache.axis2.deployment.DeploymentException:
The following error occurred during schema generation: prefix cannot be
"null" when creating a QName; nested exception is:
    [junit]     java.lang.IllegalArgumentException: prefix cannot be
"null" when creating a QName
    [junit]     at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:327)
    [junit]     ... 21 more
    [junit] Caused by: java.lang.IllegalArgumentException: prefix cannot
be "null" when creating a QName
    [junit]     at javax.xml.namespace.QName.<init>(QName.java:220)
    [junit]     at
org.apache.ws.java2wsdl.SchemaGenerator.generateSchema(SchemaGenerator.java:318)
    [junit]     at
org.apache.ws.java2wsdl.SchemaGenerator.generateSchemaforFieldsandProperties(SchemaGenerator.java:471)
    [junit]     at
org.apache.ws.java2wsdl.SchemaGenerator.generateSchema(SchemaGenerator.java:370)
    [junit]     at
org.apache.ws.java2wsdl.SchemaGenerator.generateSchemaforFieldsandProperties(SchemaGenerator.java:471)
    [junit]     at
org.apache.ws.java2wsdl.SchemaGenerator.generateSchema(SchemaGenerator.java:370)
    [junit]     at
org.apache.ws.java2wsdl.SchemaGenerator.generateSchemaforFieldsandProperties(SchemaGenerator.java:471)
    [junit]     at
org.apache.ws.java2wsdl.SchemaGenerator.generateSchema(SchemaGenerator.java:370)
    [junit]     at
org.apache.ws.java2wsdl.SchemaGenerator.generateSchemaforFieldsandProperties(SchemaGenerator.java:471)
    [junit]     at
org.apache.ws.java2wsdl.SchemaGenerator.generateSchema(SchemaGenerator.java:370)
    [junit]     at
org.apache.ws.java2wsdl.SchemaGenerator.generateSchemaForType(SchemaGenerator.java:522)
    [junit]     at
org.apache.ws.java2wsdl.SchemaGenerator.generateSchema(SchemaGenerator.java:230)
    [junit]     at
org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:332)
    [junit]     at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:320)
    [junit]     ... 21 more
    [junit] 2007-03-20 12:52:03,774 INFO
org.apache.axis2.transport.http.server.DefaultConnectionListener -
Listening on port 8080
    [junit] 2089 [HttpListener-8080-1] INFO
org.apache.axis2.transport.http.server.DefaultConnectionListener  -
Listening on port 8080
    [junit] 2007-03-20 12:52:04,783 INFO
org.apache.axis2.transport.http.server.SimpleHttpServer - Shut down
connection listener
    [junit] 3098 [main] INFO
org.apache.axis2.transport.http.server.SimpleHttpServer  - Shut down
connection listener
    [junit] 2007-03-20 12:52:04,788 INFO
org.apache.axis2.transport.http.server.SimpleHttpServer - Shut down HTTP
processors
    [junit] 3103 [main] INFO
org.apache.axis2.transport.http.server.SimpleHttpServer  - Shut down
HTTP processors
    [junit] 2007-03-20 12:52:04,788 INFO
org.apache.axis2.transport.http.server.SimpleHttpServer - HTTP protocol
handler shut down
    [junit] 3103 [main] INFO
org.apache.axis2.transport.http.server.SimpleHttpServer  - HTTP protocol
handler shut down
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 3.717
sec

BUILD FAILED
File...... /home/nmm42/.maven/cache/maven-multiproject-plugin-1.5-SNAPSHOT/plugin.jelly
Element... maven:reactor
Line...... 227
Column.... 64
Unable to obtain goal [multiproject:install-callback]
-- /home/nmm42/.maven/cache/maven-test-plugin-1.8.1-SNAPSHOT/plugin.jelly:155:49: <junit> Test org.apache.axis2.jaxws.framework.JAXWSTest failed
Total time: 42 minutes 23 seconds
Finished at: Tue Mar 20 12:52:05 GMT 2007



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [Axis2] Axis2 1.2 release prograss

Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Deepal,

I think first of all you need to fix the script which creates nightly
builds, which is broken. Otherwise it would be quite difficult to test
everything ;).

Michele

On Tue, 2007-03-20 at 16:08 +0530, Deepal Jayasinghe wrote:
> Hi All;
> 
> As I mentioned in [1] most of the features are in complete state (of
> course some of them as experimental features) so we are ready to go
> ahead with 1.2 release :) . The status of the feature items are listed
> below and there are few items that I would like to see the status
> (specially JAX-WS ) , so please update the list on their progress.
> 
> About the release I would like to release Axis2 1.2 RC1 on this Friday
> (24^th March) and do the testing , depending on the JIRAs and other
> issue will decide whether we need some other RC or not. And release
> Axis2 1.2 on April first week (if every thing went well).
> 
> - WSDL 2.0 fully support – DONE
> (Reading , writing and codegen)
> 
> - POJO – annotation – DONE 
>   (Almost complete but need more testing)
> - REST Annotation 
>   (I forget this item , what do we need to do here , is that some kind of custom annotation for REST ?)
> - JAX-WS integration
>  (Please update the list )
> - JAX-WS -annotation
>  (I hope we do have JAX-WS annotation support , any way please update the list)
> - Un-wrapping (Response) - DONE
> - ADB - missing schema support - DONE
> - Move security and Sawan module from Axis2 trunk -DONE
> - Maven2 support – Almost done (dims are we in good position on mvn2)
> - JASON support - DONE
> - Binary serialization – almost done
> - Geronimo Integration 
>  (Lasantha pls update the list )
> - Jax-ws option for code gen (Jaxbri as the db) – Wont implement
> - Custom File cache mechanism – Thilina ?
> - Multiple services support in code gen (WSDL with multiple services) -DONE
> - HTTP code generation (both WSDL 1.1 and 2.0) -DONE
> - i18n support – Won't implement
> - Fix/update helper mode - DONE
> 
> In addition to above major features we have fixed numerous JIRA issues
> and have added new features as well (Custom deployers , Message
> formatters , Builders etc etc.)
> 
> How abt JAX-WS release , is that going to follow a separate release
> cycle or will that be release with Axis2 ?
> 
> So what do you think about the release plan , is that ok if I go ahead
> with that and do the RC1 end of this week :)
> 
> [1] - http://marc.info/?l=axis-user&m=116900551522771&w=2
> 
> Thanks
> Deepal
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: unsuscribe

Posted by Alemu Tesfaye <cy...@gmail.com>.
On 3/21/07, Chris Rocker <ch...@yahoo.com> wrote:
>
> unsuscribe
>
> ------------------------------
> Need Mail bonding?
> Go to the Yahoo! Mail Q&A<http://answers.yahoo.com/dir/index;_ylc=X3oDMTFvbGNhMGE3BF9TAzM5NjU0NTEwOARfcwMzOTY1NDUxMDMEc2VjA21haWxfdGFnbGluZQRzbGsDbWFpbF90YWcx?link=ask&sid=396546091>for great
> tips from Yahoo! Answers<http://answers.yahoo.com/dir/index;_ylc=X3oDMTFvbGNhMGE3BF9TAzM5NjU0NTEwOARfcwMzOTY1NDUxMDMEc2VjA21haWxfdGFnbGluZQRzbGsDbWFpbF90YWcx?link=ask&sid=396546091>users.
>
>

unsuscribe

Posted by Chris Rocker <ch...@yahoo.com>.
unsuscribe

 
---------------------------------
Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.

Re: [Axis2] Axis2 1.2 release prograss

Posted by Davanum Srinivas <da...@gmail.com>.
Those are my 2 cents :)

-- dims

On 3/21/07, Thilina Gunarathne <cs...@gmail.com> wrote:
> Sounds like a discussion that should happen in the Axis2-dev list..
>
> ---------- Forwarded message ----------
> From: Davanum Srinivas < davanum@gmail.com>
> Date: Mar 21, 2007 4:00 PM
> Subject: Re: [Axis2] Axis2 1.2 release prograss
> To: axis-user@ws.apache.org
>
> Amila,
>
> Please comment that test out (create a JIRA that the test is failing) and
> check in your changes.
>
> thanks,
> dims
>
>
> On 3/21/07, Amila Suriarachchi <am...@gmail.com> wrote:
> >
> >
> >
> > On 3/20/07, Nicholas L Gallardo <nlgallar@us.ibm.com > wrote:
> > >
> > > +1  JAX-WS will have to be labeled experimental or "early access" until
> we're able to pass the TCK, which won't happen in two weeks.
> >
> >
> > I would like to point  out an issue  regarding the  processing of the
> parameterOder attribute  in WSDL11. As I disscussed this in a sperate
> thread[1] (it seems to be now no one replying it) there is a problem in
> fixing this issue because of a failing test case in jaxws.
> > Since we are going to release the jaxws as experimental shall we skip this
> test and proceed with the fix. On the other hand we have to do the WSDL 1.1
> in production level as well. I belive we must have this fix for RC1.
> >
> > [1]http://marc.info/?l=axis-dev&m=117396135721812&w=2
> >
> >
> > > Regards,
> > > -Nick
> > >
> > >
> > >
> >
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Fwd: [Axis2] Axis2 1.2 release prograss

Posted by Thilina Gunarathne <cs...@gmail.com>.
Sounds like a discussion that should happen in the Axis2-dev list..

---------- Forwarded message ----------
From: Davanum Srinivas <da...@gmail.com>
Date: Mar 21, 2007 4:00 PM
Subject: Re: [Axis2] Axis2 1.2 release prograss
To: axis-user@ws.apache.org

Amila,

Please comment that test out (create a JIRA that the test is failing) and
check in your changes.

thanks,
dims

On 3/21/07, Amila Suriarachchi <am...@gmail.com> wrote:
>
>
>
> On 3/20/07, Nicholas L Gallardo <nlgallar@us.ibm.com > wrote:
> >
> >
> > +1  JAX-WS will have to be labeled experimental or "early access" until
> > we're able to pass the TCK, which won't happen in two weeks.
>
>
> I would like to point  out an issue  regarding the  processing of the
> parameterOder attribute  in WSDL11. As I disscussed this in a sperate
> thread[1] (it seems to be now no one replying it) there is a problem in
> fixing this issue because of a failing test case in jaxws.
> Since we are going to release the jaxws as experimental shall we skip this
> test and proceed with the fix. On the other hand we have to do the WSDL
> 1.1 in production level as well. I belive we must have this fix for RC1.
>
> [1]http://marc.info/?l=axis-dev&m=117396135721812&w=2
>
> Regards,
> > -Nick
> >
> >
> >

Re: [Axis2] Axis2 1.2 release prograss

Posted by Davanum Srinivas <da...@gmail.com>.
Amila,

Please comment that test out (create a JIRA that the test is failing) and
check in your changes.

thanks,
dims

On 3/21/07, Amila Suriarachchi <am...@gmail.com> wrote:
>
>
>
> On 3/20/07, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
> >
> >
> > +1  JAX-WS will have to be labeled experimental or "early access" until
> > we're able to pass the TCK, which won't happen in two weeks.
>
>
> I would like to point  out an issue  regarding the  processing of the
> parameterOder attribute  in WSDL11. As I disscussed this in a sperate
> thread[1] (it seems to be now no one replying it) there is a problem in
> fixing this issue because of a failing test case in jaxws.
> Since we are going to release the jaxws as experimental shall we skip this
> test and proceed with the fix. On the other hand we have to do the WSDL
> 1.1 in production level as well. I belive we must have this fix for RC1.
>
> [1]http://marc.info/?l=axis-dev&m=117396135721812&w=2
>
> Regards,
> > -Nick
> >
> >
> >
> > Nicholas Gallardo
> > WebSphere  -  WebServices Development
> > nlgallar@us.ibm.com
> > Phone: 512-838-1182
> > Building: 901 / 5G-016
> >
> >
> >  *"Davanum Srinivas" <da...@gmail.com>*
> >
> > 03/20/2007 05:50 AM  Please respond to
> > axis-dev@ws.apache.org
> >
> >   To
> > axis-dev@ws.apache.org  cc
> > "axis-user@ws.apache.org" <ax...@ws.apache.org>  Subject
> > Re: [Axis2] Axis2 1.2 release prograss
> >
> >
> >
> >
> >
> >
> > Deepal,
> >
> > we should release whatever JAXWS support we have with 1.2 release and
> > mark it as experimental. The mvn2 seems ok. we still need to move
> > integration module to m2.
> >
> > Thanks,
> > dims
> >
> > On 3/20/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> > > Hi All;
> > >
> > > As I mentioned in [1] most of the features are in complete state (of
> > > course some of them as experimental features) so we are ready to go
> > > ahead with 1.2 release :) . The status of the feature items are listed
> > > below and there are few items that I would like to see the status
> > > (specially JAX-WS ) , so please update the list on their progress.
> > >
> > > About the release I would like to release Axis2 1.2 RC1 on this Friday
> > > (24^th March) and do the testing , depending on the JIRAs and other
> > > issue will decide whether we need some other RC or not. And release
> > > Axis2 1.2 on April first week (if every thing went well).
> > >
> > > - WSDL 2.0 fully support – DONE
> > > (Reading , writing and codegen)
> > >
> > > - POJO – annotation – DONE
> > >   (Almost complete but need more testing)
> > > - REST Annotation
> > >   (I forget this item , what do we need to do here , is that some kind
> > of custom annotation for REST ?)
> > > - JAX-WS integration
> > >  (Please update the list )
> > > - JAX-WS -annotation
> > >  (I hope we do have JAX-WS annotation support , any way please update
> > the list)
> > > - Un-wrapping (Response) - DONE
> > > - ADB - missing schema support - DONE
> > > - Move security and Sawan module from Axis2 trunk -DONE
> > > - Maven2 support – Almost done (dims are we in good position on mvn2)
> > > - JASON support - DONE
> > > - Binary serialization – almost done
> > > - Geronimo Integration
> > >  (Lasantha pls update the list )
> > > - Jax-ws option for code gen (Jaxbri as the db) – Wont implement
> > > - Custom File cache mechanism – Thilina ?
> > > - Multiple services support in code gen (WSDL with multiple services)
> > -DONE
> > > - HTTP code generation (both WSDL 1.1 and 2.0) -DONE
> > > - i18n support – Won't implement
> > > - Fix/update helper mode - DONE
> > >
> > > In addition to above major features we have fixed numerous JIRA issues
> > > and have added new features as well (Custom deployers , Message
> > > formatters , Builders etc etc.)
> > >
> > > How abt JAX-WS release , is that going to follow a separate release
> > > cycle or will that be release with Axis2 ?
> > >
> > > So what do you think about the release plan , is that ok if I go ahead
> > > with that and do the RC1 end of this week :)
> > >
> > > [1] - http://marc.info/?l=axis-user&m=116900551522771&w=2
> > >
> > > Thanks
> > > Deepal
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services
> > Developers
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
> >
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.




-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

Re: [Axis2] Axis2 1.2 release prograss

Posted by Amila Suriarachchi <am...@gmail.com>.
On 3/20/07, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
>
>
> +1  JAX-WS will have to be labeled experimental or "early access" until
> we're able to pass the TCK, which won't happen in two weeks.


I would like to point  out an issue  regarding the  processing of the
parameterOder attribute  in WSDL11. As I disscussed this in a sperate
thread[1] (it seems to be now no one replying it) there is a problem in
fixing this issue because of a failing test case in jaxws.
Since we are going to release the jaxws as experimental shall we skip this
test and proceed with the fix. On the other hand we have to do the
WSDL 1.1in production level as well. I belive we must have this fix
for RC1.

[1]http://marc.info/?l=axis-dev&m=117396135721812&w=2

Regards,
> -Nick
>
>
>
> Nicholas Gallardo
> WebSphere  -  WebServices Development
> nlgallar@us.ibm.com
> Phone: 512-838-1182
> Building: 901 / 5G-016
>
>
>  *"Davanum Srinivas" <da...@gmail.com>*
>
> 03/20/2007 05:50 AM  Please respond to
> axis-dev@ws.apache.org
>
>   To
> axis-dev@ws.apache.org  cc
> "axis-user@ws.apache.org" <ax...@ws.apache.org>  Subject
> Re: [Axis2] Axis2 1.2 release prograss
>
>
>
>
>
>
> Deepal,
>
> we should release whatever JAXWS support we have with 1.2 release and
> mark it as experimental. The mvn2 seems ok. we still need to move
> integration module to m2.
>
> Thanks,
> dims
>
> On 3/20/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> > Hi All;
> >
> > As I mentioned in [1] most of the features are in complete state (of
> > course some of them as experimental features) so we are ready to go
> > ahead with 1.2 release :) . The status of the feature items are listed
> > below and there are few items that I would like to see the status
> > (specially JAX-WS ) , so please update the list on their progress.
> >
> > About the release I would like to release Axis2 1.2 RC1 on this Friday
> > (24^th March) and do the testing , depending on the JIRAs and other
> > issue will decide whether we need some other RC or not. And release
> > Axis2 1.2 on April first week (if every thing went well).
> >
> > - WSDL 2.0 fully support – DONE
> > (Reading , writing and codegen)
> >
> > - POJO – annotation – DONE
> >   (Almost complete but need more testing)
> > - REST Annotation
> >   (I forget this item , what do we need to do here , is that some kind
> of custom annotation for REST ?)
> > - JAX-WS integration
> >  (Please update the list )
> > - JAX-WS -annotation
> >  (I hope we do have JAX-WS annotation support , any way please update
> the list)
> > - Un-wrapping (Response) - DONE
> > - ADB - missing schema support - DONE
> > - Move security and Sawan module from Axis2 trunk -DONE
> > - Maven2 support – Almost done (dims are we in good position on mvn2)
> > - JASON support - DONE
> > - Binary serialization – almost done
> > - Geronimo Integration
> >  (Lasantha pls update the list )
> > - Jax-ws option for code gen (Jaxbri as the db) – Wont implement
> > - Custom File cache mechanism – Thilina ?
> > - Multiple services support in code gen (WSDL with multiple services)
> -DONE
> > - HTTP code generation (both WSDL 1.1 and 2.0) -DONE
> > - i18n support – Won't implement
> > - Fix/update helper mode - DONE
> >
> > In addition to above major features we have fixed numerous JIRA issues
> > and have added new features as well (Custom deployers , Message
> > formatters , Builders etc etc.)
> >
> > How abt JAX-WS release , is that going to follow a separate release
> > cycle or will that be release with Axis2 ?
> >
> > So what do you think about the release plan , is that ok if I go ahead
> > with that and do the RC1 end of this week :)
> >
> > [1] - http://marc.info/?l=axis-user&m=116900551522771&w=2
> >
> > Thanks
> > Deepal
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] Axis2 1.2 release prograss

Posted by Nicholas L Gallardo <nl...@us.ibm.com>.
+1  JAX-WS will have to be labeled experimental or "early access" until 
we're able to pass the TCK, which won't happen in two weeks.

Regards,
-Nick



Nicholas Gallardo
WebSphere  -  WebServices Development
nlgallar@us.ibm.com
Phone: 512-838-1182
Building: 901 / 5G-016



"Davanum Srinivas" <da...@gmail.com> 
03/20/2007 05:50 AM
Please respond to
axis-dev@ws.apache.org


To
axis-dev@ws.apache.org
cc
"axis-user@ws.apache.org" <ax...@ws.apache.org>
Subject
Re: [Axis2] Axis2 1.2 release prograss






Deepal,

we should release whatever JAXWS support we have with 1.2 release and
mark it as experimental. The mvn2 seems ok. we still need to move
integration module to m2.

Thanks,
dims

On 3/20/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> Hi All;
>
> As I mentioned in [1] most of the features are in complete state (of
> course some of them as experimental features) so we are ready to go
> ahead with 1.2 release :) . The status of the feature items are listed
> below and there are few items that I would like to see the status
> (specially JAX-WS ) , so please update the list on their progress.
>
> About the release I would like to release Axis2 1.2 RC1 on this Friday
> (24^th March) and do the testing , depending on the JIRAs and other
> issue will decide whether we need some other RC or not. And release
> Axis2 1.2 on April first week (if every thing went well).
>
> - WSDL 2.0 fully support ? DONE
> (Reading , writing and codegen)
>
> - POJO ? annotation ? DONE
>   (Almost complete but need more testing)
> - REST Annotation
>   (I forget this item , what do we need to do here , is that some kind 
of custom annotation for REST ?)
> - JAX-WS integration
>  (Please update the list )
> - JAX-WS -annotation
>  (I hope we do have JAX-WS annotation support , any way please update 
the list)
> - Un-wrapping (Response) - DONE
> - ADB - missing schema support - DONE
> - Move security and Sawan module from Axis2 trunk -DONE
> - Maven2 support ? Almost done (dims are we in good position on mvn2)
> - JASON support - DONE
> - Binary serialization ? almost done
> - Geronimo Integration
>  (Lasantha pls update the list )
> - Jax-ws option for code gen (Jaxbri as the db) ? Wont implement
> - Custom File cache mechanism ? Thilina ?
> - Multiple services support in code gen (WSDL with multiple services) 
-DONE
> - HTTP code generation (both WSDL 1.1 and 2.0) -DONE
> - i18n support ? Won't implement
> - Fix/update helper mode - DONE
>
> In addition to above major features we have fixed numerous JIRA issues
> and have added new features as well (Custom deployers , Message
> formatters , Builders etc etc.)
>
> How abt JAX-WS release , is that going to follow a separate release
> cycle or will that be release with Axis2 ?
>
> So what do you think about the release plan , is that ok if I go ahead
> with that and do the RC1 end of this week :)
>
> [1] - http://marc.info/?l=axis-user&m=116900551522771&w=2
>
> Thanks
> Deepal
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org



Re: [Axis2] Axis2 1.2 release prograss

Posted by Nicholas L Gallardo <nl...@us.ibm.com>.
+1  JAX-WS will have to be labeled experimental or "early access" until 
we're able to pass the TCK, which won't happen in two weeks.

Regards,
-Nick



Nicholas Gallardo
WebSphere  -  WebServices Development
nlgallar@us.ibm.com
Phone: 512-838-1182
Building: 901 / 5G-016



"Davanum Srinivas" <da...@gmail.com> 
03/20/2007 05:50 AM
Please respond to
axis-dev@ws.apache.org


To
axis-dev@ws.apache.org
cc
"axis-user@ws.apache.org" <ax...@ws.apache.org>
Subject
Re: [Axis2] Axis2 1.2 release prograss






Deepal,

we should release whatever JAXWS support we have with 1.2 release and
mark it as experimental. The mvn2 seems ok. we still need to move
integration module to m2.

Thanks,
dims

On 3/20/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> Hi All;
>
> As I mentioned in [1] most of the features are in complete state (of
> course some of them as experimental features) so we are ready to go
> ahead with 1.2 release :) . The status of the feature items are listed
> below and there are few items that I would like to see the status
> (specially JAX-WS ) , so please update the list on their progress.
>
> About the release I would like to release Axis2 1.2 RC1 on this Friday
> (24^th March) and do the testing , depending on the JIRAs and other
> issue will decide whether we need some other RC or not. And release
> Axis2 1.2 on April first week (if every thing went well).
>
> - WSDL 2.0 fully support ? DONE
> (Reading , writing and codegen)
>
> - POJO ? annotation ? DONE
>   (Almost complete but need more testing)
> - REST Annotation
>   (I forget this item , what do we need to do here , is that some kind 
of custom annotation for REST ?)
> - JAX-WS integration
>  (Please update the list )
> - JAX-WS -annotation
>  (I hope we do have JAX-WS annotation support , any way please update 
the list)
> - Un-wrapping (Response) - DONE
> - ADB - missing schema support - DONE
> - Move security and Sawan module from Axis2 trunk -DONE
> - Maven2 support ? Almost done (dims are we in good position on mvn2)
> - JASON support - DONE
> - Binary serialization ? almost done
> - Geronimo Integration
>  (Lasantha pls update the list )
> - Jax-ws option for code gen (Jaxbri as the db) ? Wont implement
> - Custom File cache mechanism ? Thilina ?
> - Multiple services support in code gen (WSDL with multiple services) 
-DONE
> - HTTP code generation (both WSDL 1.1 and 2.0) -DONE
> - i18n support ? Won't implement
> - Fix/update helper mode - DONE
>
> In addition to above major features we have fixed numerous JIRA issues
> and have added new features as well (Custom deployers , Message
> formatters , Builders etc etc.)
>
> How abt JAX-WS release , is that going to follow a separate release
> cycle or will that be release with Axis2 ?
>
> So what do you think about the release plan , is that ok if I go ahead
> with that and do the RC1 end of this week :)
>
> [1] - http://marc.info/?l=axis-user&m=116900551522771&w=2
>
> Thanks
> Deepal
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org



Re: [Axis2] Axis2 1.2 release prograss

Posted by Davanum Srinivas <da...@gmail.com>.
Deepal,

we should release whatever JAXWS support we have with 1.2 release and
mark it as experimental. The mvn2 seems ok. we still need to move
integration module to m2.

Thanks,
dims

On 3/20/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> Hi All;
>
> As I mentioned in [1] most of the features are in complete state (of
> course some of them as experimental features) so we are ready to go
> ahead with 1.2 release :) . The status of the feature items are listed
> below and there are few items that I would like to see the status
> (specially JAX-WS ) , so please update the list on their progress.
>
> About the release I would like to release Axis2 1.2 RC1 on this Friday
> (24^th March) and do the testing , depending on the JIRAs and other
> issue will decide whether we need some other RC or not. And release
> Axis2 1.2 on April first week (if every thing went well).
>
> - WSDL 2.0 fully support – DONE
> (Reading , writing and codegen)
>
> - POJO – annotation – DONE
>   (Almost complete but need more testing)
> - REST Annotation
>   (I forget this item , what do we need to do here , is that some kind of custom annotation for REST ?)
> - JAX-WS integration
>  (Please update the list )
> - JAX-WS -annotation
>  (I hope we do have JAX-WS annotation support , any way please update the list)
> - Un-wrapping (Response) - DONE
> - ADB - missing schema support - DONE
> - Move security and Sawan module from Axis2 trunk -DONE
> - Maven2 support – Almost done (dims are we in good position on mvn2)
> - JASON support - DONE
> - Binary serialization – almost done
> - Geronimo Integration
>  (Lasantha pls update the list )
> - Jax-ws option for code gen (Jaxbri as the db) – Wont implement
> - Custom File cache mechanism – Thilina ?
> - Multiple services support in code gen (WSDL with multiple services) -DONE
> - HTTP code generation (both WSDL 1.1 and 2.0) -DONE
> - i18n support – Won't implement
> - Fix/update helper mode - DONE
>
> In addition to above major features we have fixed numerous JIRA issues
> and have added new features as well (Custom deployers , Message
> formatters , Builders etc etc.)
>
> How abt JAX-WS release , is that going to follow a separate release
> cycle or will that be release with Axis2 ?
>
> So what do you think about the release plan , is that ok if I go ahead
> with that and do the RC1 end of this week :)
>
> [1] - http://marc.info/?l=axis-user&m=116900551522771&w=2
>
> Thanks
> Deepal
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [Axis2] Axis2 1.2 release prograss

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Deepal Jayasinghe wrote:
> 
> - WSDL 2.0 fully support – DONE
> (Reading , writing and codegen)

Do we have ?wsdl2 support also? If not that needs to be on the list.

> - REST Annotation 
>   (I forget this item , what do we need to do here , is that some kind of custom annotation for REST ?)

Basically we need a way for the developer to tell us what HTTP operation 
to support for each Java method. Furthermore, some hints on the URL path 
etc.- basically everything that's possible in the WSDL 2.0 binding. Keith, 
maybe we can work out a set of annotations to map into WSDL 2.0? Then 
it'll be easy to impl; just map them to the corresponding WSDL 2.0 HTTP 
binding properties and everything else will "just work" ;-).

> - Un-wrapping (Response) - DONE
> - ADB - missing schema support - DONE

What about the nice names for parameters instead of param69 etc.? I think 
that's a blocker for 1.2!

> So what do you think about the release plan , is that ok if I go ahead
> with that and do the RC1 end of this week :)

+1!

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

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [Axis2] Axis2 1.2 release prograss

Posted by Davanum Srinivas <da...@gmail.com>.
Deepal,

we should release whatever JAXWS support we have with 1.2 release and
mark it as experimental. The mvn2 seems ok. we still need to move
integration module to m2.

Thanks,
dims

On 3/20/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> Hi All;
>
> As I mentioned in [1] most of the features are in complete state (of
> course some of them as experimental features) so we are ready to go
> ahead with 1.2 release :) . The status of the feature items are listed
> below and there are few items that I would like to see the status
> (specially JAX-WS ) , so please update the list on their progress.
>
> About the release I would like to release Axis2 1.2 RC1 on this Friday
> (24^th March) and do the testing , depending on the JIRAs and other
> issue will decide whether we need some other RC or not. And release
> Axis2 1.2 on April first week (if every thing went well).
>
> - WSDL 2.0 fully support – DONE
> (Reading , writing and codegen)
>
> - POJO – annotation – DONE
>   (Almost complete but need more testing)
> - REST Annotation
>   (I forget this item , what do we need to do here , is that some kind of custom annotation for REST ?)
> - JAX-WS integration
>  (Please update the list )
> - JAX-WS -annotation
>  (I hope we do have JAX-WS annotation support , any way please update the list)
> - Un-wrapping (Response) - DONE
> - ADB - missing schema support - DONE
> - Move security and Sawan module from Axis2 trunk -DONE
> - Maven2 support – Almost done (dims are we in good position on mvn2)
> - JASON support - DONE
> - Binary serialization – almost done
> - Geronimo Integration
>  (Lasantha pls update the list )
> - Jax-ws option for code gen (Jaxbri as the db) – Wont implement
> - Custom File cache mechanism – Thilina ?
> - Multiple services support in code gen (WSDL with multiple services) -DONE
> - HTTP code generation (both WSDL 1.1 and 2.0) -DONE
> - i18n support – Won't implement
> - Fix/update helper mode - DONE
>
> In addition to above major features we have fixed numerous JIRA issues
> and have added new features as well (Custom deployers , Message
> formatters , Builders etc etc.)
>
> How abt JAX-WS release , is that going to follow a separate release
> cycle or will that be release with Axis2 ?
>
> So what do you think about the release plan , is that ok if I go ahead
> with that and do the RC1 end of this week :)
>
> [1] - http://marc.info/?l=axis-user&m=116900551522771&w=2
>
> Thanks
> Deepal
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org