++ This bug is a clone of bug 779083 ++ Date of First Response: 2009-11-27 08:01:24 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/339503 project_key: SOA Platform issue for JBESB-2813: EJBProcessor performs lookup of remote EJBs at application startup. If the lookup fails, EJBProcessor throws an exception, so that the whole application cannot start. This should be changed to a lazy lookup.
Link: Added: This issue related JBESB-2813
Please remember to set the Component in future.
Engineering response says this will not be fixed. Please close accordingly.
Modernized support case reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000003hT8k&sfdc.override=1
Release Notes Docs Status: Added: Documented as Resolved Issue Writer: Added: dlesage Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-2813 The EJBProcessor looked for remote EJBs at application startup. If the look-up failed, the EJBProcessor threw an exception, meaning that the application could not start. The code, simply did a look-up at the outset and reused the proxy to invoke methods on the target EJB. It has now been changed so that it can handle remoted EJBs. As a result, no exception is encountered and the application starts correctly.
Verified in ER6