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

[Design of JBoss Web Services] - Re: Missing BasicInvocationContext class

by mark.little＠jboss.com

OK, so the disconnect may be on my side. I was under the impression that JBossAS 4.2.1 used JBossWS 2.0.0GA, but that may be wrong. If it was an earlier version of JBossWS then there is no problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104645#4104645 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104645

18 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Misleading error when StructuraDeployer throws an except

by adrian＠jboss.org

"alesj" wrote : If we agree on what we want to do, I can push that in as well, since I'm already working on the deployers for JBMICROCONT-187. Do option (2). i.e. allow determineStructure() to throw a DeploymentException and make any Throwable from determineStructure() fail the deployment (not invoke the next structure deployer). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104623#4104623 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104623

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JNDI Binding and ejbcontext test

by adrian＠jboss.org

"wolfc" wrote : Does MC call stop if start fails? | I thought it did. | | Or in general: should start, on error, set the system in the previous state? | I'm in favor, but that contradicts MC. | | Enlighten me. Neither the MC. he old JMX kernel or the deployers call stop/undeploy() if start/deploy() failed. create()/start()/deploy() is expected to clearup after itself if it throws an error. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104620#4104620 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104620

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Great error message!

by adrian＠jboss.org

"wolfc" wrote : Well, you're not showing the entire trace, but my guess is it won't get any better. :-) | | Raise a Jira. I hate these kind of errors. The only way to fix it would be to not use Class.getAnnotation{s}() and instead do it ourselves with javassist. I'm more inclined to raise it as a bug with Sun (need to test it with the latest Java6). It should at least give some indication of the missing class. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104618#4104618 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104618

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: default-activation-config?

by adrian＠jboss.org

"wolfc" wrote : The purpose is to have a template of activation config properties in aop.xml for use by multiple MDBs. Burke had for example DLQ authentication in mind. I'm not talking about aop.xml, I'm taking about the jboss.xml and the annotation on the class, e.g. from the testsuite | @DefaultActivationSpecs({ | @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue") | }) | @MessageDriven(activationConfig = | { | @ActivationConfigProperty(propertyName="destination", propertyValue="queue/defaultedmdbtest") | }) | public class DefaultedQueueTestMDB implements MessageListener | It still doesn't make sense that a template from anywhere would override the real instance properties from ejb-jar.xml? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104616#4104616 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104616

18 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: jUDDI tables dropped at server shutdown

by Kevin.Conner＠jboss.com

Just to clarify, this is also a problem in the 'production' profile of the SOA platform. This is why Trev needs to know how to tidy this up. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104607#4104607 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104607

18 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Missing BasicInvocationContext class

by mark.little＠jboss.com

Yes, but if it was a public API then it has clearly changed between 2.0.0 and 2.0.1. Unless it was marked as a "technology preview" or "unofficial release" or something like that, we now have users who are potentially using this SPI that has changed. You cannot go changing public interfaces like this in minor releases. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104604#4104604 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104604

18 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: jUDDI tables dropped at server shutdown

by kurt.stam＠jboss.com

This is only a problem in the 'all' profile of JBossAS, where AS ships the juddi.sar. From an ESB perspective this should get removed, and we should deploy our juddi.war by default into the jbossesb.sar to bring up the juddi WSs. We *should* not break anything by doing that, but it would be nice if Thomas can tell us what to do to proof this out. --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104598#4104598 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104598

18 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Missing BasicInvocationContext class

by heiko.braun＠jboss.com

With 2.0.0 the SPI did inherit the version from the core code base, because it wasn't released as a standalone binary. This changed with jboss native 2.0.1, which is using the SPI 1.0.0.GA. The SPI shipped with the 2.0.0 code base was actually some 0.x.CR release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104597#4104597 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104597

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: default-activation-config?

by wolfc

The purpose is to have a template of activation config properties in aop.xml for use by multiple MDBs. Burke had for example DLQ authentication in mind. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104592#4104592 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104592

18 years, 4 months

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 November 2007