[ 
http://issues.apache.org/jira/browse/GERONIMO-1526?page=comments#action_12428319
 ] 
            
Oleg Gusakov commented on GERONIMO-1526:
----------------------------------------

If you look at the issue from a little wider angle - it has nothing to do with 
any "exceptions" to JavaEE structure. JavaEE defines resolution structure for 
some pre-defined module types - EAR, WAR. But it also adhears to JavaSE 
classloading mechanism: looking for a class - ask parent classloader. Of cause 
- we made it more flexible here by allowing to first check module's classloader 
cache as an option.

So in essence what's stated here as well as in GERONIMODEVTOOLS-99 which seems 
to be blocked because of this one - make regular module builder flexible, able 
to resolve resources from either remote folder ("in-place deployment") and most 
problems go away.

The only real issue that may need to be solved - in IDE environment standard 
EAR or WAR structure may be split into physically different locations before 
it's finalized by the build process. In this case module builder has to do real 
"building" - assemble those pieces togerther into a compiant structure. The 
easiest solution to that might be, say, using OS level hack - symbolic links on 
the filesystem level. (Don't know if it's possible unde windows, though)

> Allow module builders to support building configuraiton from non-j2ee 
> structure.
> --------------------------------------------------------------------------------
>
>                 Key: GERONIMO-1526
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-1526
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 1.1.1
>            Reporter: Sachin Patel
>            Priority: Critical
>             Fix For: 1.x
>
>
> See the section Geronimo Runtime Requirements in the link for a detailed 
> description 
> http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-development-roadmap.html
> In summary...
> - The module builders should not assume and cannot be passed in a jar file.
> - The module builders should not locate resources by assuming that the root 
> location passed in is an J2EE file structure
> - Need to provide an abstraction of an ear/module one impl which would be by 
> default is a J2EE structure, otherwise support a pluggable method to allow 
> support for different IDEs.

-- 
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

        

Reply via email to