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

[Design of JCA on JBoss] - Re: Datasources not parsing jboss.server.data.dir

by clebert.suconic＠jboss.com

I forgot to mention... After you start jboss on trunk, you will see a directory called ${jboss.server.data.dir} under JBOSS/bin View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068345#4068345 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068345

17 years, 9 months

1
0
0 / 0

[Design of JCA on JBoss] - Datasources not parsing jboss.server.data.dir

by clebert.suconic＠jboss.com

Maybe someone already brought this up, but as I couldn't find any thread in a quick search... On jboss-5/trunk, DefaultDS is using this URL to connect to HSQLDB: jdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}localDB I was trying to look at my tables using the HSQLDB DatabaseManager, but because of this issue, the Database still empty, and we aways have two HSQLDB instances running on the JVM. Is that a known issue? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068343#4068343 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068343

17 years, 9 months

1
0
0 / 0

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

by manik.surtani＠jboss.com

Reopening http://jira.jboss.com/jira/browse/JBCACHE-725 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068269#4068269 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068269

17 years, 9 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Testsuite Failures

by ryan.campbell＠jboss.com

Please see this wiki page for instructions on how to run the test suite against the EAP: http://wiki.jboss.org/wiki/Wiki.jsp?page=HowToRunTheTestsuiteAgainstJBossEAP Thanks to Richard Achmatowicz for writing this up. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068268#4068268 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068268

17 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation handling impl

by adrian＠jboss.org

"alesj" wrote : | But I'm not sure we can port all of them, meaning those that use the same class for instantiating two different instances. You can override the annotations in the xml. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068262#4068262 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068262

17 years, 9 months

1
0
0 / 0

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

by flavia.rainone＠jboss.com

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

17 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation handling impl

by alesj

"adrian(a)jboss.org" wrote : | You haven't been following that approach in some of your tests | which is something I've been meaning to bring up. | Hmm, I tried to follow that approach, but apparently missed some of them. If you know which one's are those, let me know :-), but otherwise I can have a look. "adrian(a)jboss.org" wrote : | But now we need a third set | 3) Same Test using annotations. Yup. But I'm not sure we can port all of them, meaning those that use the same class for instantiating two different instances. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068256#4068256 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068256

17 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 : | I think we can in most cases, but when we can't your idea looks a good one. | Just as long as it isn't an all or nothing. i.e. you can use it to override | just one property where the annotations are currently inadequete | rather than having to recode everything. | | anonymous wrote : | | | | | interface ManagedPropertyConstraintsPopulator | | | { | | | /** Populate the ManagedProperty fields constraint related info | | | */ | | | populateManagedProperty(Class attachmentClass, PropertyInfo info, Fields fields); | | | } | | | | | If we also define a ManagedPropertyConstraintsPopulatorFactory, then we can introduce a constraintsFactory field to the ManagementProperty annotation to simplify the registration of the supplier. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068249#4068249 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068249

17 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation handling impl

by adrian＠jboss.org

I haven't looked at the details, but one issue is to me is how we test (including new features going forwards). The original MC tests came in two versions: 1) Test using BeanMetaData programmatically 2) Same Test using XML You haven't been following that approach in some of your tests which is something I've been meaning to bring up. But now we need a third set 3) Same Test using annotations. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068241#4068241 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068241

17 years, 9 months

1
0
0 / 0

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

by charles.crouch＠jboss.com

"scott.stark(a)jboss.org" wrote : | 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. | Thats a better way to put it Scott. Its not that its a bad thing to care about, there are just lots more important things to care about instead. Adrian, I wasn't arguing against innovation in the management layer as defined by the developer. It would be the responsibility of whoever maintained the console to make sure any integration layer with the app server's manageable components stayed in sync. I agree that assuming core dev's will maintain a separate management piece, external to their own annotations etc, is unrealistic. However I believe its equally unlikely that developers would want/be able to provide sufficient metadata to enable any dynamically driven management and administration console to have sufficient usability. It would more likely boil down to a lowest common denominator, much like the current jmx-console. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068238#4068238 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068238

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