[esb-issues] [JBoss JIRA] Commented: (JBESB-1751) StandAloneBootStrapper doesn't initialise the Registry instance in the RegistryFactory

Tue May 20 04:28:59 EDT 2008

    [ http://jira.jboss.com/jira/browse/JBESB-1751?page=comments#action_12413307 ] 

Tom Fennelly commented on JBESB-1751:
-------------------------------------

That's very interesting Kev.... I pointed this out to you before (about the RegistryFactory repeatedly creating the Reg instance) and you disregarded the suggestion that this was not right, saying it was the responsibility of the deployer to do it - end of story.... not a matter of opinion etc etc etc ;-)  This is why I didn't make the change there lol

Anyway... why is it needed... because, as you said rightly in your follow up comment... if it's not initialised, it repeatedly creates the registry instance.  Why is this an issue for Standalone and not AS/ESB deployments, because as stated above, the deployers in ESB/AS perform the initialiation (in exactly the same way as I've added it to the Standalone).  If it's not intitialised... the InVM transport breaks because it uses an invm registry.

I'll reassign to yourself and you can fix it the "right" way ;-)

> StandAloneBootStrapper doesn't initialise the Registry instance in the RegistryFactory
> --------------------------------------------------------------------------------------
>
>                 Key: JBESB-1751
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1751
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta, Registry and Repository
>    Affects Versions: 4.2.1 TP-FP1
>            Reporter: Tom Fennelly
>         Assigned To: Tom Fennelly
>             Fix For: 4.3
>
>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira