[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
by Siarhei Dudzin (JIRA)
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: http://jira.jboss.com/jira/browse/JBSEAM-2286
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Priority: Critical
As specified in the forum reference I have an MDB which uses a SLSB (also declared as Seam component) with business logic. If I deploy the application and there are already messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me to use vendor-specific API.
--
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
13 years, 1 month
[JBoss JIRA] (JBSEAM-4978) Seam-gen commands using hibernate-tools doesn't work
by Tomas Remes (JIRA)
Tomas Remes created JBSEAM-4978:
-----------------------------------
Summary: Seam-gen commands using hibernate-tools doesn't work
Key: JBSEAM-4978
URL: https://issues.jboss.org/browse/JBSEAM-4978
Project: Seam 2
Issue Type: Bug
Components: Tools
Affects Versions: 2.3.0.BETA2
Reporter: Tomas Remes
Fix For: 2.3.0.CR1
Seam-gen commands like "generate-model","generate", "generate-ui" does not work, because it's using old hibernate-tools version. Major problem is that this old version is using classes from hibernate-core 3.2.4 (and probably many other jars) and those are not compatible with hibernate 4 versions. So when you try for example command "generate-model", you will get following error:
{noformat}
jboss-seam-2.3.0.CR1-SNAPSHOT/seam-gen/build.xml:1554: java.lang.NoClassDefFoundError: org/hibernate/engine/Mapping
{noformat}
I am trying/investigating how is this used in JBoss Tools, but as far as I've understood there is entirely bundled old hibernate 3 and its related stuff.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBSEAM-5002) Components included with ui:include src="#{pageScopedViewId} broken
by Marek Schmidt (JIRA)
Marek Schmidt created JBSEAM-5002:
-------------------------------------
Summary: Components included with ui:include src="#{pageScopedViewId} broken
Key: JBSEAM-5002
URL: https://issues.jboss.org/browse/JBSEAM-5002
Project: Seam 2
Issue Type: Bug
Components: JSF Integration
Affects Versions: 2.3.0.BETA2
Environment: JBoss AS 7.1.2, Seam 2.3.0.CR1-SNAPSHOT (r14986)
Reporter: Marek Schmidt
Assignee: Marek Novotny
Fix For: 2.3.0.CR1
The following scenario that used to work in AS5/Seam2.2 doesn't work anymore in AS7/Seam2.3 for page-scoped and conversation-scoped "viewId" components:
index.xhtml:
{code}
<h:form>
<h:commandButton action="#{viewId.component1}" value="Component 1" />
<h:commandButton action="#{viewId.component2}" value="Component 2" />
</h:form>
<ui:include src="#{viewId.viewId}"/>
{code}
{code}
@Scope(ScopeType.PAGE)
@Name("viewId")
public class ViewIdComponent implements Serializable
{
private String viewId = "/component1.xhtml";
public void setViewId(String viewId) {
this.viewId = viewId;
}
public String getViewId() {
return viewId;
}
public void component1() {
setViewId("/component1.xhtml");
}
public void component2() {
setViewId("/component2.xhtml");
}
}
{code}
(compoent1 and 2 are redacted, contain a simple form)
Only the first component works properly, actions in "component2" doesn't seem to be called after switching to "Component 2".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (JBSEAM-4693) 6.12.2. Enabling Seam exception handling : web:exception-filter in components.xml
by simon lebettre (JIRA)
6.12.2. Enabling Seam exception handling : web:exception-filter in components.xml
---------------------------------------------------------------------------------
Key: JBSEAM-4693
URL: https://jira.jboss.org/browse/JBSEAM-4693
Project: Seam
Issue Type: Task
Components: Documentation Issues
Reporter: simon lebettre
this does not make sense :
"
6.12.2. Enabling Seam exception handling
To enable Seam's exception handling, we need to make sure we have the master servlet filter declared in web.xml:
"
==> Of course the master filter is in web.xml !
this would be more relevant :
"we need to make sure that <web:exception-filter url-pattern="*.seam" /> is declared in components.xml"
I m not being picky about the doc, it's been 7 months I have a bad user experience or loose some exception feedback because I forgot this line in components.xml !
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months