[JBoss Seam] - Page Parameters and Expired Conversations
by iradix
A quick question about page parameters. As I understand it, they are available so that conversational state can be reinitialized when the conversation no longer exists, like when a page is accessed from a bookmark. If that's the case, then shouldn't there be a way to override Seams default behaivour of adding org.jboss.seam.NoConversation to the faces messages if an expired conversation is encountered? Right now I'm trying to use the feature to make product pages bookmarkable and it isn't going to inspire shopper confidence to see "Conversation Expired" when trying to decide whether to click "Add to Cart"........ I also realize this is a new feature and am happy to help make it a bit more robust but I wanted to see what the plans were before digging into the code.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984617#3984617
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984617
19Â years, 6Â months
[JBoss jBPM] - JBOSS Messaging 1.0 GA and JBPM 3.1.2 deployment issues
by jglan
I'm trying to use JBPM in combination with JBOSS Messaging under JBOSS 4.0.5.
Depending on whether I have jbpm deployed scoped or not I get different errors during/after deployment of the MDBs jar package:
With jbpm unscoped directly during startup:
[org.jboss.jms.client.container.ExceptionInterceptor] Caught RuntimeException
java.lang.ClassCastException: org.jboss.jms.destination.JBossQueue
With jbpm scoped:
The server starts fine but I get an error within the MDB, which attempts to access JBPM:
java.lang.ClassCastException: org.jbpm.JbpmConfiguration
I guess I'd have to use the same classloader for the MDB jar as for jbpm.sar. (I use the jar just for testing purposes now, likely becomes an ear in future)
I wonder if there is somebody who has already figured out the right setup (e.g. I also don't have jbpm.3.1.2.jar not in the sar but in deploy/xxx/lib) for this combination.
Any comments/hints are highly appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984614#3984614
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984614
19Â years, 6Â months
[JBoss Portal] - DB2 / Hibernate mapping / error at starting
by Antoine_h
JBoss Portal 2.4
DB2 8
When the portal starts, there are some errors with some types used in portal, that don't fit with hibernate + DB2.
Error : "ERROR [org.hibernate.util.JDBCExceptionReporter] DB2 SQL error: SQLCODE: -204,..."
Error 204 is : "The object identified by _name_ is not found in the database".
Some tables cannot be created, because the fields mapping is not correct.
A string type (default type) with length 50000000 cannot be created in DB2, hence the whole table is not created.
In jboss-portal.sar\conf\hibernate_db2\instance\domain.hbm.xml
In table="JBP_INSTANCE", change
<property
| name="state"
| column="SER_STATE"
| not-null="false"
| unique="false"
| length="50000000"/>
with
<property
| name="state"
| column="SER_STATE"
| not-null="false"
| unique="false"
| type="text"
| />
And in table="JBP_INSTANCE_PER_USER", change
<property
| name="state"
| column="SER_STATE"
| not-null="false"
| unique="false"
| length="50000000"/>
with
<property
| name="state"
| column="SER_STATE"
| not-null="false"
| unique="false"
| type="text"/>
Put type="text" instead of length="50000000" (and default type="string").
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984609#3984609
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984609
19Â years, 6Â months