[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1269) Support for remotely deployed EJBs
by Roland Räz (JIRA)
Support for remotely deployed EJBs
----------------------------------
Key: JBSEAM-1269
URL: http://jira.jboss.com/jira/browse/JBSEAM-1269
Project: JBoss Seam
Issue Type: Feature Request
Components: EJB3
Affects Versions: 1.2.1.GA
Reporter: Roland Räz
We found that Seam currently has only weak support for remotely located EJBs. The only way to get to a remotely located EJB reference is to use a façade or a factory, which forces us to write unnecessary glue code. A typical use case would be a stateless SOA service, which is usually deployed remotely. This remote service might not even use Seam.
We would like to see Seam support component declarations for interfaces + jndi-name in components.xml (as opposed to class + jndi-name). This would allow Seam to find remote components, which could be referenced through the EL. Obviously no in-/outjection would work, which is usually not required for stateless remote services.
This feature request has been already discussed in the Seam Forum.
--
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
14 years, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1233) Extend @Scope to work on member variables/properties
by Andrew (JIRA)
Extend @Scope to work on member variables/properties
----------------------------------------------------
Key: JBSEAM-1233
URL: http://jira.jboss.com/jira/browse/JBSEAM-1233
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 1.1.6.GA
Reporter: Andrew
I have a relate bug:
http://jira.jboss.com/jira/browse/JBSEAM-903
My purpose for this bug was mostly due to binding issues. There are times that I want to have the scope of a member variable to be different from the scope of the bean. Especially, if the bean is conversational and I want the field/property to have event scope. Instead of the proposed @InOut from the above bug, perhaps just extending @Scope would work:
@Scope(ScopeType.EVENT)
private MyVar myVar;
Unlike @In and @Out, this scope would not put use the contexts to get and set values, but simply control the lifecycle of the variable. In this example, myVar could be set to null when the the variables of the bean are out-jected. As it stands, there is no other easy way that I know of to have a variable set to null at then end of a page request.
--
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
14 years, 11 months