Bug 779084

Summary:	Lazy lookup of EJBs in EJBProcessor
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Martin Weiler <mweiler>
Component:	JBossESB	Assignee:	Magesh Bojan <mageshbk>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0	CC:	robb.greathouse, rwagner
Target Milestone:	---
Target Release:	5.2.0 GA, 5.2.0.ER4
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1483
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	SOA-1483	Environment:
Last Closed:	2011-11-03 15:37:54 UTC	Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Weiler 2009-09-08 10:52:51 UTC

++ 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.

Comment 1 Martin Weiler 2009-09-08 10:53:52 UTC

Link: Added: This issue related JBESB-2813

Comment 2 Mark Little 2009-11-27 13:01:24 UTC

Please remember to set the Component in future.

Comment 3 Anne-Louise Tangring 2010-02-25 19:03:55 UTC

Engineering response says this will not be fixed. Please close accordingly.

Comment 5 Rick Wagner 2011-03-10 19:19:19 UTC

Modernized support case reference:

https://c.na7.visual.force.com/apex/Case_View?id=500A0000003hT8k&sfdc.override=1

Comment 6 David Le Sage 2011-08-25 22:50:00 UTC

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.

Comment 7 Jiri Pechanec 2011-11-03 15:37:54 UTC

Verified in ER6