March 2010 - jboss-dev-forums - Jboss List Archives

[jBPM Development] New message: "Re: Perhaps a bug in createHistoryActivityInstanceQuery when process has a fork"

by Maciej Swiderski

JBoss development, A new message was posted in the thread "Perhaps a bug in createHistoryActivityInstanceQuery when process has a fork": http://community.jboss.org/message/529268#529268 Author : Maciej Swiderski Profile : http://community.jboss.org/people/swiderski.maciej Message: -------------------------------------------------------------- Yeah, I would be happy to contribute, just needs some hints how Thanks Maciej -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529268#529268

15 years, 7 months

1
0
0 / 0

[Clustering Development] New message: "Re: Partition and Node identities"

by jaikiran pai

JBoss development, A new message was posted in the thread "Partition and Node identities": http://community.jboss.org/message/529264#529264 Author : jaikiran pai Profile : http://community.jboss.org/people/jaikiran Message: -------------------------------------------------------------- > mailto:david.lloyd@jboss.com wrote: > > > > In terms of implementation, my few minutes of research on the topic indicate that the best way to calculate a default node name at boot would be as follows. > 1. Define a system property, "jboss.host.qualified.name" or just "host.qualified.name", which, if unspecified, defaults to the value of:1. the HOSTNAME env var, or if that is not specified, > 2. the COMPUTERNAME env var, or if that is not specified, > 3. the value of InetAddress.getLocalHost().getHostName(), or if that does not turn up anything, > 4. a default value such as "unknown-host.unknown-domain" > > 2. Define a system property, "jboss.host.name" or just "host.name", which, if unspecified, defaults to host portion of the above property > 3. Define a system property, "jboss.node.name" which, if unspecified, defaults to the value of the above property > Given this above scheme, 2 +independent+ (non-clustered) instances of JBossAS running on the same machine, might end up with the same node name unless the user explicitly specifies a unique jboss.node.name for each of those instances, isn't it? Maybe we should by default take into account the -b option to determine the default node name? That way, the user can just continue doing: run.sh -c default -b 127.0.0.1 run.sh -c custom -b 127.0.0.2 and the node names would then be 127.0.0.1 and 127.0.0.2 respectively. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529264#529264

15 years, 7 months

1
0
0 / 0

[Clustering Development] New message: "Partition and Node identities"

by David Lloyd

JBoss development, A new message was posted in the thread "Partition and Node identities": http://community.jboss.org/message/529257#529257 Author : David Lloyd Profile : http://community.jboss.org/people/david.lloyd@jboss.com Message: -------------------------------------------------------------- In Remoting 3, we introduce the concept of an "Endpoint". An Endpoint is an instance of a node in a connected graph of Remoting participants. Each Endpoint has a name which identifies it to its peers; thus one would generally ensure that the name is unique within this graph. In an appserver setting, there would typically be a single Endpoint instance per AS instance. Thus, it meshes strongly with the notion of having a single identity per AS instance. And since it is common to have a single AS instance per host, it would appear to make sense to default the AS identity to be equivalent to the host's identity (the host name, to be more specific - not the DNS name of an interface, but the name of the host itself). Today, we configure clustered JBossAS instances with a "jboss.partition.name" which represents the identity of the cluster of which it is a part. However as far as I've been able to figure out, we do not have a hard-and-fast concept of a node name. I would like to propose a system property "jboss.node.name" which represents the identity of the node itself. This property would have a sensible default but would also be modifiable just as partition name is today. In terms of implementation, my few minutes of research on the topic indicate that the best way to calculate a default node name at boot would be as follows. 1. Define a system property, "jboss.host.qualified.name" or just "host.qualified.name", which, if unspecified, defaults to the value of:1. the HOSTNAME env var, or if that is not specified, 2. the COMPUTERNAME env var, or if that is not specified, 3. the value of InetAddress.getLocalHost().getHostName(), or if that does not turn up anything, 4. a default value such as "unknown-host.unknown-domain" 2. Define a system property, "jboss.host.name" or just "host.name", which, if unspecified, defaults to host portion of the above property 3. Define a system property, "jboss.node.name" which, if unspecified, defaults to the value of the above property (The host name identification scheme described above has been reported to work on Windows, POSIX-like OSes, and Mac OS, barring the event of the environment being cleared for some reason, of course.) When the Remoting Endpoint is instantiated, it will then use the value of this property to name the endpoint, which also acts as the default authentication realm for incoming connections. The concept of a node name is also used in a few other places that I've found: * It appears to be used by mod_jk for identification purposes * Seems that it might be used by jgroups and/or jbcache and/or infinispan for something? Thoughts/feedback? -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529257#529257

15 years, 7 months

1
0
0 / 0

[JCA Development] New message: "Re: Standalone JCA: JNDI binding for multiple connection factories..."

by Jesper Pedersen

JBoss development, A new message was posted in the thread "Standalone JCA: JNDI binding for multiple connection factories...": http://community.jboss.org/message/529252#529252 Author : Jesper Pedersen Profile : http://community.jboss.org/people/jesper.pedersen Message: -------------------------------------------------------------- I see 3 ways of defining the JNDI name for CFs and AOs: 1. Container: The container defines the name - user-friendly - based on the strategy used 2. Static: JNDI binding names are defined in metadata - f.ex. jboss-ra.xml 3. "Dynamic": JNDI binding names are defined external to the resource adapter - f.ex. in a -ds.xml file We have to define an interface for the JNDI binding strategy for the container part - as we will most likely use different strategies based on the environment we are running in - standalone, embedded and inside AS. The best solution would be to have a "static" unique JNDI name defined for each connection factory and admin object - which the strategy then just links to. But lets start with the most common case, and most user-friendly: container defined, and only one connection factory and one admin object. Then we can go from there. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529252#529252

15 years, 7 months

1
0
0 / 0

[JBoss Portal Development] New message: "Why is JB Portal gone? Is GateIn Portal really the replacement?"

by Dave Godbey

JBoss development, A new message was posted in the thread "Why is JB Portal gone? Is GateIn Portal really the replacement?": http://community.jboss.org/message/529236#529236 Author : Dave Godbey Profile : http://community.jboss.org/people/dgodbey Message: -------------------------------------------------------------- Not too long ago my group evaluated a number of open source portal products for a customer. We evaluated JBP, Liferay, and Exo. We didn't like Exo much, and we spent most of our time with Liferay and JBP. While Liferay was slick looking and did many of the things our customer wanted, it did not do EVERYTHING our customer wanted. Since the customer wanted everything that they wanted, we chose JBP for ease of customization and integration with other products. No sooner did we get out of the gate (pun intended) customizing JBP for the customer, we learned that 2.7.2 was the end of the road for JBoss Portal, and that GateIn products were the future for JBoss portal products. Unfortunately, in our view, GateIn Portal comes up short compared to Liferay (it is the same kind of product, shiny and self-contained). But then there is the Portlet Container. Our interest is in the portal toolkit, as JBP appears to be. Perhaps the GateIn Portlet Container product will fit the bill, but it is not nearly as functional as JBP was, and it looks as though the activity is with GateIn Portal right now. What happened? Are there discussions or threads where I might catch up with the JBP history and its giving way to GateIn? Dave PS I also posted on the testimonial/discussion board, but the activity there seems to be negligible, so I posted here -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529236#529236

15 years, 7 months

1
0
0 / 0

[JCA Development] New message: "Re: Standalone JCA: JNDI binding for multiple connection factories..."

by Scott Marlow

JBoss development, A new message was posted in the thread "Standalone JCA: JNDI binding for multiple connection factories...": http://community.jboss.org/message/529234#529234 Author : Scott Marlow Profile : http://community.jboss.org/people/smarlow@redhat.com Message: -------------------------------------------------------------- For resource adapter deployment, we could implement a CF jndi name distinguisher that generates the jndi name based on known variables (such as number of connection factories present and configuration properties if there are multiple factories). -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529234#529234

15 years, 7 months

1
0
0 / 0

[jBPM Development] New message: "Re: Perhaps a bug in createHistoryActivityInstanceQuery when process has a fork"

by Ronald van Kuijk

JBoss development, A new message was posted in the thread "Perhaps a bug in createHistoryActivityInstanceQuery when process has a fork": http://community.jboss.org/message/529230#529230 Author : Ronald van Kuijk Profile : http://community.jboss.org/people/kukeltje Message: -------------------------------------------------------------- And it is not difficult to get extra info in the history table either, so contributions in that area are welcome to -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529230#529230

15 years, 7 months

1
0
0 / 0

[Security Development] New message: "Re: Auth Cache is not flushed after logout"

by Jean-David Maillefer

JBoss development, A new message was posted in the thread "Auth Cache is not flushed after logout": http://community.jboss.org/message/529228#529228 Author : Jean-David Maillefer Profile : http://community.jboss.org/people/jidehem Message: -------------------------------------------------------------- Yes, I tested on JBoss 5.1. The biggest difference I see is that it's called in a scriptlet inside a JSP page (but does it really matters ?) -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529228#529228

15 years, 7 months

1
0
0 / 0

[JBoss Portal Development] New message: "jsp:include within JBoss Portal"

by Chris Armstrong

JBoss development, A new message was posted in the thread "jsp:include within JBoss Portal": http://community.jboss.org/message/529225#529225 Author : Chris Armstrong Profile : http://community.jboss.org/people/armstrongcr@gmail.com Message: -------------------------------------------------------------- Hopefully someone can help me out with this because it's been driving me nuts all day. I am currently running JBoss AS 4.2.3 JBoss Portal 2.7.2 and JDK 1.6.0_14 I've written a Portlet that does a PortalRequestDispatcher.include of a JSP file (foo.jsp) in the doView method, that jsp file also does a include to another JSP file (boo.jsp) using the <jsp:include> tage. This does include the JSP but my parameters are not getting passed. Here is an example: <jsp:include page="/WEB-INF/jsp/test/boo.jsp"> <jsp:param name="last_name" value="nugget"/> </jsp> I've also tried using the same include to a servlet with the same results. This worked in JBoss Portal 2.2.1. Thanks alot for any help. Chris -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529225#529225

15 years, 7 months

1
0
0 / 0

[JBoss Portal Development] New message: "How to fetch the user details, roles from jboss framework for developing a customized portlet"

by Aiswarya Srinivasan

JBoss development, A new message was posted in the thread "How to fetch the user details, roles from jboss framework for developing a customized portlet": http://community.jboss.org/message/529172#529172 Author : Aiswarya Srinivasan Profile : http://community.jboss.org/people/Aiswarya Message: -------------------------------------------------------------- How to fetch the user details, roles from jboss framework for developing a customized portlet -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529172#529172

15 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2010