[JBM.1.4.0.SP3 \ jboss-4.2.2.GA]
Hi,
>From a remote JBM client point of view we need some JBoss jars including jbossall-client.jar (http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone...). I see two main problems with this:
1) The order of this jars does matter - this I think is not even mentioned into the docs, but if you list them into your classpath into a different order it will not work some times. The bigger problem is that in some places/containers there is no way to specify any such order like in tomcat for example.
2) If your project uses some library which is duplicated in jbossall-client.jar also and the versions are different - again we have a problem. One such example is hibernate.
I have found in this thread http://www.jboss.org/index.html?module=bb&op=viewtopic&t=153853&postdays=... that
anonymous wrote : jbossall-client.jar is an evil aggregation of jars. You will need to use the individual client jars from /jboss/client. I have changes the examples to make use of the correct jars, and we have documented the minimal set for JBM, but depending on the other EE features you use you may need to add more client jars...
So, the question is what is the minimal set of client jars needed for a remote JBM client?
And does this will solve problem 1) ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258047#4258047
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258047
The reference guide has a topic about this: "13.9.3. Link to other pages."
// Get the ParentNode. Since we are inside a Window, the Parent is the Page
| PortalNode thisNode = req.getPortalNode().getParent();
| // Get the Node in the Portal hierarchy tree known as "../default"
| PortalNode linkToNode = thisNode.resolve("../default");
| // Create a RenderURL to the "../default" Page Node
| PortalNodeURL pageURL = resp.createRenderURL(linkToNode);
| // Output the Node's name and URL for users
| Samples
| 149
| html.append("Page: " + linkToNode.getName() + " -> ");
| html.append("<a href=\"" + pageURL.toString() + "\">" + linkToNode.getName() + "</a>");
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258045#4258045
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258045
I commented on this again since I consider this really important because at the moment it makes you change your process model for escalations which is probably not wanted. If this was possible in 3.x this would also lead to problems when migrating from 3.x to 4.x, right?
Regarding the behaviour in 3.x Joram stated in the comments answering your question:
anonymous wrote :
| The most logical is not necessarily what was in 3 ;-)
|
| But you are right: in 3, the task is kept open, but it can't be completed anymore. The only option is than to delete the task. Imo, this makes sense.
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258038#4258038
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258038