You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Delos Dai (JIRA)" <ji...@apache.org> on 2009/09/02 11:42:32 UTC
[jira] Closed: (GERONIMODEVTOOLS-289) Unable to deploy EJB
application on AG 2.1 through Eclipse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Delos Dai closed GERONIMODEVTOOLS-289.
--------------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
2.1.5
As viola said, the problem can't reproduced in latest version. So close it.
> Unable to deploy EJB application on AG 2.1 through Eclipse
> ----------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-289
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-289
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 2.1.3
> Environment: WTP 2.0.1(which has all the required artifacts), AG 2.1, GEP 2.1(unstable)
> Reporter: Ashish Jain
> Assignee: Tim McConnell
> Fix For: 2.1.5, 2.2.0
>
>
> Steps to recreate the error
> 1) Create an EJB project through Eclipse.
> 2) Deploy the project on to AG 2.1 through Eclipse.
> 3) Now try to access the EJB through a application Client.
> 4) You get the following error
> javax.naming.NameNotFoundException: /CountryCapitalBeanRemote does not exist in the system. Check that the app was successfully deployed.
> This error suggests that there is no bean deployed on the server.
> 5) On verfying the same through the administrative console. We find that an EJB has not been deployed on the server.
> Also after deploying EJB through eclipse there is a warning message on the console tab
> 23:13:04,734 WARN [RenderConfig] Couldn't find a PageConfig for page ID: [/welcome]
> The workaround is to export EJB as a jar and deploy on the server through administrative console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.