axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (AXIS2-3026) New AxisConfigurator that operates within the aar file
Date Fri, 27 Jul 2007 11:29:19 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Deepal Jayasinghe reassigned AXIS2-3026:
----------------------------------------

    Assignee: Deepal Jayasinghe

> New AxisConfigurator that operates within the aar file
> ------------------------------------------------------
>
>                 Key: AXIS2-3026
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3026
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Wish
>          Components: kernel
>    Affects Versions: nightly
>         Environment: Not specific
>            Reporter: Mark Badorrek
>            Assignee: Deepal Jayasinghe
>             Fix For: nightly
>
>
> Currently there are several AxisConfigurators:
> FileSystemConfigurator
> URLBasedAxisConfigurator
> etc
> I feel that we also need an AxisConfigurator that can read an axis_client.xml file and
client repository that are stored in the aar file. This would allow an axis service to make
client-calls to other axis services using different configurations from the parent configuration.
> For example:
> I have an axis service 'foo' that is a plain old websevice - nothing special. Now consider
that it has been invoked by a client.
> 'foo' must now make a couple of webservice calls of its own, but this time it will (for
example) engage 'rampart' and disengage'addressing' for both of its client calls. As such
each configuration will have its own rampart callback classes etc.
> Currently there is no way to include the required 'client1_axis2.xml', client1_repository',
'client2_axis2.xml', client2_repository', within the aar file and have them loaded.
> I'd like to see an 'ServiceClassloaderAxisConfigurator' to allow these artifacts to be
stored within the aar file so that the entire 'foo' webservice is a single file deploy.
> The 'client1_AxisConfiguration' and  'client1_AxisConfiguration'  should also be cached
as there is a high probability that they will be required agin and again.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


Mime
View raw message