[JBoss Seam] - Re: Two browser tabs : basic question
by dkane
"pete.muir(a)jboss.org" wrote : You don't need to use @RequestParamater with page parameters. Take a look at seamdiscs to see how they should be used.
I see no "param" tags in pages.xml of seamDISKS example (Seam 2.0) .
In seamSPACE , I see the following :
pages.xml :
<page view-id="/comment.xhtml" login-required="true">
| <restrict/>
|
| <param name="name" value="#{selectedMember.memberName}"/>
| <param name="blogId" value="#{selectedBlog.blogId}"/>
|
| <navigation from-action="#{blog.saveComment}">
| <redirect view-id="/blogentry.xhtml"/>
| </navigation>
| </page>
The target page, blogentry.xhtml , uses BlogAction component.
In BlogAction.java :
@RequestParameter
| private Integer blogId;
| ......
|
| @Factory("selectedBlog")
| @Begin(join=true)
| public void getBlog()
| {
| try
| {
| selectedBlog = (MemberBlog) entityManager.createQuery(
| "from MemberBlog b where b.blogId = :blogId and b.member.memberName = :memberName")
| .setParameter("blogId",blogId)
| .setParameter("memberName", name)
| .getSingleResult();
| }
| ....
| }
|
I.e. blogId is passed as @RequestParameter and then used to retreive current blog. Exactly the same approach I am trying to implement. Anything wrong ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114913#4114913
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114913
18 years, 4 months
[JBoss jBPM] - Re: Re-routing Tokens
by Olivier_Debels
We also use re-routing in our workflows:
* Firstly we use it when we want to split/merge tokens. The idea here is that we can gradually move in a process instance from a situation where we have:
- a single token with a reference to a collection of domain objects
- as much tokens as we have domain objects.
For example a single report can be made about several domain cases, or the user can opt to split it and make different reports for domain cases which belong together. The user can also opt to merge other domain cases into the current token. Splitting actually creates new subtokens, merging adds domain cases to the current token and can remove other process instances which were created. When a user decides to merge a re-route can happen to a certain node in the workflow (is configurable in custom addition in jbpm designer). Re-routing is done by calling node.leave()
* Secondly we allow the user to reopen task instances under certain circumstances. For example when having a process with 2 task nodes, making of a report followed by approving the report, and the user has complete the making of a report task but realized he forgot something, he can reopen this task. In that case the approving of the report task will be removed and the token will be re-routed. This is actually your case.
* Thirdly when a user did some changes in a process instance with a start task but wants to undo those changes (and he triggered the creation of the process instance), this process instance and task will be removed. This is not re-routing but simply removing task and processes.
For removing processes and task instances we just make sure they don't appear in the client task lists any more.
- We created methods to end processinstances, subprocessinstances, the tokens and taskinstances they contain. Clients won 't notice these any more but they still remain in the database.
- The circumstances in which a user can undo/reopen etc... are really specific. For example your implementation will not work if you have subprocesses or if you fork and have subtokens.
Hope this helps a bit (and is a bit understandeable),
feel free the comment
Olivier.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114912#4114912
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114912
18 years, 4 months
[JNDI/Naming/Network] - Re: javax.naming.NameNotFoundException: queue not bound
by bidhudas
Find entried in das-estinations-service.xml. Does the SQL exception u were talking about is it any way related to JMS?? As of now I do not have any issue in connecting to DB. I beleive this is for mySQL but I am connecting to Oracle DB. There is no issues with respect to that.
Please let me know if you require any additional information for resolving this issue.
<?xml version="1.0" encoding="UTF-8"?>
|
| <!-- $Id: jbossmq-destinations-service.xml 25907 2004-11-16 04:32:39Z ejort $ -->
|
| <!--
| | This file defines the default Queues and Topics that JBossMQ
| | ships with. The default Queues and Topics are used by the
| | JBoss test suite and by the sample jms programs.
| |
| | You can add other destinations to this file, or you can create other
| | *-service.xml files to contain your application's destinations.
| -->
|
| <server>
| <!-- Destination without a configured SecurityManager or without a
| a SecurityConf will default to role guest with read=true, write=true,
| create=false.
| -->
| <!--
| The following mbean is for DAS Queue
| -->
|
| <mbean code="org.jboss.mq.server.jmx.Queue"
| name="jboss.mq.destination:service=Queue,name=WebRequest"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| </mbean>
| <mbean code="org.jboss.mq.server.jmx.Queue"
| name="jboss.mq.destination:service=Queue,name=WebResponse">
| <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| </mbean>
| <mbean code="org.jboss.mq.server.jmx.Queue"
| name="jboss.mq.destination:service=Queue,name=EDIRequest">
| <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| </mbean>
| <mbean code="org.jboss.mq.server.jmx.Queue"
| name="jboss.mq.destination:service=Queue,name=TDARequest">
| <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| </mbean>
| <mbean code="org.jboss.mq.server.jmx.Queue"
| name="jboss.mq.destination:service=Queue,name=TDAResponse">
| <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| </mbean>
|
| </server>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114905#4114905
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114905
18 years, 4 months
[Installation, Configuration & DEPLOYMENT] - Multiple JBoss installations, first one is ok second one can
by rbrandon
Hi,
I have a situation where a server (Linux) is configured with multiple Jboss 4.0.5GA installations (note: not instances within a single installation). All installations only have the "default" server and all servers are running successfully without port conflicts.
We have deployed an application in the first installation that uses it's own MySQL database. As a result we have placed the JDBC driver in the server/default/lib folder of that installation and the application works correctly.
When deploying a different application in the second JBoss installation which also uses it's own MySQL database, and after placing the same JDBC driver in the server/default/lib folder of that second installation, the application fails when it tries to find the "com.mysql.jdbc.Driver" class and throws a ClassNotFoundException.
After undeploying the second application and deploying a copy of the first application in the second installation of JBoss, the same problem occurs. Because of this my conclusion is that this problem is not caused by the application itself.
I compared the boot.log of both installations and both seem to use their own paths. I have no clue why this ClassNotFoundException occurs, can anybody help?
Regards,
Raymond
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114901#4114901
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114901
18 years, 4 months