[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
15 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3362) Detect cyclic dependencies and throw exception
by Matt Drees (JIRA)
Detect cyclic dependencies and throw exception
----------------------------------------------
Key: JBSEAM-3362
URL: https://jira.jboss.org/jira/browse/JBSEAM-3362
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.BETA1
Reporter: Matt Drees
Assignee: Matt Drees
Imagine a scenario like this. Some client calls someMethod() on a component called Foo. BijectionInterceptor tries to inject Foo's @in attributes, one of which requires calling a factory method on Bar. Bar's factory method in turn calls Foo.someOtherMethod(). Foo is not in a state where it can support method calls, because it is in the process of injecting dependencies, so this sort of cyclic dependency should not be allowed. Seam should throw an exception in this case.
BijectionInterceptor used to be coded such that someOtherMethod() would run without any complaints, and any @In attributes may or may not be null, depending on which fields were injected first. Recent changes to BijectionInterceptor (for JBSEAM-3295) have changed this behavior, and now an finite loop results. Neither of these behaviors is desirable.
--
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
15 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2479) META Tags added to HTML HEAD in Seam HTML mail get removed
by Terry (JIRA)
META Tags added to HTML HEAD in Seam HTML mail get removed
----------------------------------------------------------
Key: JBSEAM-2479
URL: http://jira.jboss.com/jira/browse/JBSEAM-2479
Project: JBoss Seam
Issue Type: Bug
Components: Mail
Affects Versions: 2.0.0.GA
Environment: Windows, Outlook,
Reporter: Terry
Assigned To: Pete Muir
Fix For: 2.0.1.GA
the META tags added to HTML Head tag when sending Seam email in HTML get removed from the generated HTML. absence of META tags and not being able to add one causes issues in applications like outlook.
<m:message>
<m:from name="TISC Online" address="info(a)tisc.edu.au" />
<m:to name="#{subscriptionAdmin.recipient[0]}">#{subscriptionAdmin.recipient[1]}</m:to>
<m:subject>#{subscriptionAdmin.subscriptionConfig.massMailSubject}</m:subject>
<m:body>
<html>
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"/>
</head>
<body>
<h:outputText value="#{subscriptionAdmin.massMailMessageInterpolated}" escape="false"/>
</body>
</html>
</m:body>
</m:message>
come out like:
<html>
<head>
</head>
<body>
...
body contents
...
</body>
<html>
--
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
15 years, 8 months