Mailing-List: contact commits-help@openejb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openejb.apache.org
Message-ID: <1580918482.1217847404354.JavaMail.jira@brutus>
Date: Mon, 4 Aug 2008 03:56:44 -0700 (PDT)
From: "Kaloyan Raev (JIRA)" <jira@apache.org>
To: commits@openejb.apache.org
Subject: [jira] Commented: (OPENEJB-869) Publish does not work
In-Reply-To: <1068300078.1216818934208.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/OPENEJB-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619475#action_12619475 ] 

Kaloyan Raev commented on OPENEJB-869:
--------------------------------------

Hey, this works great now! Thanks!

> Publish does not work
> ---------------------
>
>                 Key: OPENEJB-869
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-869
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: eclipse
>            Reporter: Kaloyan Raev
>            Assignee: Jonathan Gallimore
>            Priority: Critical
>
> It seems that the publish functionality of the OpenEJB server adapter does not work at all. 
> Steps to reproduce:
> 1. Create an EJB 3.0 project targeted on the OpenEJB runtime. 
> 2. Create a Stateless Session bean with a Remote business interface. 
> 3. Create a JUnit test that looks up the bean via the remote business interfaces and tests the business interfaces. 
> 4. Publish the EJB project on the OpenEJB server. 
> 5. Run the JUnit test. It fails with javax.naming.NameNotFoundException: /CalculatorImplRemote does not exist in the system.  Check that the app was successfully deployed.
> 6. Export the EJB project as a JAR. 
> 7. Deploy the JAR manually on the OpenEJB server - using the "openejb.bat deploy" command. 
> 8. Run the JUnit test again from Eclipse. It runs successfully. 
> When I publish ejb modules to OpenEJB in Eclipse, the operation is extremely quickly - there is no delay. Nothing is dumped in the Console. I have the feeling that this feature is not implemented yet. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.