April 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBoss ESB] - ESB 4.6 release schedule

by Kevin.Conner＠jboss.com

Now is the time for us to consider the next release of the ESB 4.x stream, the development of which will start shortly. We would like to hear feedback from the community about issues/features you would like to see as part of the release. The schedule we are considering is as follows Requirements capture now - 8th May Discuss requirements for the next project release, primarily focussing on feature requests and improvements to current capabilities. Development 11th May - 26th June Main development tasks will continue, except for Java ONE and f2f meeting. During this phase we will accept additional bug fix requests but most feature requests will be postponed to the next release. Testing June 29th - July 10th Testing of the codebase with critical bug fixes being accepted. Release July 10th. If you have any suggestions then please create a topic within the development forum so that it can be discussed and then reference that topic within the following topic http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224400 Thanks, ESB team View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224402#4224402 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224402

17 years

1
0
0 / 0

[Design of JBoss ESB] - ESB 4.6 tasks for consideration

by Kevin.Conner＠jboss.com

We are about to start development of the next release of the ESB 4.x stream. If you have any suggestions or requirements for the next release then please link forum topics discussing the requirements as follow-ups to this topic. Please do not discuss requirements on this topic. Thanks ESB team. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224400#4224400 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224400

17 years

1
0
0 / 0

[Design of POJO Server] - Re: JSR-299 servlet injection

by pete.muir＠jboss.org

Another option, which is probably easier, is to install a AnnotationProcessor (which wraps and forwards calls to the default AnnotationProcessor in JBossWeb), and delegates at runtime to an AnnotationProcessor which Web Beans exposes to the ServletContext on contextInitialized. I took this approach for the plain Tomcat integration https://svn.jboss.org/repos/webbeans/extensions/trunk/tomcat/support/src/... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224394#4224394 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224394

17 years

1
0
0 / 0

[Design of Management Features on JBoss] - Re: ManagementView.process()

by ips

I also think it would be more intuitive if at least the component that was just updated or removed was automatically updated/removed in the view (i.e. the next time getComponents*() are called). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224360#4224360 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224360

17 years

1
0
0 / 0

[Design of Management Features on JBoss] - Re: ManagementView.process()

by emuckenhuber

"ips" wrote : Can it be removed then, or at least deprecated? Sure - if we don't find another use for this it will be removed or marked as deprecated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224348#4224348 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224348

17 years

1
0
0 / 0

[Design of Management Features on JBoss] - Re: ManagementView.process()

by ips

Can it be removed then, or at least deprecated? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224345#4224345 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224345

17 years

1
0
0 / 0

[Design of Management Features on JBoss] - Re: ManagementView.process()

by emuckenhuber

Hmm mgtView.process() is not really used anymore. So actually none of these require a process() that updates are applied. remove/updateComponent require a reload of the mgtView so that the changes are applied though. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224342#4224342 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224342

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: LargeMessageExample doesn't build

by clebert.suconic＠jboss.com

oops.... it was an accident. If it is a problem.. can someone revert it please? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224336#4224336 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224336

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - LargeMessageExample doesn't build

by timfox

It uses new stuff added for message streams which hasn't been committed yet. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224327#4224327 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224327

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Simplifying the JBM beans deployment

by jmesnil

"timfox" wrote : JNDIServer is completely independent so shouldn't need to be injected anywhere. | What's Naming? Can't see it in jbm-standalone-beans.xml | Naming is the 1st bean defined in jbm-standalone-beans.xml As you said, both jndi beans are already independent. So it leaves only 2 beans to be injectable: - JBMSecurityManager - MBeanServer View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224320#4224320 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224320

17 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2009