[ http://issues.apache.org/jira/browse/GERONIMO-1526?page=all ]
Sachin Patel updated GERONIMO-1526:
-----------------------------------
Summary: Allow module builders to support building configuraiton
from non-j2ee structure. (was: Suppot for running applications directly from a
development enviornment)
Description:
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.
was:In order for the runtime to have better integration for a
tooling/development environment we need the runtime to be able to run modules
and their resources directly from a users development environment without
having to package it. Currently, if a single source file changes the entire
EAR must be exported and redeployed. This is not a long term solution and in
past experiences this can lead to severe performance issues hindering a users
development experience.
Affects Version/s: 1.1.1
(was: 1.x)
Assignee: (was: Sachin Patel)
Priority: Critical (was: Major)
> 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
