WSRequest

TASKS

-- XPI release
-- ActiveX release

 We need to do a new release of the above two things ASAP.. The currently released versions support only the *now* deprecated SOAPHttpRequest..

Improvement Suggestions

-- HTTPLocation
-- HTTPVersion
-- replace useSOAP with "binding"
-- Security functionality     
-- Support for operations

Proposal for the above points can be found at http://wso2.org/mailarchive/wsf-general/2007-April/000087.html ...

-- Authentication (WSDL?)
WSDL2.0 can contain some form of authentication related meta-data.. According to Jonathan we might be able to support a similar thing in the WSRequest API too..
-- Performance?? (Post alpha1)..factory (stub)..

 Performance issues that can arise due to the creation of WSRequest objects per invocation basis were discussed. We are instantiating a org.apache.axis2.client.ServiceClient object each time we create WSRequest object, which can be a heavy operation if a large number of WSRequest objects were created.

One suggestion is to use some kind of a Factory or a cloning method as a remedy for the above.. We decided to look in to these issues after the alpha1..  

Mashup Server Major TODO Items

-- UI

UI for the MASHUP server  is the main blocker at this moment.. Milinda is looking in to it..

-- Documentation

HOWTO doc
-- ? support (https://www.wso2.org/jira/browse/WSAS-213)

We decided to request a pluggable url ? framework from WSAS..  (ex: http://localhost/services/echo?stub).
This framework should allow us to manipulate additional parameters too.. (ex: http://localhost/services/echo?stub&language=e4x\|firefox).

Plugging the ?stub ability to generate a javascript client for the deployed service is identified as a top priority.. Jonathan will make sure the XSLT based stub generation framework is up to the expected level for the alpha1 release, while Thilina will try to integrate the XSLT based framework in to the Mashup server..

Looking in to performance improvements (eg:caching the stylesheet for a particular service in the serverside) are differed to post pre 1.0..

When we get the ?stub framework in to the place, next step would be adding the ?tryit which will generate a sample HTML client which will use the above generated stub..

-- samples

-- packaging

See the following for details about the proposed packaging system. http://wso2.org/mailarchive/mashup-dev/2007-April/000252.html