Suggestion: New type of scope

[ru...@enabler.com]

Hi all,
 
I am sending you this mail to suggest a new type of scope to the axis
webservice.
 
I am developing a webservice and I discovered that I need a new type of
scope to grow the performance of my webservice.
Probably, you have thought on this, and you have a good reason to not
implement it.
 
However, I will describe my webservice.
 
My webservice provides a service, that makes available a method which
receives two identifiers (two integers) and a string that contains a
xml. This method makes the following tasks;
 
    - Parse the xml (using xerces);
    - Validate the xml against a xml schema;
    - Evaluate some xpath expressions (using xalan);
    - Invoke  an oracle store procedure, which inserts the xml in an
Oracle queue, if the xml is in accordance with the XML schema.
 
As you can see, the method provided is very simple.
 
So, my service has a Request scope, which creates a new instance of the
class, each time is made a new Request.
 
As you now, instantiating new classes is a heavy operation, because it
is necessary to allocate memory, and reusing old instances is a good
practice.
 
So, what I suggest is to develop a "Classes pool" scope, that creates a
number of instances at startup, and reuse them each time a new request
comes.
 
This new type of scope must be configured, with some parameters, e.g:
 
        - Minimum number of instances;
        - Minimum idle instances;
        - Maximum number of instances;
        - and others .... 
 
To make this reutilization  possible, all the deployed classes must have
a reset method which cleans the object, making the object ready for
reutilization.
 
 
Regards,
 
Rui Torres

Re: New feature to enhance in support of ?wsdl

[keith chapman <ke...@gmail.com>]

I guess the better solution might be to use the AxisBinding hierarchy
introduced while integrating WSDL 2.0 changes. Currently the
services.xmldoes not populate the Binding hierarchy but keeps all the
details in the
AxisService. It might be a better solution to populate 3 bindings by default
(namely SOAP 1.1, SOAP 1.2 and HTTP) and customize it based on properties in
the services.xml.

When ?wsdl or ?wsdl2 is called we look for binding hierarchy, and if its
present we serialize them. If its not present we generate 3 default
bindings. So if the above is incorporated we would automatically get a WSDL
that the user desires.

Using the binding hierarchy has other benefits, such as been able to
customize a particular binding without effecting the others. I certainly
think that we should be using the Binding hierarchy when building services
from the services.xml.

Thanks,
Keith.

On 8/10/07, Davanum Srinivas <da...@gmail.com> wrote:
>
> Yes, please create a JIRA, if there are some overlapping ones, we'll
> link them or close them.
>
> thanks,
> dims
>
> On 8/9/07, Nadir Amra <am...@us.ibm.com> wrote:
> > Hi all,
> >
> > I believe that it would be a very useful feature if  we controlled the
> > generation of what WSDL bindings is returned in a WSDL document by AXIS
> 2
> > (when one does not exist) from within the services.xml file.  One can
> > indicate through a parameter whether SOAP11, SOAP12, HTTP, ALL, etc.
> > binding are to be returned.
> >
> > I presume there is no such feature in current implementation and was
> > wondering if it would be a good idea to open JIRA if it is feasible so
> > that maybe it can be added in a future release?
> >
> >
> >
> > Nadir K. Amra
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> 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: New feature to enhance in support of ?wsdl

[Davanum Srinivas <da...@gmail.com>]

Yes, please create a JIRA, if there are some overlapping ones, we'll
link them or close them.

thanks,
dims

On 8/9/07, Nadir Amra <am...@us.ibm.com> wrote:
> Hi all,
>
> I believe that it would be a very useful feature if  we controlled the
> generation of what WSDL bindings is returned in a WSDL document by AXIS 2
> (when one does not exist) from within the services.xml file.  One can
> indicate through a parameter whether SOAP11, SOAP12, HTTP, ALL, etc.
> binding are to be returned.
>
> I presume there is no such feature in current implementation and was
> wondering if it would be a good idea to open JIRA if it is feasible so
> that maybe it can be added in a future release?
>
>
>
> Nadir K. Amra
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

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

New feature to enhance in support of ?wsdl

[Nadir Amra <am...@us.ibm.com>]

Hi all, 

I believe that it would be a very useful feature if  we controlled the 
generation of what WSDL bindings is returned in a WSDL document by AXIS 2 
(when one does not exist) from within the services.xml file.  One can 
indicate through a parameter whether SOAP11, SOAP12, HTTP, ALL, etc. 
binding are to be returned. 

I presume there is no such feature in current implementation and was 
wondering if it would be a good idea to open JIRA if it is feasible so 
that maybe it can be added in a future release? 



Nadir K. Amra


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