[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1747) SeamPhaseListener transaction debug log statements are misleading/confusing
by Matt Drees (JIRA)
SeamPhaseListener transaction debug log statements are misleading/confusing
---------------------------------------------------------------------------
Key: JBSEAM-1747
URL: http://jira.jboss.com/jira/browse/JBSEAM-1747
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.BETA1
Environment: 20070727.1142
Reporter: Matt Drees
Priority: Trivial
Debug logs from SeamPhaseListener look something like this on a non-faces request:
DEBUG 31-07 11:34:31,467 (org.jboss.seam.jsf.SeamPhaseListener:begin:573) beginning transaction prior to phase: RESTORE_VIEW 1
DEBUG 31-07 11:34:31,560 (org.jboss.seam.jsf.SeamPhaseListener:commitOrRollback:589) committing transaction after phase: RESTORE_VIEW 1
DEBUG 31-07 11:34:31,560 (org.jboss.seam.jsf.SeamPhaseListener:begin:573) beginning transaction prior to phase: RENDER_RESPONSE 6
DEBUG 31-07 11:34:31,576 (org.jboss.seam.jsf.SeamPhaseListener:commitOrRollback:589) committing transaction after phase: INVOKE_APPLICATION 5
DEBUG 31-07 11:34:31,592 (org.jboss.seam.jsf.SeamPhaseListener:begin:573) beginning transaction prior to phase: INVOKE_APPLICATION 5
DEBUG 31-07 11:34:33,731 (org.jboss.seam.jsf.SeamPhaseListener:commitOrRollback:589) committing transaction after phase: RENDER_RESPONSE 6
It's misleading. For one thing, there is no "INVOKE_APPLICATION" phase; but that phaseid is used for logging before and after page actions. For another, the "before" and "after" statements are backwards (semantically).
--
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
17 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1832) Use of <a:support> tag breaks conversation in Seam-gen (and elsewhere)
by Vincent Latombe (JIRA)
Use of <a:support> tag breaks conversation in Seam-gen (and elsewhere)
----------------------------------------------------------------------
Key: JBSEAM-1832
URL: http://jira.jboss.com/jira/browse/JBSEAM-1832
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 2.0.0.BETA1
Environment: Jboss 4.2.0.GA
Reporter: Vincent Latombe
I've seen the problem from BETA1 to HEAD
To reproduce the bug, try the following :
Create some seam-gen based project and generate-entities.
Go to an edit page, fill some data, and click on the submit button, without clicking elsewhere (the focus must be on an edited field just before submit). Instead of validation error, or adding the new data, you should get the "The conversation ended, timed out or was processing another request" message. It seems that the validation triggered by the onblur event messes up with the validation.
I have also seen the bug occuring while I was switching from one field to another quite fast (fast enough to have many validation on queue in ajax4jsf). It seems that adding <s:conversationId/> to the a:support solves this part.
Here is the snippet I currently use
<a:support event="onblur" bypassUpdates="true" reRender="cityCodeDecoration">
<s:conversationId/>
</a:support>
I tried to upgrade ajax4jsf + richfaces 3.0.1 to richfaces 3.1.0 rc2, but it didn't change anything.
--
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
17 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1183) Allow custom ExceptionHandler implementations to be inserted
by Mike Quilleash (JIRA)
Allow custom ExceptionHandler implementations to be inserted
------------------------------------------------------------
Key: JBSEAM-1183
URL: http://jira.jboss.com/jira/browse/JBSEAM-1183
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 1.1.6.GA
Environment: Any
Reporter: Mike Quilleash
Currently you can only configure a small subset of actions to occur on an exception (redirect, http-error etc). Enhancing the exception configuration xml to allow pluggable ExceptionHandler implementations would make this a lot more flexible.
e.g. pages.xml
<pages>
<!-- the current way, exception class + action -->
<exception class="javax.persistence.EntityNotFoundException">
<http-error error-code="404"/>
</exception>
<!-- proposed enhancement -->
<exception handlerClass="com.xxx.seam.CustomExceptionHandler"/>
</pages>
These should probably have higher precedence than standard configure-by-exception-class handlers.
--
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
17 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1709) seam-gen generated code throws exception
by Ralph Schaer (JIRA)
seam-gen generated code throws exception
----------------------------------------
Key: JBSEAM-1709
URL: http://jira.jboss.com/jira/browse/JBSEAM-1709
Project: JBoss Seam
Issue Type: Bug
Components: Core, Framework
Affects Versions: 2.0.0.BETA1
Environment: Seam (CVS checkout from today), JBoss 4.2.1, Java 6, Windows XP
Reporter: Ralph Schaer
A seam-gen generated application (with generated entities) is throwing the following error, when I click for example on the column header in a list (sort) or when I try to create a new object.
Exception during request processing:
Caused by java.lang.IllegalArgumentException with message: "Could not invoke method by reflection: Instance.getComponent() on: test.CarHome"
org.jboss.seam.util.Reflections.invoke(Reflections.java:31)
org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
Caused by java.lang.IllegalArgumentException with message: "object is not an instance of declaring class"
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
org.jboss.seam.persistence.ManagedEntityIdentityInterceptor.aroundInvoke(ManagedEntityIdentityInterceptor.java:45)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
org.jboss.seam.transaction.TransactionInterceptor$1.work(TransactionInterceptor.java:38)
org.jboss.seam.util.Work.workInTransaction(Work.java:39)
org.jboss.seam.transaction.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:32)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106)
org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:151)
org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:87)
test.CarHome_$$_javassist_2.getComponent(CarHome_$$_javassist_2.java)
org.jboss.seam.core.Validators.getValidator(Validators.java:85)
Steps to reproduce the error
1. Create a table in the database (Example with mysql. I guess the database does not matter)
CREATE TABLE `test`.`Car` (
`id` INTEGER UNSIGNED NOT NULL DEFAULT NULL AUTO_INCREMENT,
`name` VARCHAR(255) NOT NULL,
PRIMARY KEY (`id`)
)
ENGINE = InnoDB;
2. seam setup (ear or war deployment does not matter. Problem exists in both deployment modes)
3. seam new-project
4. seam generate-entities
5. seam explode (jboss is already running)
6. Start the broser and type http://localhost:8080/name_of_webapp
7. Browser shows the Welcome screen. Everything looks fine.
8. Click on "Car List "
9. Click on "Create car"
10. Exception
--
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
17 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1818) Patch proposed to LocaleSelector
by Marco Pancotti (JIRA)
Patch proposed to LocaleSelector
--------------------------------
Key: JBSEAM-1818
URL: http://jira.jboss.com/jira/browse/JBSEAM-1818
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.BETA1
Reporter: Marco Pancotti
Priority: Minor
org.jboss.seam.international.LocaleSelector does not implement a getDefaultLocale method. I think it can be useful in a multi-language application. So I propose to apply the following patch in the LocaleSelector class adding the following methods (it can be more complex if you want orthogonal returns respect the return of the specified locale):
public Locale getDefaultLocale(){
return FacesContext.getCurrentInstance().getApplication().getDefaultLocale() ;
}
public String getDefaultLocaleLanguage(){
return FacesContext.getCurrentInstance().getApplication().getDefaultLocale() .getLanguage();
}
Marco Pancotti
--
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
17 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1623) Problems with rendering emails with seam-email and IceFaces 1.6
by Karol Oslowski (JIRA)
Problems with rendering emails with seam-email and IceFaces 1.6
---------------------------------------------------------------
Key: JBSEAM-1623
URL: http://jira.jboss.com/jira/browse/JBSEAM-1623
Project: JBoss Seam
Issue Type: Bug
Components: ICE Faces Integration
Affects Versions: 1.2.1.GA
Environment: JBoss AS 4.0.5 GA with EJB3 installed (1.2.0.GA), project with Seam 1.2.1 GA,
Reporter: Karol Oslowski
Assigned To: Gregory Dick
Bug is quite simple to replicate. All u have to do is install jboss with ejb3 from the net installer http://labs.jboss.com/jemsinstaller/downloads version 1.2.0.GA. You also have to get the example applications from seam 1.2.1 GA, You have to configure the mail example as described in jboss forum linked to this bug and when trying to send an email there will be such exception:
04:18:32,140 INFO [MailSession] Creating JavaMail Session (l***:)
04:18:32,156 INFO [MailSession] connected to mail server
04:18:32,250 ERROR [MailExample] Error sending mail
java.lang.NullPointerException
at org.jboss.seam.mail.ui.UIMessage.getCharset(UIMessage.java:242)
at org.jboss.seam.mail.ui.AddressComponent.getInternetAddress(AddressComponent.java:29)
at org.jboss.seam.mail.ui.UIFrom.encodeBegin(UIFrom.java:27)
at org.jboss.seam.ui.JSF.renderChild(JSF.java:171)
at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162)
at org.jboss.seam.mail.ui.UIMessage.encodeChildren(UIMessage.java:159)
at org.jboss.seam.ui.JSF.renderChild(JSF.java:174)
at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162)
at org.jboss.seam.ui.facelet.FaceletsRenderer.renderFacelet(FaceletsRenderer.java:150)
at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:112)
at org.jboss.seam.example.mail.MailExample.send(MailExample.java:42)
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:20)
at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:57)
at org.jboss.seam.interceptors.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:47)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69)
at org.jboss.seam.interceptors.ManagedEntityIdentityInterceptor.aroundInvoke(ManagedEntityIdentityInterceptor.java:37)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69)
at org.jboss.seam.interceptors.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:34)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69)
at org.jboss.seam.interceptors.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:27)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69)
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:103)
at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:151)
at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:87)
at org.jboss.seam.example.mail.MailExample_$$_javassist_19.send(MailExample_$$_javassist_19.java)
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 com.sun.el.parser.AstValue.invoke(AstValue.java:174)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:286)
at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68)
at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:69)
at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:63)
at javax.faces.component.UICommand.broadcast(UICommand.java:106)
at javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:94)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:168)
at org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:343)
at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
at com.icesoft.faces.webapp.http.core.ReceiveSendUpdates.renderCycle(ReceiveSendUpdates.java:57)
at com.icesoft.faces.webapp.http.core.ReceiveSendUpdates.service(ReceiveSendUpdates.java:45)
at com.icesoft.faces.webapp.http.core.IDVerifier.service(IDVerifier.java:25)
at com.icesoft.faces.webapp.http.servlet.BasicAdaptingServlet.service(BasicAdaptingServlet.java:16)
at com.icesoft.faces.webapp.http.servlet.ViewBoundAdaptingServlet.service(ViewBoundAdaptingServlet.java:44)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
at com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet.service(MainSessionBoundServlet.java:97)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:35)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:359)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:54)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
--
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
17 years, 8 months