[JBoss JIRA] (JBSEAM-5072) Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context
by Claus Elsborg (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5072?page=com.atlassian.jira.plugi... ]
Claus Elsborg commented on JBSEAM-5072:
---------------------------------------
It looks like java:global JNDI is not available until the application is fully deployed.
This means that quartz jobs that fires during startup throws a javax.naming.NameNotFoundException: appname/jboss-seam/EjbSynchronizations -- service jboss.naming.context.java.global.appname.jboss-seam.EjbSynchronizations.
If Quartz jobs are persisted in a database, the quartz jobs gets scheduled during the QuartzDispatcher.java Startup.
If using RAM store, it is normal to schedule the jobs by observing the org.jboss.seam.postInitialization event. But even here it still fails. After deployment is complete the jobs works fine.
For the described workaround to be useful I need a way to schedule quartz jobs during deployment or a least just after deployment completes in order to handle "misfires" during server down time. Any ideas of how to do this?
> Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBSEAM-5072
> URL: https://issues.jboss.org/browse/JBSEAM-5072
> Project: Seam 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2.0.GA, 2.2.1.Final, 2.2.2.Final
> Reporter: Luan Cestari
>
> Description of problem:
> Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context. In other words, Seam can`t find the beans in context, even that they are there (due the annotations and logs that confirm that).
> EAP 6`s documentation that gives the steps to migrate Seam 2 applications: https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_Applicati...
> Version-Release number of selected component (if applicable):
> Seam 2.2 in EAP 6
> How reproducible:
> Just create a Seam and Quartz bean and another Seam and EJB bean that on Startup will lookup for Seam/Quartz bean, but can`t find it.
> Actual results:
> Can`t find the bean
> Expected results:
> Find the bean
> Additional info:
> salesforce link: https://c.na7.visual.force.com/apex/Case_View?id=500A000000CQzrg&sfdc.ove...
--
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-5109) Problem when deploying application with already initialized EJB Timer
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5109?page=com.atlassian.jira.plugi... ]
Marek Novotny closed JBSEAM-5109.
---------------------------------
Fix Version/s: (was: 2.3.2.CR1)
Resolution: Rejected
This is not a bug, when Seam is initialized the failed timer will trigger again.
> Problem when deploying application with already initialized EJB Timer
> ---------------------------------------------------------------------
>
> Key: JBSEAM-5109
> URL: https://issues.jboss.org/browse/JBSEAM-5109
> Project: Seam 2
> Issue Type: Bug
> Affects Versions: 2.3.1.CR1
> Reporter: Tomas Remes
> Assignee: Marek Novotny
> Priority: Minor
>
> There occurs following exception, when deploying previously undeployed application, which has initialized some interval EJB Timer. Problem is that the initialization of Timer happens before the Seam initialization.
> {noformat}
> 08:13:03,533 ERROR [org.jboss.as.ejb3] (EJB default - 4) JBAS014122: Error during retrying timeout for timer: [id=9b570b93-583e-461e-82d7-cc509a22c337 timedObjectId=seam-ejbtimer.ejbtimer-ejb.PaymentProcessor auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@4a88b729 initialExpiration=Thu May 30 08:12:00 CEST 2013 intervalDuration(in milli sec)=5000 nextExpiration=Thu May 30 08:13:05 CEST 2013 timerState=RETRY_TIMEOUT: javax.ejb.EJBException: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:165) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.tx.TimerCMTTxInterceptor.handleExceptionInOurTx(TimerCMTTxInterceptor.java:53) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:250) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:315) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:101) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:111) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:157) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.timerservice.task.TimerTask.retryTimeout(TimerTask.java:184) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:140) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_17]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_17]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
> Caused by: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.component.stateless.StatelessSessionComponent$1.create(StatelessSessionComponent.java:67) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.component.stateless.StatelessSessionComponent$1.create(StatelessSessionComponent.java:64) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.pool.AbstractPool.create(AbstractPool.java:60) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.pool.strictmax.StrictMaxPool.get(StrictMaxPool.java:123) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:47) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> ... 26 more
> Caused by: javax.ejb.EJBException: java.lang.NullPointerException
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:165) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:250) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:339) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> ... 34 more
> Caused by: java.lang.NullPointerException
> at org.jboss.seam.intercept.RootInterceptor.init(RootInterceptor.java:50)
> at org.jboss.seam.intercept.SessionBeanInterceptor.postConstruct(SessionBeanInterceptor.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_17]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_17]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_17]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_17]
> at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:118) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:115) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> ... 43 more
> {noformat}
--
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-5072) Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5072?page=com.atlassian.jira.plugi... ]
Marek Novotny closed JBSEAM-5072.
---------------------------------
Resolution: Won't Fix
Basically before JBoss AS7 existance all JBoss servers (4,5,6) had a quartz Resource adapter which introduced and set up the correct EJB initial context. So Seam 2 pojo component worked. JBoss AS7 implements Java EE 6 and it enhanced TimerService features so AS team didn't invest any time to resource adapter for another timer scheduler/service as is Quartz. Every non-ejb thread needs to use java:global JNDI or create scheduler thread(s) from EJB component, recommended is EJB Singleton.
> Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBSEAM-5072
> URL: https://issues.jboss.org/browse/JBSEAM-5072
> Project: Seam 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2.0.GA, 2.2.1.Final, 2.2.2.Final
> Reporter: Luan Cestari
>
> Description of problem:
> Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context. In other words, Seam can`t find the beans in context, even that they are there (due the annotations and logs that confirm that).
> EAP 6`s documentation that gives the steps to migrate Seam 2 applications: https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_Applicati...
> Version-Release number of selected component (if applicable):
> Seam 2.2 in EAP 6
> How reproducible:
> Just create a Seam and Quartz bean and another Seam and EJB bean that on Startup will lookup for Seam/Quartz bean, but can`t find it.
> Actual results:
> Can`t find the bean
> Expected results:
> Find the bean
> Additional info:
> salesforce link: https://c.na7.visual.force.com/apex/Case_View?id=500A000000CQzrg&sfdc.ove...
--
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-5127) SeamNavigationHandler is not JSF2 compliant
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5127?page=com.atlassian.jira.plugi... ]
Marek Novotny reassigned JBSEAM-5127:
-------------------------------------
Assignee: Marek Novotny
> SeamNavigationHandler is not JSF2 compliant
> -------------------------------------------
>
> Key: JBSEAM-5127
> URL: https://issues.jboss.org/browse/JBSEAM-5127
> Project: Seam 2
> Issue Type: Bug
> Components: JSF Integration
> Affects Versions: 2.3.0.Final
> Reporter: Ilia Vassilev
> Assignee: Marek Novotny
>
> From javax.faces.application.NavigationHandler:
> {code}
> * <p class="changed_added_2_0">This method must set the render targets
> * (used in partial rendering) to <code>render all </code>
> * invoking {@link javax.faces.context.PartialViewContext#setRenderAll})
> * if the view identifier has changed as the result of an application
> * action (to take into account <code>Ajax requests</code>).</p>
> public abstract void handleNavigation(FacesContext context,
> String fromAction,
> String outcome);
> {code}
> org.jboss.seam.jsf.SeamNavigationHandler doesn't implement it and therefore an ajax-view-change cannot be detected by PartialViewContext. Result: nothing will be rendered.
--
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-5127) SeamNavigationHandler is not JSF2 compliant
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5127?page=com.atlassian.jira.plugi... ]
Ilia Vassilev updated JBSEAM-5127:
----------------------------------
Workaround Description:
This will wrap the buggy SeamNavigationHandler and informs the PartialViewContext about view-root changes:
{code}
public class WrapNavigationHandler extends ConfigurableNavigationHandler {
private final NavigationHandler baseNavigationHandler;
public PortletNavigationHandler(NavigationHandler navigationHandler)
{
this.baseNavigationHandler = navigationHandler;
}
@Override
public void handleNavigation(FacesContext context, String fromAction, String outcome) {
String oldView = (context.getViewRoot() != null ? context.getViewRoot().getViewId() : "");
baseNavigationHandler.handleNavigation(context, fromAction, outcome);
if (!oldView.equals(context.getViewRoot().getViewId())) {
PartialViewContext pctx = context.getPartialViewContext();
if (!pctx.isRenderAll()) {
pctx.setRenderAll(true);
}
}
}
...
}
{code}
Workaround: Workaround Exists
> SeamNavigationHandler is not JSF2 compliant
> -------------------------------------------
>
> Key: JBSEAM-5127
> URL: https://issues.jboss.org/browse/JBSEAM-5127
> Project: Seam 2
> Issue Type: Bug
> Components: JSF Integration
> Affects Versions: 2.3.0.Final
> Reporter: Ilia Vassilev
>
> From javax.faces.application.NavigationHandler:
> {code}
> * <p class="changed_added_2_0">This method must set the render targets
> * (used in partial rendering) to <code>render all </code>
> * invoking {@link javax.faces.context.PartialViewContext#setRenderAll})
> * if the view identifier has changed as the result of an application
> * action (to take into account <code>Ajax requests</code>).</p>
> public abstract void handleNavigation(FacesContext context,
> String fromAction,
> String outcome);
> {code}
> org.jboss.seam.jsf.SeamNavigationHandler doesn't implement it and therefore an ajax-view-change cannot be detected by PartialViewContext. Result: nothing will be rendered.
--
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-5127) SeamNavigationHandler is not JSF2 compliant
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5127?page=com.atlassian.jira.plugi... ]
Ilia Vassilev updated JBSEAM-5127:
----------------------------------
Description:
>From javax.faces.application.NavigationHandler:
{code}
* <p class="changed_added_2_0">This method must set the render targets
* (used in partial rendering) to <code>render all </code>
* invoking {@link javax.faces.context.PartialViewContext#setRenderAll})
* if the view identifier has changed as the result of an application
* action (to take into account <code>Ajax requests</code>).</p>
public abstract void handleNavigation(FacesContext context,
String fromAction,
String outcome);
{code}
org.jboss.seam.jsf.SeamNavigationHandler doesn't implement it and therefore an ajax-view-change cannot be detected by PartialViewContext. Result: nothing will be rendered.
was:
>From javax.faces.application.NavigationHandler:
<code>
* <p class="changed_added_2_0">This method must set the render targets
* (used in partial rendering) to <code>render all </code>
* invoking {@link javax.faces.context.PartialViewContext#setRenderAll})
* if the view identifier has changed as the result of an application
* action (to take into account <code>Ajax requests</code>).</p>
public abstract void handleNavigation(FacesContext context,
String fromAction,
String outcome);
<code>
org.jboss.seam.jsf.SeamNavigationHandler doesn't implement it and therefore an ajax-view-change cannot be detected by PartialViewContext. Result: nothing will be rendered.
> SeamNavigationHandler is not JSF2 compliant
> -------------------------------------------
>
> Key: JBSEAM-5127
> URL: https://issues.jboss.org/browse/JBSEAM-5127
> Project: Seam 2
> Issue Type: Bug
> Components: JSF Integration
> Affects Versions: 2.3.0.Final
> Reporter: Ilia Vassilev
>
> From javax.faces.application.NavigationHandler:
> {code}
> * <p class="changed_added_2_0">This method must set the render targets
> * (used in partial rendering) to <code>render all </code>
> * invoking {@link javax.faces.context.PartialViewContext#setRenderAll})
> * if the view identifier has changed as the result of an application
> * action (to take into account <code>Ajax requests</code>).</p>
> public abstract void handleNavigation(FacesContext context,
> String fromAction,
> String outcome);
> {code}
> org.jboss.seam.jsf.SeamNavigationHandler doesn't implement it and therefore an ajax-view-change cannot be detected by PartialViewContext. Result: nothing will be rendered.
--
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-5127) SeamNavigationHandler is not JSF2 compliant
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5127?page=com.atlassian.jira.plugi... ]
Ilia Vassilev updated JBSEAM-5127:
----------------------------------
Description:
>From javax.faces.application.NavigationHandler:
<code>
* <p class="changed_added_2_0">This method must set the render targets
* (used in partial rendering) to <code>render all </code>
* invoking {@link javax.faces.context.PartialViewContext#setRenderAll})
* if the view identifier has changed as the result of an application
* action (to take into account <code>Ajax requests</code>).</p>
public abstract void handleNavigation(FacesContext context,
String fromAction,
String outcome);
<code>
org.jboss.seam.jsf.SeamNavigationHandler doesn't implement it and therefore an ajax-view-change cannot be detected by PartialViewContext. Result: nothing will be rendered.
was:
>From javax.faces.application.NavigationHandler:
...
* <p class="changed_added_2_0">This method must set the render targets
* (used in partial rendering) to <code>render all </code>
* invoking {@link javax.faces.context.PartialViewContext#setRenderAll})
* if the view identifier has changed as the result of an application
* action (to take into account <code>Ajax requests</code>).</p>
...
public abstract void handleNavigation(FacesContext context,
String fromAction,
String outcome);
org.jboss.seam.jsf.SeamNavigationHandler doesn't implement it and therefore an ajax-view-change cannot be detected by PartialViewContext. Result: nothing will be rendered.
> SeamNavigationHandler is not JSF2 compliant
> -------------------------------------------
>
> Key: JBSEAM-5127
> URL: https://issues.jboss.org/browse/JBSEAM-5127
> Project: Seam 2
> Issue Type: Bug
> Components: JSF Integration
> Affects Versions: 2.3.0.Final
> Reporter: Ilia Vassilev
>
> From javax.faces.application.NavigationHandler:
> <code>
> * <p class="changed_added_2_0">This method must set the render targets
> * (used in partial rendering) to <code>render all </code>
> * invoking {@link javax.faces.context.PartialViewContext#setRenderAll})
> * if the view identifier has changed as the result of an application
> * action (to take into account <code>Ajax requests</code>).</p>
> public abstract void handleNavigation(FacesContext context,
> String fromAction,
> String outcome);
> <code>
> org.jboss.seam.jsf.SeamNavigationHandler doesn't implement it and therefore an ajax-view-change cannot be detected by PartialViewContext. Result: nothing will be rendered.
--
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-5127) SeamNavigationHandler is not JSF2 compliant
by Ilia Vassilev (JIRA)
Ilia Vassilev created JBSEAM-5127:
-------------------------------------
Summary: SeamNavigationHandler is not JSF2 compliant
Key: JBSEAM-5127
URL: https://issues.jboss.org/browse/JBSEAM-5127
Project: Seam 2
Issue Type: Bug
Components: JSF Integration
Affects Versions: 2.3.0.Final
Reporter: Ilia Vassilev
>From javax.faces.application.NavigationHandler:
...
* <p class="changed_added_2_0">This method must set the render targets
* (used in partial rendering) to <code>render all </code>
* invoking {@link javax.faces.context.PartialViewContext#setRenderAll})
* if the view identifier has changed as the result of an application
* action (to take into account <code>Ajax requests</code>).</p>
...
public abstract void handleNavigation(FacesContext context,
String fromAction,
String outcome);
org.jboss.seam.jsf.SeamNavigationHandler doesn't implement it and therefore an ajax-view-change cannot be detected by PartialViewContext. Result: nothing will be rendered.
--
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