Is there a way to upgrade deployed workflow tasks to the new version of the workflow. I don't want to use multiple versions of the same workflow.
For example, if the deployed workflow pattern goes like:
A -> B -> C
I would like to upgrade the deployed tasks so that it goes:
A -> C -> D
where B tasks would go to A or C using to new version of the workflow.
We have documents that may be in the workflow for many months. Sometimes policies change on how they are to be processed. If the policies grandfather the existing documents, then leaving them in the older workflow version is fine. However, the policies may very well dictate that they be moved to the new flow and continue through it. We need to be prepared for that situation so that we can support it.
Thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123085#4123085
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123085
Wish I had paid more attention during English classes.
I'll try to rephraze.
I was actually wondering whether people are looking for an extra log type possibility like:
org.hibernate.type -> log binding and returning statements
org.hibernate.type.binding -> only log binding variables.
(and possibly even differentiate between binding variables in insert stmts and query stmts)
org.hibernate.type.returning -> only log returning variables.
I would appreciate it, I looked into the source code of the nullable type and it doesnt look very complicated to implement, I'm not sure on performance impact though.
regards,
jeroen.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123083#4123083
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123083
What version of JBoss Portal and JBossAS are you using? What database are you using? If you reinitialize everything (new JBossAS, new JBoss Portal, empty database), does the Portal run fine? (Another way of asking that last question: was the Portal running fine before you deployed wiki.war?)
Also, what you posted was the exception stack trace shown on the browser. That is usually useless in debugging a problem. Instead, post the stack trace written to the console.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123082#4123082
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123082
If I do this, I get a clean server start, but when calling the first servlet, I get this error now:
javax.naming.NameNotFoundException: local:ejb not bound
Is this because I use the call
DataAccessFacadeLocalHome dataFacadeHome = (DataAccessFacadeLocalHome)getContext().lookup("local:ejb/ejb/com/wag/debeos/DataAccessFacadeLocalHome");
in the code of the servlet?
(;-) you remember - I'm just a rookie trying to get some knowledge, but haven't yet...)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123079#4123079
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123079
When you say your application is not accessible, what exactly happens? How do you access your application? Which version of Java are you using? Is your application deployed as a war file or a ear file?
Does it throw any errors on the console or in the logs files or on the browser when you access the application?
The logs that you posted show that the application is starting up. Maybe the logs are not complete. There's a server.log file in /opt/jboss-4.0.3/server/all/log folder. See whether it contains any error message when you access your application.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123074#4123074
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123074
For the settings you have, the JVM will initially ask the OS for 1GB of memory. As the JVM runs, it *might* after certain garbage collections ask the OS for more memory. If you ask the JVM how big the heap is, it will tell you anything from 1GB to 4GB, depending on how much memory it has allocated at that time.
Apparently, it is telling you 3GB because that is all that it has asked for. If you expect the JVM to use 4GB, force it to ask for that much:
-Xms4096m -Xmx4096m
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123073#4123073
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123073
For a <tx-connection-factory> with <xa-transaction/> but without <track-connection-by-tx/>, does obtaining a connection handle within an application component acquire an exclusive lock on the underlying managed connection?
Is it possible to have multiple concurrent transactions all holding open handles to the same managed connection with transaction interleaving facilitating the context switching between them?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123072#4123072
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123072