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 "Paul Fremantle (JIRA)" <ji...@apache.org> on 2005/10/31 18:02:55 UTC
[jira] Created: (AXIS2-298) Underlying Repository store should be flexible behind an interface
Underlying Repository store should be flexible behind an interface
------------------------------------------------------------------
Key: AXIS2-298
URL: http://issues.apache.org/jira/browse/AXIS2-298
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: deployment
Versions: 0.93
Environment: Any
Reporter: Paul Fremantle
Currently the repository must be stored in a physical filesystem using java.io.File etc. We have already seen problems in certain Servlet containers.
The repository Store API should be abstracted out so that different implementations of a repository store can be used underneath the repository code.
One possibility is JSR170 - but an initial simple interface would also be acceptable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-298) Underlying Repository store should be
flexible behind an interface
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-298?page=comments#action_12364426 ]
Deepal Jayasinghe commented on AXIS2-298:
-----------------------------------------
Pual ;
How about following approach ;
1. If you can put your modules (like Addressing , RM etc) in the class path (it should be there in the same folder that ur axis2.jar is there) , then I can provide a way to run axis2 without having a repository , according to this ur class path directory will look like follow;
axis2-core.jar
addressing-0.94.mar
sandesha-1.0.mar
any comments
and other thing is I can nicely support module versioning as well with this approach.
> Underlying Repository store should be flexible behind an interface
> ------------------------------------------------------------------
>
> Key: AXIS2-298
> URL: http://issues.apache.org/jira/browse/AXIS2-298
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: deployment
> Versions: 0.93
> Environment: Any
> Reporter: Paul Fremantle
>
> Currently the repository must be stored in a physical filesystem using java.io.File etc. We have already seen problems in certain Servlet containers.
> The repository Store API should be abstracted out so that different implementations of a repository store can be used underneath the repository code.
> One possibility is JSR170 - but an initial simple interface would also be acceptable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXIS2-298) Underlying Repository store should be
flexible behind an interface
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-298?page=all ]
Deepal Jayasinghe resolved AXIS2-298:
-------------------------------------
Fix Version: 0.95
Resolution: Fixed
by implementing AxisConfigurator we can get the reuired feature.
> Underlying Repository store should be flexible behind an interface
> ------------------------------------------------------------------
>
> Key: AXIS2-298
> URL: http://issues.apache.org/jira/browse/AXIS2-298
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: deployment
> Versions: 0.93
> Environment: Any
> Reporter: Paul Fremantle
> Fix For: 0.95
>
> Currently the repository must be stored in a physical filesystem using java.io.File etc. We have already seen problems in certain Servlet containers.
> The repository Store API should be abstracted out so that different implementations of a repository store can be used underneath the repository code.
> One possibility is JSR170 - but an initial simple interface would also be acceptable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira