[
https://jira.jboss.org/jira/browse/JBSEAM-3335?page=com.atlassian.jira.pl...
]
Jay Balunas updated JBSEAM-3335:
--------------------------------
Fix Version/s: 2.1.0.BETA2
(was: 2.0.2.GA)
Affects Version/s: 2.1.0.BETA1
(was: 2.0.2.CR2)
This minor change was never ported to trunk.
Modify the jee5 main.xhtml so that the search string input box supports queuing events and
uses the conversation ID.
<h:inputText id="searchString" value="#{hotelSearch.searchString}"
style="width: 165px;">
<a:support event="onkeyup"
actionListener="#{hotelSearch.find}" reRender="searchResults"
eventsQueue="searchQueue">
<s:conversationId/>
</a:support>
</h:inputText>
port fix to trunk for glassfish jee5 example throws
IllegalStateException: EJB is already associated with an incomplete transaction
-----------------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3335
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3335
Project: Seam
Issue Type: Bug
Components: Examples, Platform interoperability
Affects Versions: 2.1.0.BETA1
Environment: Glassfish V2
Reporter: Jay Balunas
Assignee: Jay Balunas
Fix For: 2.1.0.BETA2
The app seemed to deploy fine, I could register new users, and login, change password,
click the search button and book hotels.
However if I enter a character in the input box for searching hotels I would get the
exception below (See attachment for full stack).
Caused by: javax.ejb.EJBException: nested exception is: java.lang.IllegalStateException:
EJB is already associated with an incomplete transaction
at com.sun.ejb.containers.BaseContainer.preInvoke(BaseContainer.java:1266)
at
com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:195)
at
com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke(EJBLocalObjectInvocationHandlerDelegate.java:83)
at $Proxy111.isNextPageAvailable(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
at
org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
at
org.jboss.seam.intercept.ClientSideInterceptor$1.proceed(ClientSideInterceptor.java:76)
at
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
at org.jboss.seam.ejb.RemoveInterceptor.aroundInvoke(RemoveInterceptor.java:41)
at
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at
org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:32)
at
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
at
org.jboss.seam.intercept.ClientSideInterceptor.invoke(ClientSideInterceptor.java:54)
at org.javassist.tmp.java.lang.Object_$$_javassist_3.isNextPageAvailable(Obje
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira