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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


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

Reply via email to