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

[Design of JCA on JBoss] - Re: JCA AOP-MC Integration

by weston.price＠jboss.com

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

17 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JCA AOP-MC Integration

by kabir.khan＠jboss.com

If you run into any problems point me to the code and I'll take a look :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022738#4022738 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022738

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: [O/T] Bug/issue triage

by brittm

Ronald, I'm so glad you brought this up. I'm having to take the approach of 'just wait and see' what I get with a new release. Banking on what is projected in Jira has already bitten me (the description tag and one or two others that seem to keep being pushed to the next release). I'd love to have the time to peruse the beta's, but I'm too busy puting jBPM to work. --not complaining, just chiming in. -Britt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022734#4022734 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022734

17 years, 2 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: jboss/remoting 2.2.0.Alpha7 not compatible with jboss5

by ovidiu.feodorov＠jboss.com

Beautiful. We're looking forward to remoting-http-jbossweb, remoting-http-tomcat5, etc. Maybe this will also solve our HTTP stress test failures? :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022731#4022731 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022731

17 years, 2 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - org.jboss.web.tomcat.security.RunAsListener

by pthurmond＠jboss.com

We've seen some contention in several different performance tests related to RunAsListener. See http://mail-archives.apache.org/mod_mbox/tomcat-dev/200702.mbox/<45DD8ADD.6040801%40apache.org> According to Remy in the thread above, the current implementation of InstanceSupport should not be used for anything other than debugging purposes. Maybe InstanceSupport could be changed to use some concurrent type, rather than array? --Phillip View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022728#4022728 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022728

17 years, 2 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: jboss/remoting 2.2.0.Alpha7 not compatible with jboss5

by scott.stark＠jboss.org

For jboss5 that is probably all that is needed. If remoting has to create remotting-http-jbossweb, remoting-http-tomcat5, remoting-http-jetty6, ... then the jbm piece that depends on the http stack needs to be separable so that the required http stack is selected. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022727#4022727 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022727

17 years, 2 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: jboss/remoting 2.2.0.Alpha7 not compatible with jboss5

by ovidiu.feodorov＠jboss.com

"scott.stark(a)jboss.org" wrote : If you don't care about http, then why did you say "Messaging needs remoting HTTP support...". That dependency links to an http stack regardless of what it is. | OK. That's fine with us. But why do I have to specify a specific HTTP stack version? Why can't we just say "we use Remoting 2.2.0 and whatever Remoting 2.2.0 uses as HTTP stack" Remoting 2.2.0 was presumably tested with several HTTP stacks, let them decided what's best. IF I have to specify that I depend on jboss-remoting-core.jar 2.2.0 and jboss-remoting-http.jar 2.2.0, that's perfect. If this is all we need to do, then the story is over. We're happy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022724#4022724 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022724

17 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JCA AOP-MC Integration

by weston.price＠jboss.com

Thanks for looking into it BTW. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022718#4022718 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022718

17 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JCA AOP-MC Integration

by weston.price＠jboss.com

I assume I can do the same thing against HEAD now right? That is, the prototypes are simply that, prototypes; I really need to be able to use the same functionality against HEAD. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022717#4022717 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022717

17 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JCA AOP-MC Integration

by kabir.khan＠jboss.com

"adrian(a)jboss.org" wrote : The prototypes are here: | http://fisheye.jboss.org/browse/JBoss/jboss-jca | http://fisheye.jboss.org/browse/JBoss/rars | I have fixed these so they now work with all tests passing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022716#4022716 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022716

17 years, 2 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 February 2007