[
https://issues.apache.org/jira/browse/AXIS2-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2195.
--------------------------------------
Resolution: Fixed
We can not implement this , since module get its own class loader so how can we
share data across classloaders . If you want to have this features then as you
have mentioned create separate jar and put that into class path.
> Expose module's classes outside of the module
> ---------------------------------------------
>
> Key: AXIS2-2195
> URL: https://issues.apache.org/jira/browse/AXIS2-2195
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: modules
> Environment: All
> Reporter: Dug
> Assignee: Davanum Srinivas
> Priority: Minor
>
> The way modules are currently designed, only the module code has access to
> the classes within the module.
> This means that utility classes in the module, that may be needed by
> application code (or anything else outside of the module) can not get to
> them. The only solution now is to create a separate jar file for these
> classes and carry them around independent of the *.mar file. this isn't very
> user friendly.
> It also assumes that the utility jar can be small enough to extract from the
> rest of the module code without needing to pull in everything - a bad
> assumption.
> It would be nice if a module were more like a jar file and can be in the
> normal classpath - thus making it available, as needed and people can still
> move around just one consolidated artifact when they want to deploy a module.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
