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

[Design of JBoss Web Services] - jbossxb 2.0.0.CR2

by scott.stark＠jboss.org

Is there any use of the jbossxb ObjectModelFactory such that the change in jbossxb-2.0.0.CR2 to support property refs is going to impact the current jbossws-jboss50/2.0.0.CR5? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029577#4029577 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029577

19 years

1
0
0 / 0

[Design of JBossXB] - Not seeing property replacement happen

by scott.stark＠jboss.org

I'm not seeing property replacement occur in the GenericObjectModelFactory calls in jboss5. It looks like we only do property replacement when the jbossxb is driven by a schema. To add support for this in the ObjectModelFactorys, is looks like the DelegatingObjectModelFactory.setValue(Object o, UnmarshallingContext navigator, String namespaceURI, String localName, String value) needs to be updated, and that the ObjectModelFactory would be queried for an isReplacePropertyRefs() method to allow it to control whether replacement happens. I'm going to add this as some of the tests rely on property replacement from descriptors. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029564#4029564 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029564

19 years

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBoss and NLB

by diabelos

Ok, well switching to TCP did the trick, however, we still could not use MS NLB because it has some other requirements we were not able to overcome. MS NLB requires an ARP address statically added to the router/switch in the mode we were running it in, which is not the preferred method in the environment we were deploying in. So, instead, we have switched to a HW based NLB solution. I then switched everything back to UDP multicasting, and all seems happy...so far ;) Still, keep in mind, there is some strange incompatibility between MS NLB and UDP multicast JBOSS clusters. Just my 2 cents ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029550#4029550 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029550

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Messaging 1.2 integration in jboss5

by kabir.khan＠jboss.com

I've upgraded the aop release's component-info.xml to fetch in the latest mc release View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029535#4029535 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029535

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Messaging 1.2 integration in jboss5

by kabir.khan＠jboss.com

It is the container from the microcontainer. In aop trunk it is currently using the mc snapshot. I will update it to use the latest release and keep you posted View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029529#4029529 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029529

19 years

1
0
0 / 0

[Design of POJO Server] - Re: Missing EAR/WAR Isolation

by thomas.diesler＠jboss.com

This should be fixed | [tdiesler@tdvaio trunk]$ svn log -v -r61470 | ------------------------------------------------------------------------ | r61470 | thomas.diesler(a)jboss.com | 2007-03-19 23:19:11 +0100 (Mon, 19 Mar 2007) | 1 line | Changed paths: | M /trunk/server/src/main/org/jboss/deployment/AppParsingDeployer.java | M /trunk/server/src/main/org/jboss/deployment/JBossAppParsingDeployer.java | M /trunk/server/src/main/org/jboss/deployment/JBossApplicationObjectFactory.java | M /trunk/system-jmx/src/main/org/jboss/system/deployers/ServiceClassLoaderDeployer.java | | Fix EAR scoping with <loader-repository> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029526#4029526 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029526

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Messaging 1.2 integration in jboss5

by clebert.suconic＠jboss.com

aop is dependent on something while its dependency is not being declared: anonymous wrote : [echo] NOTE: aopc incremental compilation might fail, if so do an ant clean first (see JMESSAGING-271) | [aopc] Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/metadata/spi/signature/Signature | [aopc] at org.jboss.aop.ClassicWeavingStrategy.translate(ClassicWeavingStrategy.java:91) | [aopc] at org.jboss.aop.AspectManager.translate(AspectManager.java:889) | [aopc] at org.jboss.aop.AspectManager.transform(AspectManager.java:832) | [aopc] at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:345) | [aopc] at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:326) | [aopc] at org.jboss.aop.standalone.Compiler.compile(Compiler.java:234) | [aopc] at org.jboss.aop.standalone.Compiler.main(Compiler.java:90) | I suspect this is the Adrian's microcontainer (or microkernel? I confused the names now) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029519#4029519 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029519

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Messaging 1.2 integration in jboss5

by clebert.suconic＠jboss.com

I'm running my testsuite using aop 2.0.0.alph3... and if everything runs ok I will add the dependency on the repository (or take corretive actions) I want a complete run before giving a go.. what should take 4 hours. I will update this thread afterwards... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029518#4029518 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029518

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - org.jboss.test.cts.test.MDBUnitTestCase

by scott.stark＠jboss.org

The MDBUnitTestCase is failing because of this client side error: | 2631 ERROR [ExceptionInterceptor] Caught throwable | java.lang.IllegalStateException: There is already a delivery set for auto ack | at org.jboss.jms.client.state.SessionState.setAutoAckInfo(SessionState.java:372) | at org.jboss.jms.client.container.SessionAspect.handlePreDeliver(SessionAspect.java:257) | at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect_z_handlePreDeliver_195406657.invoke(SessionAspect_z_handlePreDeliver_195406657.java) | at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_N1401156438058258070.invokeNext(ClientSessionDelegate$preDeliver_N1401156438058258070.java) | at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:171) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:106) | at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_N1401156438058258070.invokeNext(ClientSessionDelegate$preDeliver_N1401156438058258070.java) | at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71) | at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_N1401156438058258070.invokeNext(ClientSessionDelegate$preDeliver_N1401156438058258070.java) | at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107) | at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_N1401156438058258070.invokeNext(ClientSessionDelegate$preDeliver_N1401156438058258070.java) | at org.jboss.jms.client.delegate.ClientSessionDelegate.preDeliver(ClientSessionDelegate.java) | at org.jboss.jms.client.remoting.MessageCallbackHandler.receive(MessageCallbackHandler.java:442) | at org.jboss.jms.client.container.ConsumerAspect.handleReceive(ConsumerAspect.java:150) | at org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect_z_handleReceive_195406657.invoke(ConsumerAspect_z_handleReceive_195406657.java) | at org.jboss.jms.client.delegate.ClientConsumerDelegate$receive_N8299950230150603585.invokeNext(ClientConsumerDelegate$receive_N8299950230150603585.java) | at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:171) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:106) | at org.jboss.jms.client.delegate.ClientConsumerDelegate$receive_N8299950230150603585.invokeNext(ClientConsumerDelegate$receive_N8299950230150603585.java) | at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71) | at org.jboss.jms.client.delegate.ClientConsumerDelegate$receive_N8299950230150603585.invokeNext(ClientConsumerDelegate$receive_N8299950230150603585.java) | at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107) | at org.jboss.jms.client.delegate.ClientConsumerDelegate$receive_N8299950230150603585.invokeNext(ClientConsumerDelegate$receive_N8299950230150603585.java) | at org.jboss.jms.client.delegate.ClientConsumerDelegate.receive(ClientConsumerDelegate.java) | at org.jboss.jms.client.JBossMessageConsumer.receive(JBossMessageConsumer.java:86) | at org.jboss.test.cts.test.MDBInvoker.run(MDBInvoker.java:70) | I'm using the 1.2.0.GA with aop version compatibility locally hacked to be 2.0.0.alpha3. What is the source of this error? The test uses basic jms apis. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029517#4029517 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029517

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Messaging 1.2 integration in jboss5

by scott.stark＠jboss.org

The version dependencies are broken. The worst seems to be the aop version which is 1.5.0.GA in jbm, 2.0.0.alpha3 in jboss5: /home/svn/JBossHead/jboss-head/build/build.xml:900: The following error occurred while executing this line: /home/svn/JBossHead/jboss-head/build/build-thirdparty.xml:143: A versioning problem exists: Component: jboss/aop is at version: 2.0.0.alpha3 but it is also required to be compatible with: [Compatible@4b142196{id=null, version=1.5.0.GA}] by: jboss/messaging I'm updating this locally in my repo to see if I can even run with this aop, but there needs to be a jbm release that works with jboss5. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029512#4029512 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029512

19 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 March 2007