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

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBAS-3532 Design

by JerryGauth

I'll take a look at the circular dependency issue using "whenRequired." I won't pursue JBAS-3499; I only mentioned it in case that's what you had in mind as a prerequisite here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067971#4067971 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067971

16 years, 9 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Extraneous pom.xml dependencies in jboss-common and othe

by scott.stark＠jboss.org

The jboss-commons-core dependency on the webdav lib I do agree should be a separate jar, and ultimately be part of the vfs if anything. qdox is used at runtime for parsing aop expressions on annotations as far as I know. The ant tasks should be better factored out of the main artifact, but its not a real runtime dependency. The mc test dependencies on junit, jboss-test and profiler should only require test scope. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067969#4067969 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067969

16 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - AOP Integration with Microcontainer

by flavia.rainone＠jboss.com

http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067964#4067964 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067968#4067968 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067968

16 years, 9 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - AOP Integration with Microcontainer

by flavia.rainone＠jboss.com

Hi, everyone! I need to gather information regarding tasks remaining on the integration of JBoss AOP with the microcontainer. Kabir is on vacation, and that's why I can't ask him. What do we have left? I've taken a look at task http://jira.jboss.com/jira/browse/JBMICROCONT-75. Are there any other tasks besides JBMICROCONT-75 and its subtasks? Any information on the current status of the left tasks will be welcome. :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067964#4067964 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067964

16 years, 9 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBAS-3532 Design

by bstansberry＠jboss.com

As you said, the issue with DRM/ClusterPartition is that it's a circular dependency, making it a wee bit complex for dependency injection. That should be solvable by adding "whenRequired" attributes to the inject elements. I.e in pseudo-xml in cluster-beans.xml: | <bean name="HAPartition" ...> | <property name="distributedReplicantManager"><inject bean="DRM" whenRequired="Create"/></property> | </bean> | <bean name="DRM" ...> | <property name="HAPartition"><inject bean="HAPartition" whenRequired="Instantiated"/></property> | </bean> | The above example could be wrong; it's more there to give you the concept. Idea is you inject the DRM into the HAPartition just before it needs it in create(). You inject HAPartition into DRM early, since a DRM without an HAPartition is basically useless. The MC can analyze this situation and properly instantiate both objects. The schema for beans.xml explains this stuff fairly well; it's in the Microcontainer source at https://svn.jboss.org//repos/jbossas/projects/microcontainer/trunk/kernel... . Valid values for "whenRequired" are the various states the MC moves a bean through as it deploys it: Described Instantiated Configured Create Start Installed I didn't have a chance to properly explore this last Nov when I was looking at this. If you have bandwidth to play with it a bit and try to get it sorted, that would be great. (Note I'm leaving on 2 week vacation in a few hours, so will not be in touch.) Re: JBAS-3499, that's still really low priority. DRM works now, except for a couple JIRAs we need to track down. DRM is mission critical, and with all the stuff there is to do, I have a "if it ain't broke don't fix it" attitude toward making DRM use JBoss Cache. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067961#4067961 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067961

16 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-181 & ManagedDeployments

by scott.stark＠jboss.org

"adrian(a)jboss.org" wrote : We'll have to agree to differ then. ;-) | | P.S. I was planning on writing my own Swing admin console that was entirely | driven by the hints in the ManagedObjects. It might not be pretty, but it will | test whether the information/model can be used to construct "reasonable" UI | for user written deployers whose metadata model we know nothing about. I don't know that I so much disagree as don't want to get too hung up on making this a required feature initially. Certainly in principle the default jmx console could use this to generate a much better default view of the admin capabilities. Its just not a required feature in order for an admin tool to be able to effectively manage a server. I guess the main issue is validating that there are not incompatible evolutions of existing properties, as well as making sure that new properties that need user attention have some support without the tool needing a complete revision. For the ha datasource URLDeliimeter property, its is a new datasource type that does effectively need some synchronization with the admin tool as there can be a lot of hidden complexity in the list of jdbc urls in terms of a tool providing testing to ping the indicated databases. Arguably this also requires a new multi-valued jdbc url property rather than a separator that is used in combination with the old jdbc url. How we deal with this type of evolution best is the question. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067960#4067960 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067960

16 years, 9 months

1
0
0 / 0

[Design of JBossCache] - Re: Too much jboss cache INFO logging

by bstansberry＠jboss.com

Thanks. :) The definition of INFO vs DEBUG there is slightly vague, until you interpret the concept of "service state" in the INFO description in terms of the AS ServiceMBean.getState() definitions; i.e. lifecycle state -- created/started/stopped/destroyed. With that interpretation all these should be at DEBUG. We could cheat and log the version as part of a "Cache started" INFO message. :-) BTW, with the practice of only supporting Platforms, the need to log versions is reduced, since the JBC version is defined by the Platform version. When we support JBC as a Framework, the support tools will be fixed so the customer can properly specify the version in the form they fill out to submit a case. Presumably they know the version if they went to the effort of specifically buying support for it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067955#4067955 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067955

16 years, 9 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - JBAS-3532 Design

by JerryGauth

This issue notes that DRM and DS should be injected into ClusterPartition. This work has been previously accomplished for DS. For DRM, it doesn't look like this is possible until further ground work is done. The issue indicates that DRM is now an independent service but this isn't the case as it has a dependency on ClusterPartition for RPC support, membership services, and state transfer support (at first glance anyways). A separate issue (JBAS-3499) notes that DRM should be refactored to use JBossCache. Maybe this would reduce or eliminate DRM dependencies on ClusterPartition. Another possibility might be to inject JChannelFactory into DRM and have it implement whatever services it requires independently of ClusterPartition. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067951#4067951 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067951

16 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-181 & ManagedDeployments

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | If they can't innvocate around the management views they provide they'll simply ignore it. | They might like to innovate as well. ;-) I've been looking at AOP code too much recently! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067930#4067930 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067930

16 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-181 & ManagedDeployments

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | If they can't innvocate around the management views they provide they'll simply ignore it. | Take an example from JCA. If you wanted the database failover you've previously had to use ha-local-tx-data-source this is because we consider it experimental and didn't want to upset the main jdbc rar. Now its been in the wild and tested, those features are now being rolled into the standard datasource configuration. Are you saying we can't do this? Of course, it needs an annotation that says | @From("jboss-5.0.0") | @ManagedProperty("url-delimiter") | public void setURLDeliimeter(String delimeter) {}; | so we can warn the user in case they want to use the profile on an earlier version than this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067927#4067927 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067927

16 years, 9 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 July 2007