[JNDI and Naming] - Default JNDI name changed after recompiling
by icordoba
Hi there,
I have just migrated an application from JBoss 4 and Java 5 to JBoss 5.1 and Java 6. It worked OK... my Stateless Session Beans had a remote JNDi name like:
UserManager/remote (as all docs state is the default remote name). For some reason I had implemented @Remote both in the interface and in the bean class itself. That worked ok in JBoss 4 but JBoss 5.1 started giving problems when deploying so I removed @Remote from the bean and left it just in the interface (as it is supposed to be done).
Now the standard bean JNDI name has changed from
"UserManager/remote" to
"UserManager/remote-com.mypackage.UserManager"
Is that normal? Anybody can give me any ideas on the reason for this?
I have had to change the hardcoded standard lookup code in the clients or make xml deploying descriptors.
Thanks for any help,
Ignacio
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264887#4264887
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264887
16 years, 5 months
[jBPM Users] - Re: Advice regarding complex proccess modeling
by saraswati.santanu
How about creating sub-tasks in you actual task? Signalling flag will be false for the sub-tasks by default. So it will not transit to the next node till you call complete on the super task.
The following code may be used when the review task becomes active
| Task reviewTask = taskService.createTaskQuery()
| .activityName("Review")
| .processInstanceId(processInstanceId)
| .uniqueResult();
|
| for (String userId:userIds) {
| TaskImpl subTask = reviewTask.createTask("Review for user "+userId)
| .addCandidateUser(userId);
|
| reviewTask.addSubTask(subTask);
| }
|
When an user performs review then you can execute something like this:
| //somehow get the review task
| Task reviewTask = taskService.createTaskQuery()
| .activityName("Review")
| .processInstanceId(processInstanceId)
| .uniqueResult();
|
| //some get the sub task for this user
| Task reviewSubTask = taskService.createTaskQuery()
| .activityName("Review for user "+userId)
| .processInstanceId(processInstanceId)
| .uniqueResult();
|
| //complete the sub task
| taskService.completeTask(reviewSubTask.getId());
|
| //remove sub task from the super task
| reviewTask.removeSubTask(reviewSubTask);
|
| //if there exists not sub task then move on
| if (reviewTask.getSubTasks().isEmpty()) {
| taskService.completeTask(reviewTask.getId());
| }
|
This is just an idea I got now. I have never tried this. So the code may not be accurate. Let me know if it works.
You may need to create a node altogether if you need to implement your own activity behaviour. You cannot really assign your own behaviour to the existing Task node of Jbpm. This also can be an approach to solve this problem.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264867#4264867
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264867
16 years, 5 months
[jBPM Users] - Re: [jBPM 4.1] Process Definition XML File
by saraswati.santanu
Koen,
My two cents. All that people might need is a nice wrapper over a DOM API which makes Jpdl xml writing using Java code simpler. This may not really require to touch any of the core classes for this. For e.g. I can write something like:
| //this is the step where we generate the xml dynamically
| JpdlWriter writer = new JpdlWriter();
| String xmlString = writer.startNode("Start Node Name")
| .transition("Transition Name", "Next Task")
| .task("Next Task")
| ... etc.
| .xml();
|
| //this is deployment, which is the same even for a static xml, read from a file
| String deploymentId = repositoryService.createDeployment()
| .addResourceFromString(resourceName, xmlString)
| .deploy();
|
I would assume the JpdlWriter class and any other associated classes will not do anything with the real process definition object. However code above is just a random thought to elaborate the idea.
I believe something like this Sebastian suggested and you also mentioned.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264858#4264858
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264858
16 years, 5 months