[JBoss Seam] - Re: please document library versions
by tynor
In the mean time, can someone tell me what versions of the following jars are bundled in Seam 1.2.1-GA and 2.0.0-BETA?
hibernate-all.jar
jboss-ejb3-all.jar
jsf-facelets.jar
and the javassist bundled into thirdparty-all.jar
none of those jar's MANIFEST.MF's specify versions.
Thanks!
anonymous wrote : I am running into a bug which from googling may be fixed in a newer hibernate or ejb3 release, but I can't be sure -- I can't tell from the jboss-seam-1.2.1-GA.zip file just what versions of various jars are bundled.
|
| The Seam 2.0-BETA distribution does not appear to be any better documented. Before te next release, please update the lib/readme.txt to include details of each jar file's version and/or change their filenames (e.g., from hibernate-all.jar to hibernate-all.x.y.z.jar) so we can know what versions we're using.
|
| If I'm just blind and not looking in the right place, my apologies, and please just point me to the docs.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072240#4072240
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072240
18Â years, 9Â months
[JBoss Seam] - Re: entity's lifecycle and jBPM
by vladimir.kovalyuk
My understanding is different.
For instance once the author of a document completed with draft it might ask somebody to review the document. And the process of reviewing would be a normal business process. As the result of reviewing the document could be promoted to the next state. But, when it is being promoted the action assigned to the transition could perform whatever we want, for instance inform the people interested in the traking the document about the the fact that the document has been promoted. That's why I believe jBPM suites.
Lifecyle is similar to state-diagram or timeline (It's matter of taste). I'd prefer not to see tasks in the Lifecycle graph.
And what is important user can be happy looking at the picture. Tasks make the picture overcomplicated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072239#4072239
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072239
18Â years, 9Â months
[JBoss Seam] - Pages.enterPage and FaceletsViewHandler.buildView
by andrew.rw.robinson
I am trying to get the functionality of JBoss Seam's pages.xml to work with facelet include files. This way I can have security and action methods called on included views as well as the main page.
The problem I am having is one of order of execution. Pages.enterPage is called from a PhaseListener in the before render event. FaceletsViewHandler.buildView is called from the renderView function. So, when the page is "entered", the view is not built yet, so I can't surf the component hierarchy of the page to find my include components and determine their view ID to have Pages check on it.
Anyone have any bright ideas on how I can get the Pages functionality to be executed after the view is built, but before it is rendered without having to change Facelets or Seam source?
-Andrew
Facelets 1.1.11
Seam 1.2.1
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072237#4072237
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072237
18Â years, 9Â months
[JBoss Seam] - Connection handle has been closed and is unusable
by msduk
Hi. There is a huge amount of noise relating to this error all over the place. I'm not really sure if it is a seam/AS/Hibernate issue.
The stack is as follows
Caused by: java.sql.SQLException: Connection handle has been closed and is unusable
| at org.jboss.resource.adapter.jdbc.WrappedConnection.checkStatus(WrappedConnection.java:537)
| at org.jboss.resource.adapter.jdbc.WrappedConnection.checkTransaction(WrappedConnection.java:524)
| at org.jboss.resource.adapter.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:184)
| at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:497)
| at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:415)
| at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139)
| at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1560)
| at org.hibernate.loader.Loader.doQuery(Loader.java:661)
| at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224)
| at org.hibernate.loader.Loader.loadCollection(Loader.java:1918)
This was occurring frequently and I added
<valid-connection-checker-class-name>com.mysql.jdbc.integration.jboss.MysqlValidConnectionChecker</valid-connection-checker-class-name>
| <check-valid-connection-sql>SELECT count(warehouseId) FROM warehouse</check-valid-connection-sql> which I dont think had an effect (the errors were still common). I upgraded the hibernate versions in Seam 1.2.1 to the latest hibernate which definitely reduced the frequency however they are still there. Any suggestions welcome.
(Just in case it helps)
One thing I did notice which admittedly is likely a red herring is that the errors seem to happen where concurrent modification is likely i.e. separate threads modifying the same data. As one thread is only reading ever then I cant see that this could be an issue.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072233#4072233
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072233
18Â years, 9Â months