axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Assigned: (AXIS2-2195) Expose module's classes outside of the module
Date Thu, 24 May 2007 14:49:16 GMT


Davanum Srinivas reassigned AXIS2-2195:

    Assignee: Davanum Srinivas

> Expose module's classes outside of the module
> ---------------------------------------------
>                 Key: AXIS2-2195
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: modules
>         Environment: All
>            Reporter: Dug
>         Assigned To: 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:
For additional commands, e-mail:

View raw message