January 2008 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: NoCopyNestedJarHandler usage

by scott.stark＠jboss.org

I checked in a fix for the IllegalStateException and using the resulting vfs snapshot does show all of the SeamVFSClassloadingTestCase tests are working. Need to debug the classpath seen by the ULR associated with the deployment. I'm looking at it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118527#4118527 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118527

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: NoCopyNestedJarHandler usage

by scott.stark＠jboss.org

Its not the no-copy case that works as those urls cause the IllegalStateException. Its the default copy mode that is working. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118508#4118508 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118508

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: NoCopyNestedJarHandler usage

by alesj

"scott.stark(a)jboss.org" wrote : The testULRClassloading and testURLClassLoader work with the proper classpath for the no copy case. | But what's the difference then in AS5 AnnotationMetaDataDeployer when using NoCopy, so that the info (now trace) doesn't print out? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118453#4118453 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118453

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: VFS subproject in JIRA and next VFS release.

by dimitris＠jboss.org

Actually, we have the same problem with: - integration - javaee - metadata and possibly others. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118444#4118444 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118444

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: VFS subproject in JIRA and next VFS release.

by alesj

I'm in favor of top level project. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118442#4118442 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118442

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - VFS subproject in JIRA and next VFS release.

by dimitris＠jboss.org

As it stands now the MicroContainer subprojects do not have their own JIRAs / versioning. So VFS although is currently at 2.0.0.Beta6 we don't know exactly what's in this version. We need either to create seperate top level projects, or emulate seperate versioning using the version name, e.g. JBoss VFS-2.0.0.Beta7, and having only VFS issues assigned to a particular fix version. This could be actually simpler than maintaining another top level project. Having solved that, we need to decide what fixes/performance enhancement will go into the next jboss vfs release for inclusion in AS5 Beta4: http://jira.jboss.com/jira/browse/JBAS-5113 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118435#4118435 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118435

18 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: NPE booting Embedded JBoss from trunk

by clebert.suconic＠jboss.com

This will require more time debugging this... I have taken the action of looking into this, and there is something going on with aop. Our aspects are being deployed, but for some reason the PerVM aspect we use is not being applied here. I have added a trace to our code, and I could see where the connection is created: [testng] 2008-01-09 14:45:02,131 13889 INFO [org.jboss.jms.delegate.ConnectionFactoryDelegate] @WorkManager(1)-2 connectionDelegate created = ConnectionDelegate[31261706, ID=g-iasbc8bf-1-aqkbc8bf-ssqw43-110j3, SID=0] state = null | [testng] java.lang.Exception: trace | [testng] at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:197) | [testng] at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) | [testng] at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205) | [testng] at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101) | [testng] at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95) | [testng] at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:137) | [testng] at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83) | [testng] at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48) | [testng] at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:401) | [testng] at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:339) | [testng] at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:692) | [testng] at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) | [testng] at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) | [testng] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) | [testng] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) | [testng] at java.lang.Thread.run(Thread.java:595) | [testng] 2008-01-09 14:45:02,151 13909 WARN [org.jboss.resource.adapter.jms.inflow.JmsActivation] @WorkManager(1)-2 Failure in jms activation org.jboss.resour And we should have StateCreationAspect on the stack trace, before the ConnectionFactoryDelegate. So.. there is something going on with AOP. (which is an InVM aspect), So... someone should debug this from the AOP point of view. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118434#4118434 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118434

18 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: NPE booting Embedded JBoss from trunk

by charles.crouch＠jboss.com

Hi Pete Do the messaging queues and topics still get deployed ok in JBAS5 embedded, or are they bust as well? I realise that they won't be usable since the JMS server won't start, but it would be useful if they could be deployed so they are at least accessible from a management perspective. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118397#4118397 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118397

18 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Does JBossWS optimize local invocations?

by ovidiu.feodorov＠jboss.com

Hi Thomas, Thank you for your answer. It looks like we're talking about effects of two different mechanisms here. One is payload-to-XML serialization, which I understand cannot be avoided, and that is fine. However, for co-located topologies, Remoting allows you a choice of either passing the already-serialized XML payload over the full TCP/IP stack and Tomcat HTTP Connector or just passing it directly to a local connector, which is obviously faster. Does JBossWS take advantage of this second mechanism? Thanks, Ovidiu View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118382#4118382 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118382

18 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBObject/EJBLocalObject in EAP 4.2 CP02

by bdecoste

OK, I'll roll back my changes to the tests. Somehow the Beta3 changes made it into EAP 4.2 CP02 or we broke it in a very similar way. Shouldn't be a major fix - we're just not implementing EJBObject/EJBLocalObject in the proxies unless they are explicitly extended by the interfaces. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118372#4118372 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118372

18 years, 2 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 January 2008