You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2005/10/02 07:01:48 UTC
[jira] Closed: (GERONIMO-1024) Null Pointer exception thrown if message destination specifies an incorrect module name.
[ http://issues.apache.org/jira/browse/GERONIMO-1024?page=all ]
David Jencks closed GERONIMO-1024:
----------------------------------
Fix Version: 1.0
Resolution: Fixed
Hmmm I guess I could have made you apply this :-)
Fixed only in head, to late for M5
Sending modules/j2ee-builder/src/java/org/apache/geronimo/j2ee/deployment/RefContext.java
Transmitting file data .
Committed revision 293071.
> Null Pointer exception thrown if message destination specifies an incorrect module name.
> -----------------------------------------------------------------------------------------
>
> Key: GERONIMO-1024
> URL: http://issues.apache.org/jira/browse/GERONIMO-1024
> Project: Geronimo
> Type: Bug
> Versions: 1.0-M5
> Environment: All
> Reporter: Matt Hogstrom
> Assignee: David Jencks
> Priority: Minor
> Fix For: 1.0
> Attachments: refcontext.diff
>
> In working on converting daytrader I found that the module name tradeEJB was incorrect as I renamed the jar. When deploying I received an NPE during deployment because of the incorrect module name. I added code to handle this condition and put out a more meaningful message to assist in diagnosing the problem. Here is modified output
> 10:33:37,984 DEBUG [Deployer] Deployment failed: plan=/home/hogstrom/geronimo/geronimo/sandbox/daytrader/dayTrader-plan.xml, module=/home/hogstrom/.maven/repository/
> org.apache.geronimo.common.DeploymentException: Unknown module tradeEJB.jar when processing message destination tradeEJB.jar#TradeBrokerQueue
> Known mdules in deployable unit are:
> daytrader-ejb-1.0-SNAPSHOT.jar
> daytrader-web-1.0-SNAPSHOT.war
> at org.apache.geronimo.j2ee.deployment.RefContext.getMessageDestination(RefContext.java:151)
> at org.apache.geronimo.naming.deployment.ENCConfigBuilder.addMessageDestinationRefs(ENCConfigBuilder.java:347)
> The original exception was an NPE with no helpful info.
--
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