[ http://jira.andromda.org/browse/ANDROMDAPP-32?page=all ]
Matthias Bohlen updated ANDROMDAPP-32:
--------------------------------------
Description:
I describe here a few steps that a naive user would do to remove the need for
EJBs in her project:
When andromdapp:generate runs, it creates a project with support for EJB 2.0,
even if the user selects Spring as the preferred way to structure the
application. In the generated andromda.xml, it says:
<!-- to remove any dependency on EJB, comment the following property -->
<property name="session-ejbs">${core.generated.dir}</property>
If the user comments the property and wants to rebuild, she gets an error
message concerning ejb-jar.xml because the packaging type of the core project
is still ejb. So, the user changes core/pom.xml like this:
<packaging>jar</packaging>
Now, the whole project builds fine. However, it does not run in JBoss because
the library jars are not on the classpath any more. Before, they were on the
EJB manifest classpath. See this forum entry for the problem:
http://galaxy.andromda.org/forum/viewtopic.php?p=16864
So, I suggest to add one more question to the project generator:
"Do you want to run Spring with EJB? yes/no"
If yes, generate everything as it is now. If no, generate everything without
EJBs and still make sure that the jars are on the classpath, again.
was:
I describe here a few steps that a naive user would do to remove the need for
EJBs in her project:
When andromdapp:generate runs, it creates a project with support for EJB 2.0,
even if you select Spring as the preferred of structuring the application. In
the generated andromda.xml, it says:
<!-- to remove any dependency on EJB, comment the following property -->
<property name="session-ejbs">${core.generated.dir}</property>
If the user does this and wants to rebuild, she gets an error message
concerning ejb-jar.xml because the packaging type of the core project is still
ejb. So, the user changes core/pom.xml like this:
<packaging>jar</packaging>
Now, the whole project builds fine. However, it does not run in JBoss because
the library jars are not on the classpath any more. Before, they were on the
EJB manifest classpath. See this forum entry for the problem:
http://galaxy.andromda.org/forum/viewtopic.php?p=16864
So, I suggest to add one more question to the project generator:
"Do you want to run Spring with EJB? yes/no"
If yes, generate everything as it is now. If no, generate everything without
EJBs and still make sure that the jars are on the classpath, again.
> Add option to generate project without EJB support
> --------------------------------------------------
>
> Key: ANDROMDAPP-32
> URL: http://jira.andromda.org/browse/ANDROMDAPP-32
> Project: AndroMDApp Project Generator
> Type: Improvement
> Reporter: Matthias Bohlen
> Assignee: Chad Brandon
>
> I describe here a few steps that a naive user would do to remove the need for
> EJBs in her project:
> When andromdapp:generate runs, it creates a project with support for EJB 2.0,
> even if the user selects Spring as the preferred way to structure the
> application. In the generated andromda.xml, it says:
> <!-- to remove any dependency on EJB, comment the following property -->
> <property name="session-ejbs">${core.generated.dir}</property>
> If the user comments the property and wants to rebuild, she gets an error
> message concerning ejb-jar.xml because the packaging type of the core project
> is still ejb. So, the user changes core/pom.xml like this:
> <packaging>jar</packaging>
> Now, the whole project builds fine. However, it does not run in JBoss because
> the library jars are not on the classpath any more. Before, they were on the
> EJB manifest classpath. See this forum entry for the problem:
> http://galaxy.andromda.org/forum/viewtopic.php?p=16864
> So, I suggest to add one more question to the project generator:
> "Do you want to run Spring with EJB? yes/no"
> If yes, generate everything as it is now. If no, generate everything without
> EJBs and still make sure that the jars are on the classpath, again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
