[forge-issues] [JBoss JIRA] (FORGE-604) Add support for Java EE 6 Full Profile

[Christopher Volk (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735511#comment-12735511 ] 

Christopher Volk commented on FORGE-604:
----------------------------------------

So my 6 month, 70/hr/wk project is done, and recovery efforts here in New York City have progressed to the point where I have a little time.  Since I see this issue has been promoted to the next release, I thought today would be a good time to add something here:

Forge issues when trying to create Java EE Full Profile App

Testing env:
- Oracle JDK 7u9
- Forge 1.1.2
- Ubuntu 12.10

Issue #1:
--------
No applicable project "type":

[no project] forge $ new-project --named Testing2 --type 
pom       jar       war       bundle


Issue #2:
--------
If one chooses the closest option for "type" (war), then you get just that, a simple project dir with a src dir and a pom.xml setup for a .war.  Once that is there, you can do an ejb setup (I assume this is setup in forge to use the Web Profile's "EJB Lite"?), but there is no "ear setup" or similar.  I don't see any way to work around issue #1 by creating the modular structure of a full profile app from a project created using forge's war "type".

Thoughts: 
--------
I'm not sure I've added much value here other than to show that you can't progress past getting a full profile project setup in place, and so other issues are mostly speculation at this point.  I've only looked at a small portion of the source code, but I'm thinking that the --type setting for projects influences how many/most things are executed within forge as the locations and configuration of many things depend on the project type.  With full profile apps being modular, forge would need module-oriented commands as well - add/update/delete of new ejb modules, war modules, ear-level dependencies, etc. would be specific to full profile project setups.

One thought on implementing module management - it would be great to allow for having multiple ejb modules to the point such that you could, for example, keep your entities in one and your business logic in another (I know I require this on some projects) :-)

I would think that 'project *-dependency' would need to be a bit smarter when dealing with ear's multi-module setup since you can have app-level dependencies as well as module-level dependencies.
                
> Add support for Java EE 6 Full Profile
> --------------------------------------
>
>                 Key: FORGE-604
>                 URL: https://issues.jboss.org/browse/FORGE-604
>             Project: Forge
>          Issue Type: Task
>          Components: Java EE APIs
>    Affects Versions: 1.0.5.Final
>         Environment: All
>            Reporter: Christopher Volk
>             Fix For: 1.1.3.Final
>
>
> Add support for Java EE 6 Full profile, including multi-module support (cli/maven/ear) and EAR packaging.
> The EAR packaging should be fairly "easy" to implement.  The maven side of multi-module should be similarly "easy".  CLI multi-module support is something I would expect to take up most of this effort.
> I believe this to be a critical feature - serious enterprise software requires Full Profile, and Forge would be even more useful for bootstrapping and developing against the Full Profile than even the Web Profile.  I know that almost all the apps I work on professionally require Full Profile.  
> This would be a real home run, IMHO, especially in the wake of JBoss AS7.1's Full Profile Compliance :-)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira