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 Deepak Bhole <db...@redhat.com> on 2006/02/15 22:23:25 UTC
[Axis2] Things I can work on
Hi,
I was thinking of starting to work on some of the bigger issues/features
in axis. I see a list of TODO's on the main page:
- JAX-RPC 1.1 and/or JAX-WS compliance
- SOAP Encoding
- Binary serialization and de-serialization support
- Management Interface for Axis2
- Implementation of other Transports.
- Resource framework implementation (WS-RF) and Enterprise web services
such as JSR 109 support
- Completion of interop tests
The first one seems to be ongoing, second one is taken, so how about I
start with 3rd (binary ser./deser.)? That brings up the question, could
someone please point me to what exactly is meant by "binary
serialization/deserialization"? In the simplest sense, it seems like
being able to insert binary content into an envelope and read it back;
but we can already do that (image transfer for example), so that seems
already covered....
PS: If there anything more pressing than this that I could work on
instead, please let me know.
Thanks,
Deepak
Re: [Axis2] Things I can work on
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi all,
Yep, There are a number of things you can work on and since my name is
mentioned with respect to code generation, here are some tips about
the things to be done.
- I18n - some parts of the code has been i18ned but there's a lot of
stuff to be done. Our mechanism is a resource bundle per maven module,
and you'll probably need a messages class (have a look at ) per module
since the message classes are written bound to a specific resource
bundle.
- ADB was meant to be simple but it turned out to be a moving
horizon problem :). We need to handle the following cases (which will
bring ADB near to XMLBeans :))
* correct handling of simple content
* correct handling of simple type restrictions/extensions (we
partialy handle this by picking the base type )
* complextype restrictions (we handle extensions)
- C# support - we have done some of the preliminary C# support (IKVM
based) and it was meant to be a "proof of concept". It can easily be
made into a working solution. If we do have enough time we can
actually think of other cool stuff like generating Javascript :)
Ajith
On 2/17/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> How about more items:
>
> > I was thinking of starting to work on some of the bigger issues/features
>
> Excellent!
>
> How about some more unlisted items:
>
> - I18n of the entire codebase .. a lot of painful work :(
> - Make ADB more complete .. pick an unsupported schema construct and
> make it work .. hard work depending on the construct
> - Add support for C# stubs .. Ajith started doing this but its far from
> being done yet. (That'd mean using Axis2 under iKVM on the CLR.)
> - Come up with the ServiceLifecycle stuff (see mailing list discussion)
>
> Will send more ideas soon.
>
> Sanjiva.
>
>
--
Ajith Ranabahu
Re: [Axis2] Things I can work on
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
How about more items:
> I was thinking of starting to work on some of the bigger issues/features
Excellent!
How about some more unlisted items:
- I18n of the entire codebase .. a lot of painful work :(
- Make ADB more complete .. pick an unsupported schema construct and
make it work .. hard work depending on the construct
- Add support for C# stubs .. Ajith started doing this but its far from
being done yet. (That'd mean using Axis2 under iKVM on the CLR.)
- Come up with the ServiceLifecycle stuff (see mailing list discussion)
Will send more ideas soon.
Sanjiva.
Re: [Axis2] Things I can work on
Posted by Steve Loughran <st...@apache.org>.
Chathura Ekanayake wrote:
>
> Hi Steve and all,
>
> What are the functionalities you would expect from the management interface.
>
> I have currently implemeted the functionalities provided by the Axis2
> admin page so that those tasks can be performed using APIs. Below are
> some functionalities I have implemented so far;
>
> Getting list of serviceGroups, services, operations, modules and transports
> Getting and editing parameters at all levels (e.g. service parameters,
> global parameters)
> Getting engaged modules at various levels (e.g. global, service)
> Engage modules globally
> Engage modules to services
> Engage modules to operations
>
> And I am using Apache commons.modeler package for JMX. Therefore,
> clients can access the management interface using a
> MBeanServerConnection object and using methods like invoke
> and getAttribute with the method or attribute name as a parameter. Is
> this good enough?
Yes it is. What is useful is to have some good attributes to monitor, like
-current load
-load by endpoint
And statistics
-number of requests
-number of failed requests
-number of successful requests
-operation to reset the counters
and any other statistics that are easy to gather and easy to present.
That way a management tool can define health as "load<some value" and
#of failed requests below a certain threshold. alerting people (ideally
not us developers) when things start to fail. This is important for web
services, because
-there's no easy way to browse to the page to check it works
-if you are part of a chain, you want to find and fix a problem before
people upstream do it.
>
> And when using the WS interface, the client is just a web services
> client, using Axis2, .NET or any other technology.
>
> What specific feathers should the management interface support to use it
> with SmartFrog?
ah, that's a good question.
Right now I have a deployment of Jetty+Axis2 in our own JVM
What I'm doing there is just declaring the servlet engine and servlet
bindings of Axis
Axis2Servlet extends Servlet {
name "AxisServlet";
className "org.apache.axis2.transport.http.AxisServlet";
pathSpec "/services/*";
}
Axis2ServletContext extends ServletContext {
}
Somewhere later on I bring up jetty and bind the servlet inside the
servlet context. Because jetty isnt hosting JSP pages, I can't make
happy.jsp my liveness check for system health, so I do something else (I
forget what).
What I would like is an easy way to declare endpoints themselves,
without having to create archive files and service group XML entries and
things like that, and pass configuration data down to them.
-steve
Re: [Axis2] Things I can work on
Posted by Chathura Ekanayake <cc...@gmail.com>.
Hi Steve and all,
What are the functionalities you would expect from the management interface.
I have currently implemeted the functionalities provided by the Axis2 admin
page so that those tasks can be performed using APIs. Below are
some functionalities I have implemented so far;
Getting list of serviceGroups, services, operations, modules and transports
Getting and editing parameters at all levels (e.g. service parameters,
global parameters)
Getting engaged modules at various levels (e.g. global, service)
Engage modules globally
Engage modules to services
Engage modules to operations
And I am using Apache commons.modeler package for JMX. Therefore, clients
can access the management interface using a MBeanServerConnection object and
using methods like invoke and getAttribute with the method or attribute name
as a parameter. Is this good enough?
And when using the WS interface, the client is just a web services client,
using Axis2, .NET or any other technology.
What specific feathers should the management interface support to use it
with SmartFrog?
Regards,
Chathura.
Re: [Axis2] Things I can work on
Posted by Steve Loughran <st...@apache.org>.
Chathura Ekanayake wrote:
>
> I am busy working on the management interface. I have implemented a web
> services based interface to expose the management functionalities as well.
> And a servlet web application to manage remote engines by connecting to them
> using the remote URL. I exposed the management interface as webservices
> instead of using JMX as JMX failed in the integration. But the code can be
> easily converted to use JMX as core modules are not affected by the method
> used to expose them. I will send the code as soon as possible (within three
> days:).
>
Hey, this is great!
JMX is probably my preference because I do deploy/configure in the same
JVM, without having to worry about securing another endpoint. We have
some JMX support in smartfrog, which is currently being updated to
support new stuff, especially JSR-77 app-server deploy/config.
-steve
Re: [Axis2] Things I can work on
Posted by Chathura Ekanayake <cc...@gmail.com>.
On 2/15/06, Eran Chinthaka <ch...@opensource.lk> wrote:
>
> Hi Deepak,
>
> Deepak Bhole wrote:
>
> Hi,
>
> I was thinking of starting to work on some of the bigger issues/features
> in axis. I see a list of TODO's on the main page:
>
> - JAX-RPC 1.1 and/or JAX-WS compliance
>
>
> I think Azeez started on this.
>
> - SOAP Encoding
>
>
> No one has started on this. Someone was talking about this for sometime,
> but I didn;t see *any *activity on this so far. So this is still
> available.
>
> - Binary serialization and de-serialization support
>
>
> Let me explain this a bit. Basically we wanna integrate something like
> Fast-Infoset or DFDL so that OM can read and write binary data. Its not the
> attachments we are talking about here.
> For example, one can send the complete message binary serialized over the
> network, but AXIOM should be able to read it in and perhaps feed in to
> Axis2.
>
> Please see
> http://wiki.apache.org/ws/FrontPage/Axis2/Tasks/BinarySerialization for
> more information.
>
> - Management Interface for Axis2
>
>
> There was a Googgle SoC project on this, but it has not been integrated by
> that student in to Axis2 completely so far. So I *personally *do not like
> to mark it as complete.
I am busy working on the management interface. I have implemented a web
services based interface to expose the management functionalities as well.
And a servlet web application to manage remote engines by connecting to them
using the remote URL. I exposed the management interface as webservices
instead of using JMX as JMX failed in the integration. But the code can be
easily converted to use JMX as core modules are not affected by the method
used to expose them. I will send the code as soon as possible (within three
days:).
- Implementation of other Transports.
>
>
> We have JMS and HTTP transports tested and working well. But we have
> tested SMTP and TCP to a limited amount only. So one can either work on
> these two or implement some other transports.
>
> - Resource framework implementation (WS-RF) and Enterprise web services
> such as JSR 109 support
> - Completion of interop tests
>
>
> This is done.
>
> PS: If there anything more pressing than this that I could work on
> instead, please let me know.
>
>
> Deepak, I call for a list of features that we require for 1.0 release.
> Give the devs sometime to fill that up. But unfortunately I didn't see lot
> of people coming and filling it. But if I had announced, as the release
> manager, Axis2's 1.0 release, then lot of people would have come and
> obstruct it. IMO, this is pathetic. Anyway, please wait some time for all
> the devs to fill the list.
>
> I prefer if you can select one from that list, as that will contain more
> pressing needs.
>
> Dims and Sanjiva, do you foresee and specific features for 1.0 so that
> Deepak can work on.
>
> Thanks for your offer,
> *Eran *Chinthaka
>
> Thanks,
> Deepak
>
>
>
>
>
>
Re: [Axis2] Things I can work on
Posted by Eran Chinthaka <ch...@opensource.lk>.
Hi Deepak,
Deepak Bhole wrote:
>Thanks for the detailed list! Too many choices now :) What about
>Java2WSDL? It is a fairly critical component, and it is listed as
>experimental. Are features missing from it?
>
>
We do a small trick when we announce our features. We do not announce a
feature, until we are confortable with it and not tested to a good
extent. Actually java2wsdl is sort of done, and there is some testing
left to be done. So I don't think it will be a good option for you to
touch it. You won't get nothing much to do in that.
So I personally prefer if you can select one from the Sanjiva's list.
Thanks,
Chinthaka
>Deepak
>
>
>
>
Re: [Axis2] Things I can work on
Posted by Deepak Bhole <db...@redhat.com>.
On Thu, 2006-02-16 at 08:58 +0600, Eran Chinthaka wrote:
> Hi Deepak,
>
> Deepak Bhole wrote:
> > Hi,
> >
> > I was thinking of starting to work on some of the bigger issues/features
> > in axis. I see a list of TODO's on the main page:
> >
> > - JAX-RPC 1.1 and/or JAX-WS compliance
> >
> I think Azeez started on this.
> > - SOAP Encoding
> >
> No one has started on this. Someone was talking about this for
> sometime, but I didn;t see any activity on this so far. So this is
> still available.
> > - Binary serialization and de-serialization support
> >
> Let me explain this a bit. Basically we wanna integrate something like
> Fast-Infoset or DFDL so that OM can read and write binary data. Its
> not the attachments we are talking about here.
> For example, one can send the complete message binary serialized over
> the network, but AXIOM should be able to read it in and perhaps feed
> in to Axis2.
>
> Please see
> http://wiki.apache.org/ws/FrontPage/Axis2/Tasks/BinarySerialization
> for more information.
> > - Management Interface for Axis2
> >
> There was a Googgle SoC project on this, but it has not been
> integrated by that student in to Axis2 completely so far. So I
> personally do not like to mark it as complete.
> > - Implementation of other Transports.
> >
> We have JMS and HTTP transports tested and working well. But we have
> tested SMTP and TCP to a limited amount only. So one can either work
> on these two or implement some other transports.
> > - Resource framework implementation (WS-RF) and Enterprise web services
> > such as JSR 109 support
> > - Completion of interop tests
> >
> This is done.
>
> > PS: If there anything more pressing than this that I could work on
> > instead, please let me know.
> >
> Deepak, I call for a list of features that we require for 1.0 release.
> Give the devs sometime to fill that up. But unfortunately I didn't see
> lot of people coming and filling it. But if I had announced, as the
> release manager, Axis2's 1.0 release, then lot of people would have
> come and obstruct it. IMO, this is pathetic. Anyway, please wait some
> time for all the devs to fill the list.
>
> I prefer if you can select one from that list, as that will contain
> more pressing needs.
>
> Dims and Sanjiva, do you foresee and specific features for 1.0 so that
> Deepak can work on.
>
> Thanks for your offer,
> Eran Chinthaka
Thanks for the detailed list! Too many choices now :) What about
Java2WSDL? It is a fairly critical component, and it is listed as
experimental. Are features missing from it?
Deepak
[Axis2] WSRF impl (was Re: [Axis2] Things I can work on)
Posted by Steve Loughran <st...@apache.org>.
Srinath Perera wrote:
> Hi Eran;
>> - Resource framework implementation (WS-RF) and Enterprise web services
>> such as JSR 109 support
>> - Completion of interop tests
>> This is done.
> Do we have a WSRF impl for Axis2? where can I find more info .. I
> guess chathura will be intersting on knowing more
I have some bits of WSRF support in the CDDLM deployment API impl,
though it aint currently building against SVN_HEAD as things got moved
around since I last built it. You can check it out and look at it (under
http://sourceforge.net/projects/smartfrog , CVS area
/core/components/deployapi ), but remember this is LGPL.
most stuff is here:
http://cvs.sourceforge.net/viewcvs.py/smartfrog/core/components/deployapi/src/org/smartfrog/services/deployapi/transport/wsrf/
My design has the following features
-it uses ?id=value as a way of distinguishing resources, rather than
other aspects of WS-A, other bits that have worse interop.
Every resource does its properties as map of QNAme->Interface mappings,
the interface provides access
public interface WSRPResourceSource {
/**
* Get a property value
*
* @param property
* @return null for no match;
* @throws BaseException if they feel like it
*/
OMElement getProperty(QName property);
}
(yes, its read only props right now).
When messages hit an endpoint, WSRF messages are either handled or
rejected as not yet implemented:
http://cvs.sourceforge.net/viewcvs.py/smartfrog/core/components/deployapi/src/org/smartfrog/services/deployapi/transport/wsrf/WsrfEndpoint.java?view=markup
Operations get handed off to a processor that turns them into Xom and
dispatches them.
The goal of this design is to eliminate any implicit mapping from WSRF
resources and java instances. the resources refer to deployed things
that may be hosted on other boxes, but can be located and manipulated
under Axis through some lookup mechanism (e.g. query a tuple space for
information mapping a jobID to a node.) I need this for high
availability work, where axis can come and go but refs remain valid.
-steve
So:
Re: [Axis2] Things I can work on
Posted by Chathura Herath <ch...@gmail.com>.
Hi guys,
I am more interested in Notification and eventing, or may be a both in
one since they are very similar. I actually have done some significant
work associated with that for an Indiana University project. So
WS-Notification and Eventing is a good project to work on too. I would
love to give a hand too as time permits.
Yah i am a WSRF user not a impl guy ;-). I do not see a good
applications of this other than in grid. The grids found WSRF very
interesting because it gave a web service counterpart for their "grid
service" concept that they were strugling with.
Steve mentioned he was working on WSRF stuff sometime back, but not
sure is it for Axis2.
THanks
Chathura
On 2/16/06, Srinath Perera <he...@gmail.com> wrote:
> > Anyway, I didn't know Chathura is doing WS-RF. Thanks Chathura in advance
> > ;-)
>
> No No .. he is doing related stuff .. not a WS-RF impl .. GTK4 is
> based on WSRF lot.
> He is in that arena .. that why I said he will be intersed
>
> Deepak You have WSRF as a option :)
>
> Thanks
> Srinath
>
>
> --
> ============================
> Srinath Perera:
> http://www.cs.indiana.edu/~hperera/
> http://www.bloglines.com/blog/hemapani
>
--
Chathura Herath
http://chathurah.blogspot.com/
Re: [Axis2] Things I can work on
Posted by Srinath Perera <he...@gmail.com>.
> Anyway, I didn't know Chathura is doing WS-RF. Thanks Chathura in advance
> ;-)
No No .. he is doing related stuff .. not a WS-RF impl .. GTK4 is
based on WSRF lot.
He is in that arena .. that why I said he will be intersed
Deepak You have WSRF as a option :)
Thanks
Srinath
--
============================
Srinath Perera:
http://www.cs.indiana.edu/~hperera/
http://www.bloglines.com/blog/hemapani
Re: [Axis2] Things I can work on
Posted by Eran Chinthaka <ch...@opensource.lk>.
Srinath Perera wrote:
>Hi Eran;
>
>
>> - Resource framework implementation (WS-RF) and Enterprise web services
>> such as JSR 109 support
>>- Completion of interop tests
>> This is done.
>>
>>
>Do we have a WSRF impl for Axis2? where can I find more info .. I
>guess chathura will be intersting on knowing more
>
>
"This is done" only applies to interop tests. I've missed WS-RF :)
Anyway, I didn't know Chathura is doing WS-RF. Thanks Chathura in
advance ;-)
-- Chinthaka
>
>
Re: [Axis2] Things I can work on
Posted by Srinath Perera <he...@gmail.com>.
Hi Eran;
> - Resource framework implementation (WS-RF) and Enterprise web services
> such as JSR 109 support
> - Completion of interop tests
> This is done.
Do we have a WSRF impl for Axis2? where can I find more info .. I
guess chathura will be intersting on knowing more
> PS: If there anything more pressing than this that I could work on
> instead, please let me know.
>
> Deepak, I call for a list of features that we require for 1.0 release. Give
> the devs sometime to fill that up. But unfortunately I didn't see lot of
> people coming and filling it. But if I had announced, as the release
> manager, Axis2's 1.0 release, then lot of people would have come and
> obstruct it. IMO, this is pathetic. Anyway, please wait some time for all
> the devs to fill the list.
I will try to fill it up bit today night!! How about identifying the
features from the JIRA open issues. On my experiance compiling a list
never work out sucessfully.
I will get back to you on this with more thoughts?
Thanks
Srinath
> Thanks for your offer,
> Eran Chinthaka
>
> Thanks,
> Deepak
>
>
>
>
>
--
============================
Srinath Perera:
http://www.cs.indiana.edu/~hperera/
http://www.bloglines.com/blog/hemapani
Re: [Axis2] Things I can work on
Posted by Davanum Srinivas <da...@gmail.com>.
oops s/Ajith/Afkham :)
On 2/16/06, Davanum Srinivas <da...@gmail.com> wrote:
> Deepak,
>
> +1 from me for you to help Ajith with JAX-WS stuff.
>
> thanks,
> dims
>
> On 2/16/06, Afkham Azeez <af...@gmail.com> wrote:
> > On 2/16/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> > > Hi Deepak,
> > >
> > > Deepak Bhole wrote:
> > > Hi,
> > >
> > > I was thinking of starting to work on some of the bigger issues/features
> > > in axis. I see a list of TODO's on the main page:
> > >
> > > - JAX-RPC 1.1 and/or JAX-WS compliance
> > >
> > > I think Azeez started on this.
> >
> > Acutally only the JAX-WS interfaces have been added in as a jaxws
> > module. No real work has been planned or started on this module yet.
> > So you are welcome to look into this area as well :)
> >
> > Regards
> > Azeez
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2] Things I can work on
Posted by Davanum Srinivas <da...@gmail.com>.
Deepak,
+1 from me for you to help Ajith with JAX-WS stuff.
thanks,
dims
On 2/16/06, Afkham Azeez <af...@gmail.com> wrote:
> On 2/16/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> > Hi Deepak,
> >
> > Deepak Bhole wrote:
> > Hi,
> >
> > I was thinking of starting to work on some of the bigger issues/features
> > in axis. I see a list of TODO's on the main page:
> >
> > - JAX-RPC 1.1 and/or JAX-WS compliance
> >
> > I think Azeez started on this.
>
> Acutally only the JAX-WS interfaces have been added in as a jaxws
> module. No real work has been planned or started on this module yet.
> So you are welcome to look into this area as well :)
>
> Regards
> Azeez
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2] Things I can work on
Posted by Afkham Azeez <af...@gmail.com>.
On 2/16/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> Hi Deepak,
>
> Deepak Bhole wrote:
> Hi,
>
> I was thinking of starting to work on some of the bigger issues/features
> in axis. I see a list of TODO's on the main page:
>
> - JAX-RPC 1.1 and/or JAX-WS compliance
>
> I think Azeez started on this.
Acutally only the JAX-WS interfaces have been added in as a jaxws
module. No real work has been planned or started on this module yet.
So you are welcome to look into this area as well :)
Regards
Azeez
Re: [Axis2] Things I can work on
Posted by Eran Chinthaka <ch...@opensource.lk>.
Hi Deepak,
Deepak Bhole wrote:
>Hi,
>
>I was thinking of starting to work on some of the bigger issues/features
>in axis. I see a list of TODO's on the main page:
>
>- JAX-RPC 1.1 and/or JAX-WS compliance
>
>
I think Azeez started on this.
>- SOAP Encoding
>
>
No one has started on this. Someone was talking about this for sometime,
but I didn;t see *any *activity on this so far. So this is still available.
>- Binary serialization and de-serialization support
>
>
Let me explain this a bit. Basically we wanna integrate something like
Fast-Infoset or DFDL so that OM can read and write binary data. Its not
the attachments we are talking about here.
For example, one can send the complete message binary serialized over
the network, but AXIOM should be able to read it in and perhaps feed in
to Axis2.
Please see
http://wiki.apache.org/ws/FrontPage/Axis2/Tasks/BinarySerialization for
more information.
>- Management Interface for Axis2
>
>
There was a Googgle SoC project on this, but it has not been integrated
by that student in to Axis2 completely so far. So I *personally *do not
like to mark it as complete.
>- Implementation of other Transports.
>
>
We have JMS and HTTP transports tested and working well. But we have
tested SMTP and TCP to a limited amount only. So one can either work on
these two or implement some other transports.
>- Resource framework implementation (WS-RF) and Enterprise web services
> such as JSR 109 support
>- Completion of interop tests
>
>
This is done.
>PS: If there anything more pressing than this that I could work on
>instead, please let me know.
>
>
Deepak, I call for a list of features that we require for 1.0 release.
Give the devs sometime to fill that up. But unfortunately I didn't see
lot of people coming and filling it. But if I had announced, as the
release manager, Axis2's 1.0 release, then lot of people would have come
and obstruct it. IMO, this is pathetic. Anyway, please wait some time
for all the devs to fill the list.
I prefer if you can select one from that list, as that will contain
more pressing needs.
Dims and Sanjiva, do you foresee and specific features for 1.0 so that
Deepak can work on.
Thanks for your offer,
*Eran *Chinthaka
>Thanks,
>Deepak
>
>
>
>