[ http://jira.andromda.org/browse/SPRING-171?page=all ]
Jens Vagts closed SPRING-171:
-----------------------------
Fix Version: 3.2-RC1
Resolution: Fixed
> ServiceLocator template: always use "beanRefFactory" as default id even with
> EJB enabled
> ----------------------------------------------------------------------------------------
>
> Key: SPRING-171
> URL: http://jira.andromda.org/browse/SPRING-171
> Project: Spring Cartridge
> Type: Bug
> Versions: 3.2-RC1
> Reporter: Jens Vagts
> Assignee: Jens Vagts
> Fix For: 3.2-RC1
>
> Currently the "beanRefFactoryEjb" reference is used as default if EJB
> generation is enabled. This does not realy make sense: beanRefFactoryEjb
> contains the remote ejb client access configuration for the (local) server
> app. So it's unusable by any server code. Currently the WebService cartridge
> can not be used togeher remote ejb access, since the generated service
> delegator use exactly this functionality.
> I would prefer to always use the (local) "beanRefFactory" as reference id
> for all cases even with ejb enabled. If the ServiceLocator is used on client
> side for remote access it has to be initialized with the remote address
> anyway by client code.
> This should not break on any site, since it hasn't worked correctly
> (ServiceLocator for local access with remote ejb anabled) and seems not to
> be used anywhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
