May 2007 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: Javadoc fixes

by alesj

"adrian(a)jboss.org" wrote : | So you can play with all you like now. :-) Hehe. Will do for sure. Pulling of some Dillons. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042976#4042976 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042976

17 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Support dynamic "usage" relationships between resources

by bytor99999

Can we add support for related resources? For example this JMS Topic is configured to currently use this other JMS Queue as a dead letter queue. Mark View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042972#4042972 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042972

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Javadoc fixes

by adrian＠jboss.org

I've pretty much finished with the base classloader code now (except for adding the Translator support). So you can play with all you like now. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042967#4042967 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042967

17 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Retrieving state/availability information on an individual r

by bytor99999

Is there going to be a way to determine if a service or resource is available, meaning successfully deployed and running? We think some resources and services might also need more detailed state of the deployment, such the following examples. For applications this will be states like "STARTING UP", "FAILED TO DEPLOY" For resources this will be states like o "PAUSED": if a Connector has been paused o "STOPPED": if DataSource has had its underlying connection pool stopped o "NOT INSTALLED": if a resource is known to the profile service but is has not been installed. Thanks Mark View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042965#4042965 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042965

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Duplicated clientIds

by clebert.suconic＠jboss.com

We have recently added a check on Duplicated ClientIDs based on integration tests: - That we can't have two connections using the same ClientId. Reading the JMS Spec, section 4.3.2, it clearly says that "such an attempt of sharing individual clients shouldn't result in messages being lost or doubly processed". so, I read from that that there is no requirement from the spec about ClientIDs.. You could even have multiple Subscriptions with the same ID as long we share the load with them without creating duplications or loosing messages. So.. we will be dropping that check. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042963#4042963 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042963

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Expand the ManagedObject spi to operations/runtime prope

by bytor99999

So our priorities regarding operations, we are first looking for simple void operation() methods. But at some point later handle the Object operation(args) type of methods. :) Mark View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042956#4042956 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042956

17 years, 8 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: JBoss Logging and JBoss AOP

by kabir.khan＠jboss.com

"scott.stark(a)jboss.org" wrote : Hopefully that is resolved with the separation of the logging spi from jdk/log4j impls. | I'm repackaging AOP for the next 2.0.alpha, and am putting in the jars for jboss logging. I am in doubt about what to ship with though. The minimum needed to run is the jboss-logging-spi.jar, which uses the NullLoggerPlugin, so there is no logging. In order to have any meaningful logging we would need to add jboss-logging-log4j.jar and log4j.jar. Are the any reasons why these should NOT be part of the aop download? This mainly applies to people running aop standalone, in the app server all the necessary bits and pieces are obviously present. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042938#4042938 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042938

17 years, 8 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Cluster Aware Cache Policy for the Jaas Security Manager

by sneusatz

I've taken a look in the jboss-cache project and it seemed to me that it suits our need of a cluster aware security cache. Besides managing the consistency of cache state in all cluster nodes, it allows for a number of configurations, such as replication messages mode (sync/async) and eviction policies (LRU, MRU, FIFO, etc). Currently, the JaasSecurityManagerService instantiates a TimedCachePolicy by default. If we were to make the cache policy configurable, we would have to make some arrangements (like, for example, creating a new CachePolicy subclass to handle clustered environments and allowing the user to define which policy is to be used). On the other hand, maybe it would be possible to simply redefine the cache solution used by JaasSecurityManager to use solely the cluster-aware policy (since TreeCache can also be used in non-clustered environments). In any case, the time-out behaviour of the TimedCachePolicy could be achieved by registering eviction policies that would cause the nodes to be evicted after a configurable amout of time. A TreeCacheListener would then register for eviction events and cause the principal to be logged out upon reception of such an event. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042876#4042876 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042876

17 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Do you have a plan that supports XPDL?

by wkzk

Hi Ronald. Thank you for your reply. Wow. super-exciting stuff out there!! BPEL2 is on the same line,too. By the way, I'm a member of Japan JBoss User Group, and I 've translated jPDL user guide ver.3.1 and 3.2(currently working on) from English to Japanese. There 's so much to look forward to "lightning" ;-) Shige View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042848#4042848 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042848

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - VFS changes

by scott.stark＠jboss.org

I have started working on removing the excessive String usage due to creation of too many URLs in the vfs in the https://svn.jboss.org/repos/jbossas/projects/vfs/branches/urlconn-work branch. The current checkpoint changes include: - The vfsurl and url as the primary key for a VirtualFileHandler has been dropped. Instead there is the URLConnection for the associated VFSContext and a relative path. - The use of JarFile and JarURLConnection has been dropped. Instead there is a VFSJarFile abstraction that allows for alternate jar file implementations, and this is obtained from the URLConnection.getContent call. Issues: - In working through some testsuite problems, its seems clear to me that the vfsjar notion should be dropped. A jar is not a protocol. Its a content type. A url like: vfsfile:root/some.ear/some.war/WEB-INF/lib/some.jar is a filesystem entity that may or may not include structured files encoded as jars. The StructuredVirtualFileHandler instances along the path should encapsulate this, not the url. - The current protocol handlers based on VirtualFileURLConnection have a circular relationship to the VirtualFileHandler codebase. There are circular dependencies showing up in calls like URLConnection.getContent and URLConnection.getLastModified. This needs to be cleaned up by having the protocol handlers depend on AbstractURLHandler rather than the VirtualFileHandler. We were pushing url notions into AbstractVirtualFileHandler that should not be there. - Still need to look at how the vfs protocol and contexts Bill added relate to these issues. Once I get the testsuite running I'll update this thread. If you have any comments in the meantime post them here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042812#4042812 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042812

17 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2007