"javax.persistence.TransactionRequiredException: no transaction is in progress" thrown during flush of a transient entity in a @Transactional POJO
--------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-1145
URL: http://jira.jboss.com/jira/browse/JBSEAM-1145
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.1.GA
Environment: Tomcat + Microcontainer (has also been tried on Tomcat + JOTM, Tomcat + Atomikos, Tomcat + JBoss Transactions, all with the same result)
Seam-managed Tx and PC, long-running conversations with manual flush
Reporter: Alex Savitsky
When persisting a transient entity during manual flush, an exception "javax.persistence.TransactionRequiredException: no transaction is in progress" is thrown, unless getEntityManager().joinTransaction() is executed prior to flush() - despite declaring the POJO as @Transactional and using Seam-managed transactions and persistence contexts.
When persisting a managed entity, however, no exceptions are thrown and update completes normally.
--
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
Usage of jBPM core:process-definitions needs clarification
----------------------------------------------------------
Key: JBSEAM-1034
URL: http://jira.jboss.com/jira/browse/JBSEAM-1034
Project: JBoss Seam
Issue Type: Bug
Components: Documentation
Affects Versions: 1.2.0.GA
Environment: All
Reporter: Arjan van Bentem
Priority: Minor
The Seam documentation for "21.6. Configuring jBPM in Seam" describes how to add jBPM process definitions to components.xml:
<core:jbpm>
<core:pageflow-definitions>
<value>createDocument.jpdl.xml</value>
<value>editDocument.jpdl.xml</value>
<value>approveDocument.jpdl.xml</value>
</core:pageflow-definitions>
<core:process-definitions>
<value>documentLifecycle.jpdl.xml</value>
</core:process-definitions>
</core:jbpm>
Nice, but as a side-effect a new copy is inserted into the database each time JBoss AS is started, even if the deployed EAR has not changed. This, of course, can only be noticed if in the example hibernate.cfg.xml from the DVD Store example the line
<property name="hbm2ddl.auto">create-drop</property>
is changed into
<property name="hbm2ddl.auto">update</property>
Apparently using <core:pageflow-definitions> is considered to be a developers tool:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=98430http://www.jboss.com/index.html?module=bb&op=viewtopic&t=90206http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103819
I think this needs some clarification in the documentation, but unfortunately (right now) I would not know what is the preferred way to deploy processes in Seam on a production machine. The third topic might include some ideas from others on that.
Arjan.
--
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
s:decorateAll tag
-----------------
Key: JBSEAM-2249
URL: http://jira.jboss.com/jira/browse/JBSEAM-2249
Project: JBoss Seam
Issue Type: Feature Request
Reporter: Tim Evers
Currently each input field needs to be surounded by the s:decorate tag.
What would be nicer is to be able to use a s:decorateAll tag which would accept a template that would suround evey input component inside the tag.
--
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
<s:formattedText value="#{post.body}" highlight="#{word}"/>
-----------------------------------------------------------
Key: JBSEAM-650
URL: http://jira.jboss.com/jira/browse/JBSEAM-650
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.5.GA
Seam needs to support wikitext ootb.
--
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
jsf control (convertor) that will convert bytes to kilobytes/megabytes/...
--------------------------------------------------------------------------
Key: JBSEAM-1862
URL: http://jira.jboss.com/jira/browse/JBSEAM-1862
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Reporter: Adrian Mitev
This is useful when fileupload is performed to show the file size in user-readable form.
--
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
s:transformImageSize - could be optimized if image already has requested size
-----------------------------------------------------------------------------
Key: JBSEAM-1793
URL: http://jira.jboss.com/jira/browse/JBSEAM-1793
Project: JBoss Seam
Issue Type: Feature Request
Reporter: henrik lindberg
Priority: Optional
If an image already has the requested size, s:transformImageSize does not have to go through the drawing logic. Would save some cycles.
--
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