Thanks. These are added, revision 71310 of AS trunk. JIRA is http://jira.jboss.com/jira/browse/JBAS-5340 . As we discussed they are named "jbm-control" and "jbm-data". Feel free to edit these going forward. FYI I'll probably rename this file to jboss-jgroups-stacks.xml in the next day or so.
Let's keep using this thread to discuss the transport protocol configs, perhaps see if we can agree on common configs for the UDP and TCP protocols that we can share between the "udp" stack and "jbm-control" and/or between the "tcp" stack and "jbm-data". http://jira.jboss.com/jira/browse/JBAS-5341
Also, to control multicast TTL you guys are using ${jboss.messaging.ipttl:8} . The other stacks are all using ${jgroups.udp.ip_ttl:2} . Is using your own property with a value of 8 important to you? It would be nice to use a single property. In most cases I'd think an admin would want the same value for all usages.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139076#4139076
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139076
"adrian(a)jboss.org" wrote :
| Also, I don't know whether you saw my comment, but the way
| the vfsmemory handler is handling URL is brokens.
|
I just commited the following to the MemoryTestCase, and it passes:
| public void testUrlHandling()throws Exception
| {
| URL directory = new URL("vfsmemory://guid");
| URL classes = new URL(directory, "classes");
|
| URL classes2 = new URL(directory + "/classes");
|
| assertEquals(classes, classes2);
| assertTrue(classes.equals(classes2));
| }
|
Did you mean something else? This test looks "weird" :-)
"adrian(a)jboss.org" wrote :
| I think this is because you are doing your own manual parsing of the URL
| instead of using the api as its meant to be used?
|
Sorry, please elaborate a bit?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139064#4139064
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139064
Usually new modes are either mode managed by the portal or by the portlet itself. The portlet mode you are referencing is a pure portal mode, which consist in having the portal sending the instance shared preferences to the portlet associated with the READ_WRITE access mode.
The simple portal that makes the JBoss Portlet Container does not support additional modes because it is out of scope of the product.
JBoss Portal 2.6 (and therefore 2.7) support this feature already, when the portlet is invoked with EDIT_DEFAULTS, the shared instances preferences are provided wit the READ_WRITE access mode.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139058#4139058
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139058
Hi,
Does JBoss PTL Container 2.0 support custom portlet mode? I want to implement a 'edit defaults' mode and tried to add this in the portlet.xml. However no visual control shows up in the portal.
I've used @RenderMode(name = "edit_defaults") on a specific GenericPortlet overriding class method to perform the functionality.
Is there no control shown, due to the fact that PTL Container 2.0 doesn't support security?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139045#4139045
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139045