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 Glen Daniels <gl...@thoughtcraft.com> on 2007/11/13 00:42:00 UTC
[axis2] Hackathon plans
Hi folks!
So Deepal and I are taking a look at our current post-1.3 list [1].
We've got some more hacking time tomorrow and are hoping to start
tackling some of the items from the list. In particular, we're thinking
of talking about the stuff that requires some architectural thinking or
serious design, to maximize our face-time. If we come out with more
documents/emails than code for now, that's great. Some topics:
* Discuss the URL / file deployment design, and get ready to implement
* Glen will look into WSDL generation (rationalizing 1.1/2.0) in the
afternoon when Deepal is busy w/his tutorial
* Discuss RPC/Enc support
* Sweep through list and prioritize things that we really need to have
done for 1.4.
If there are particular things you'd like us to cover, or if you'd like
to participate in these discussions via IRC, please let us know!
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [axis2] Hackathon plans
Posted by Amila Suriarachchi <am...@gmail.com>.
please check this issue as well. I do not have a clear understanding
in this area.
https://issues.apache.org/jira/browse/AXIS2-3296
thanks,
Amila.
On Nov 13, 2007 2:42 PM, Amila Suriarachchi <am...@gmail.com> wrote:
> something to discuss in hackathon (or even in this list).
>
> have a look at this issue
> https://issues.apache.org/jira/browse/AXIS2-3294
>
> basically he is asking to keep the default http protocol as Http 1.0.
> if there is no reason to
> keep it as Http 1.1 I think it is reasonable to do this change.
>
> And also if there no reason to switch on chunking by default shall we
> remove that as well.
> I saw some people have .net interop problems becauase of chunking.
>
> Any thoughts??
>
> in default Axis2.xml here is how it has given.
>
> <transportSender name="http"
>
> class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> <parameter name="PROTOCOL">HTTP/1.1</parameter>
> <parameter name="Transfer-Encoding">chunked</parameter>
>
> </transportSender>
>
> thanks,
> Amila.
>
>
> On Nov 13, 2007 9:45 AM, Deepal jayasinghe <de...@gmail.com> wrote:
> >
> > > Hi Glen/Deepal,
> > >
> > > How about Support binding level policies (dispatch to BindingMessage
> > > <http://wiki.apache.org/ws/BindingMessage>?).
> > Actually that something we really need to do and we discussed about this
> > at the last hackathon as well. Depending on the time we got we will
> > definitely look into this.
> >
> > Thanks
> > Deepal
> >
> >
> > ---------------------------------------------------------------------
> > 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.
>
--
Amila Suriarachchi,
WSO2 Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [axis2] Hackathon plans
Posted by Amila Suriarachchi <am...@gmail.com>.
something to discuss in hackathon (or even in this list).
have a look at this issue
https://issues.apache.org/jira/browse/AXIS2-3294
basically he is asking to keep the default http protocol as Http 1.0.
if there is no reason to
keep it as Http 1.1 I think it is reasonable to do this change.
And also if there no reason to switch on chunking by default shall we
remove that as well.
I saw some people have .net interop problems becauase of chunking.
Any thoughts??
in default Axis2.xml here is how it has given.
<transportSender name="http"
class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
<parameter name="PROTOCOL">HTTP/1.1</parameter>
<parameter name="Transfer-Encoding">chunked</parameter>
</transportSender>
thanks,
Amila.
On Nov 13, 2007 9:45 AM, Deepal jayasinghe <de...@gmail.com> wrote:
>
> > Hi Glen/Deepal,
> >
> > How about Support binding level policies (dispatch to BindingMessage
> > <http://wiki.apache.org/ws/BindingMessage>?).
> Actually that something we really need to do and we discussed about this
> at the last hackathon as well. Depending on the time we got we will
> definitely look into this.
>
> Thanks
> Deepal
>
>
> ---------------------------------------------------------------------
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [axis2] Hackathon plans
Posted by Deepal jayasinghe <de...@gmail.com>.
> Hi Glen/Deepal,
>
> How about Support binding level policies (dispatch to BindingMessage
> <http://wiki.apache.org/ws/BindingMessage>?).
Actually that something we really need to do and we discussed about this
at the last hackathon as well. Depending on the time we got we will
definitely look into this.
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] Hackathon plans
Posted by keith chapman <ke...@gmail.com>.
Hi Glen/Deepal,
How about Support binding level policies (dispatch to
BindingMessage<http://wiki.apache.org/ws/BindingMessage>?).
In order to do this we will have to make full use of the Axis Binding
hierarchy, Currently this hierarchy is made use of only during deployment
using a WSDL (WSDL 1.1 or WSDL 2.0). How about populating the default
bindings (SOAP 1.1, SOAP 1.2, HTTP) if no details of bindings are present?
This will help us bring the WSDL 2.0 HttpBinding properties to pojos as
well. Cause at present properties such are HTTPLocation are drawn from the
binding hierarchy which pojo deployer does not populate. This makes it
impossible to leverage the benefits of WSDL 2.0 HttpBinding across axis2. If
we can get this sorted out we can offer better REST support via pojos rather
than defaulting it to servicename/operationName.
Thanks,
Keith.
On Nov 13, 2007 5:12 AM, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Hi folks!
>
> So Deepal and I are taking a look at our current post-1.3 list [1].
> We've got some more hacking time tomorrow and are hoping to start
> tackling some of the items from the list. In particular, we're thinking
> of talking about the stuff that requires some architectural thinking or
> serious design, to maximize our face-time. If we come out with more
> documents/emails than code for now, that's great. Some topics:
>
> * Discuss the URL / file deployment design, and get ready to implement
>
> * Glen will look into WSDL generation (rationalizing 1.1/2.0) in the
> afternoon when Deepal is busy w/his tutorial
>
> * Discuss RPC/Enc support
>
> * Sweep through list and prioritize things that we really need to have
> done for 1.4.
>
> If there are particular things you'd like us to cover, or if you'd like
> to participate in these discussions via IRC, please let us know!
>
> Thanks,
> --Glen
>
> ---------------------------------------------------------------------
> 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/