[JBoss JIRA] (SEAMTRANSACTION-2) thread is already associated with a transaction
by Gaetano Mazzeo (JIRA)
[ https://issues.jboss.org/browse/SEAMTRANSACTION-2?page=com.atlassian.jira... ]
Gaetano Mazzeo updated SEAMTRANSACTION-2:
-----------------------------------------
Attachment: server.zip
> thread is already associated with a transaction
> -----------------------------------------------
>
> Key: SEAMTRANSACTION-2
> URL: https://issues.jboss.org/browse/SEAMTRANSACTION-2
> Project: Seam Transaction
> Issue Type: Bug
> Affects Versions: 3.1.0.Beta1
> Environment: Jboss as 7
> Seam 3 (latest beta)
> jsf 2
> richface 4
> hibernate 4
> Reporter: Trevor Sweeney
> Attachments: server.zip
>
>
> I am migrating a large app from seam 2 to 3. We have some large portions of the site working with a nagging issue.
> When a page is loaded, after the default transaction timeout fires the server cannot server any more requests because of the below error:
> Environment: Jboss AS 7.0.1 Seam 3 Hibernate 4 Jsf 2 Richafaces 4
> 20:26:33,061 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA12127: TwoPhaseCoordinator.afterCompletion - returned failure for SynchronizationImple< 0:ffff0a84403a:-3c589bf9:4e6ea2ca:30, org.jboss.seam.transaction.TransactionManagerSynchronizations@95f259 >
> 20:26:33,061 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA12121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffff0a84403a:-3c589bf9:4e6ea2ca:2a
> 20:26:53,671 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/webstore].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: java.lang.IllegalStateException: BaseTransaction.checkTransactionState - thread is already associated with a transaction!
> at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.checkTransactionState(BaseTransaction.java:259)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:61)
> at org.jboss.seam.transaction.UTTransaction.begin(UTTransaction.java:51) [seam-transaction-3.1.0.Beta2.jar:]
> at org.jboss.seam.transaction.DefaultSeamTransaction.begin(DefaultSeamTransaction.java:87) [seam-transaction-3.1.0.Beta2.jar:]
> at org.jboss.seam.faces.transaction.TransactionPhaseListener.begin(TransactionPhaseListener.java:108) [seam-faces-3.1.0.Beta2.jar:]
> at org.jboss.seam.faces.transaction.TransactionPhaseListener.begin(TransactionPhaseListener.java:101) [seam-faces-3.1.0.Beta2.jar:]
> at org.jboss.seam.faces.transaction.TransactionPhaseListener.handleTransactionsBeforePhase(TransactionPhaseListener.java:82) [seam-faces-3.1.0.Beta2.jar:]
> at org.jboss.seam.faces.transaction.TransactionPhaseListener.beforePhase(TransactionPhaseListener.java:64) [seam-faces-3.1.0.Beta2.jar:]
> at org.jboss.seam.faces.event.DelegatingPhaseListener.beforePhase(DelegatingPhaseListener.java:43) [seam-faces-3.1.0.Beta2.jar:]
> at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
> at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:111) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
> at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:312) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:118) [prettyfaces-jsf2-3.3.0.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:734) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:541) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:479) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:407) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:110) [prettyfaces-jsf2-3.3.0.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.seam.servlet.exception.CatchExceptionFilter.doFilter(CatchExceptionFilter.java:65) [seam-servlet-3.1.0.Beta2.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.seam.servlet.event.ServletEventBridgeFilter.doFilter(ServletEventBridgeFilter.java:72) [seam-servlet-3.1.0.Beta2.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at java.lang.Thread.run(Thread.java:619) [:1.6.0_20]
> 20:26:53,671 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/webstore].[default]] (http--127.0.0.1-8080-1) Servlet.service() for servlet default threw exception: java.lang.IllegalStateException: BaseTransaction.checkTransactionState - thread is already associated with a transaction!
> at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.checkTransactionState(BaseTransaction.java:259)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:61)
> at org.jboss.seam.transaction.UTTransaction.begin(UTTransaction.java:51) [seam-transaction-3.1.0.Beta2.jar:]
> at org.jboss.seam.transaction.DefaultSeamTransaction.begin(DefaultSeamTransaction.java:87) [seam-transaction-3.1.0.Beta2.jar:]
> at org.jboss.seam.faces.transaction.TransactionPhaseListener.begin(TransactionPhaseListener.java:108) [seam-faces-3.1.0.Beta2.jar:]
> at org.jboss.seam.faces.transaction.TransactionPhaseListener.begin(TransactionPhaseListener.java:101) [seam-faces-3.1.0.Beta2.jar:]
> at org.jboss.seam.faces.transaction.TransactionPhaseListener.handleTransactionsBeforePhase(TransactionPhaseListener.java:82) [seam-faces-3.1.0.Beta2.jar:]
> at org.jboss.seam.faces.transaction.TransactionPhaseListener.beforePhase(TransactionPhaseListener.java:64) [seam-faces-3.1.0.Beta2.jar:]
> at org.jboss.seam.faces.event.DelegatingPhaseListener.beforePhase(DelegatingPhaseListener.java:43) [seam-faces-3.1.0.Beta2.jar:]
> at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
> at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:111) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
> at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:312) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:118) [prettyfaces-jsf2-3.3.0.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:734) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:541) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:479) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:407) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:110) [prettyfaces-jsf2-3.3.0.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.seam.servlet.exception.CatchExceptionFilter.doFilter(CatchExceptionFilter.java:65) [seam-servlet-3.1.0.Beta2.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.seam.servlet.event.ServletEventBridgeFilter.doFilter(ServletEventBridgeFilter.java:72) [seam-servlet-3.1.0.Beta2.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at java.lang.Thread.run(Thread.java:619) [:1.6.0_20]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months
[JBoss JIRA] (JBSEAM-3938) Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them.
by Sean Flanigan (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-3938?page=com.atlassian.jira.plugi... ]
Sean Flanigan edited comment on JBSEAM-3938 at 9/12/13 3:02 AM:
----------------------------------------------------------------
(I'm assuming "tagged interfaces" refers to interfaces which have JAX-RS annotations.)
I ran into a related problem with this set up in Seam 2.3:
{code}
@Path("/accounts")
public interface AccountsResource {
@GET
public Response get();
}
@Path("/accounts")
@Name("accountsService")
public class AccountsService implements AccountsResource {
@Context
private Request request;
@Override
@GET
public Response get()
{
// use request for something -> NullPointerException
}
}
{code}
If the bean implements an interface which is annotated @Path, the @Context is not injected.
was (Author: sflanigan):
(I'm assuming "tagged interfaces" refers to interfaces which have JAX-RS annotations.)
I ran into a related problem with this set up in Seam 2.3:
{code}
@Path("/accounts")
public interface AccountsResource {
@GET
public Response get();
}
@Path("/accounts")
@Name("accountsService")
public class AccountsService implements AccountsResource {
@Context
private Request request;
@GET
public Response get()
{
// use request for something -> NullPointerException
}
}
{code}
If the bean implements an interface which is annotated @Path, the @Context is not injected.
> Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them.
> ---------------------------------------------------------------------------------------------------
>
> Key: JBSEAM-3938
> URL: https://issues.jboss.org/browse/JBSEAM-3938
> Project: Seam 2
> Issue Type: Bug
> Components: WS
> Affects Versions: 2.1.1.GA
> Environment: SEAM 2.1.1.GA with seam-resteasy patch described in https://jira.jboss.org/jira/browse/JBSEAM-3449, and RestEasy 1.0.1.GA.
> Reporter: John Sublette
> Assignee: Jozef Hartinger
> Priority: Minor
> Labels: RestEasy
>
> Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them as described in RestEasy's documentation (section 28.2 - Sharing an interface...). An interface with tagged @Path throws an exception when it is registered - because an interface doesn't have a constructor.
> See org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap Line 112 through 138 for how RestEasy handles this by default - (using Scannotation)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBSEAM-3938) Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them.
by Sean Flanigan (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-3938?page=com.atlassian.jira.plugi... ]
Sean Flanigan commented on JBSEAM-3938:
---------------------------------------
(I'm assuming "tagged interfaces" refers to interfaces which have JAX-RS annotations.)
I ran into a related problem with this set up in Seam 2.3:
{code}
@Path("/accounts")
public interface AccountsResource {
@GET
public Response get();
}
@Path("/accounts")
@Name("accountsService")
public class AccountsService implements AccountsResource {
@Context
private Request request;
@GET
public Response get()
{
// use request for something -> NullPointerException
}
}
{code}
If the bean implements an interface which is annotated @Path, the @Context is not injected.
> Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them.
> ---------------------------------------------------------------------------------------------------
>
> Key: JBSEAM-3938
> URL: https://issues.jboss.org/browse/JBSEAM-3938
> Project: Seam 2
> Issue Type: Bug
> Components: WS
> Affects Versions: 2.1.1.GA
> Environment: SEAM 2.1.1.GA with seam-resteasy patch described in https://jira.jboss.org/jira/browse/JBSEAM-3449, and RestEasy 1.0.1.GA.
> Reporter: John Sublette
> Assignee: Jozef Hartinger
> Priority: Minor
> Labels: RestEasy
>
> Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them as described in RestEasy's documentation (section 28.2 - Sharing an interface...). An interface with tagged @Path throws an exception when it is registered - because an interface doesn't have a constructor.
> See org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap Line 112 through 138 for how RestEasy handles this by default - (using Scannotation)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (SEAMSPRING-13) InputStream left open in SpringContextBootstrapExtension
by Gunther Klein (JIRA)
Gunther Klein created SEAMSPRING-13:
---------------------------------------
Summary: InputStream left open in SpringContextBootstrapExtension
Key: SEAMSPRING-13
URL: https://issues.jboss.org/browse/SEAMSPRING-13
Project: Seam Spring
Issue Type: Bug
Affects Versions: 3.1.0.Final, 3.2.0.Alpha1
Environment: Win 7 64Bit, Glassfish 3.2.1, Glassfish 4
Reporter: Gunther Klein
Assignee: Marius Bogoevici
We use the seam spring core library for integration of spring batch into our java ee 6 application (groupId:org.jboss.seam.spring, artifactId:seam-spring-core, version:3.1.0.Final). On Glassfish 3.2.1 and 4 undeployment of our ear shows the warning message:
WARNING: Input stream has been finalized or forced closed without being explicitly closed; stream instantiation reported in following stack trace
java.lang.Throwable
at com.sun.enterprise.loader.ASURLClassLoader$SentinelInputStream.<init>(ASURLClassLoader.java:1280)
at com.sun.enterprise.loader.ASURLClassLoader.getResourceAsStream(ASURLClassLoader.java:938)
at org.jboss.seam.spring.extension.SpringContextBootstrapExtension.loadSpringContext(SpringContextBootstrapExtension.java:61)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...
Looking into method org.jboss.seam.spring.extension.SpringContextBootstrapExtension::loadSpringContext() shows that it opens an InputStream to /META-INF/org.jboss.seam.spring.contexts, which never gets closed. This causes the ugly warning message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBSEAM-5002) Components included with ui:include src="#{pageScopedViewId} broken
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5002?page=com.atlassian.jira.plugi... ]
Marek Novotny commented on JBSEAM-5002:
---------------------------------------
It seems that now we refactored the posting conversationId through request as a parameter we can revert the commit which fixed JBSEAM-4667 and JBSEAM-4868 - replacing ViewRoot.getAttributes() with ViewRoot.getViewMap() in:
https://source.jboss.org/changelog/Seam?cs=14262
https://source.jboss.org/changelog/Seam?cs=14260
> 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, 2.3.0.Final
> Environment: JBoss AS 7.1.2, Seam 2.3.0.CR1-SNAPSHOT (r14986)
> Reporter: Marek Schmidt
> Assignee: Marek Novotny
> Fix For: 2.3.2.CR1
>
> Attachments: JBSEAM-5002.ear, JBSEAM-5002.tar.gz
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBSEAM-5002) Components included with ui:include src="#{pageScopedViewId} broken
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5002?page=com.atlassian.jira.plugi... ]
Marek Novotny updated JBSEAM-5002:
----------------------------------
Fix Version/s: 2.3.2.CR1
(was: The future)
> 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, 2.3.0.Final
> Environment: JBoss AS 7.1.2, Seam 2.3.0.CR1-SNAPSHOT (r14986)
> Reporter: Marek Schmidt
> Assignee: Marek Novotny
> Fix For: 2.3.2.CR1
>
> Attachments: JBSEAM-5002.ear, JBSEAM-5002.tar.gz
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months