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

[Design the new POJO MicroContainer] - Re: Eclipse deployer-vfs tests

by alesj

"adrian(a)jboss.org" wrote : | It's not difficult to start eclipse and do file/import/existing projects into workspace, | especially since maven will update the eclipse files for you when change the pom. | | I'm not saying you have to develop with eclipse, but it's a lot easier | if you could debug the problem directly instead of me proxying stacktraces | and logs. This is very debatable topic, since I remember how you once almost ruined my IDEA settings, trying to hack something directly on my machine. :-) But I'll put this on next week's agenda. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166436#4166436 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166436

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Question about Transaction timeouts and Journal

by clebert.suconic＠jboss.com

As we discussed on #jbossmessaging@freenode, I will just block until the transaction is completed... the same way it would happen with a regular sync / NIO. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166434#4166434 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166434

17 years, 8 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Dynamic AOP API

by flavia.rainone＠jboss.com

I agree that we should design a new API. IMHO the design of this API poses quite a challenge to the JBoss AOP team. Being dynamic is one of the strongest points of JBoss AOP and yet we need to provide something easy and intuititve to use, without taking out the power of flexibility (or, at least, try to balance simplicity with flexibililty). I think we should be able of providing most of the options a user has when defining an xml. And I also think it would be a great step to provide overloaded methods as a way of avoiding null parameters. I mean, if you need to use cflow, choose the method with cflow parameter. If you don't need, passing a null cflow is not accepted, use the method without cflow instead (in the current API, you must use null in AdviceBinding constructor to indicate that a binding won't use cflow). What do you say about annotation overrides? Maybe it would be an interesting feature to add it to our dynamic API? Or you think it would just make things too complicated? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166432#4166432 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166432

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Eclipse deployer-vfs tests

by adrian＠jboss.org

"alesj" wrote : Do you know which one? | Can you re-create the problem? | There's no errors in the logs for either these tests | junit.framework.AssertionFailedError: Expected [appc.jar, ejbs.jar, web.jar, services.jar] got [] expected:<4> but was:<0> | at junit.framework.Assert.fail(Assert.java:47) | at junit.framework.Assert.failNotEquals(Assert.java:277) | at junit.framework.Assert.assertEquals(Assert.java:64) | at junit.framework.Assert.assertEquals(Assert.java:195) | at org.jboss.test.deployers.vfs.structure.AbstractStructureTest.assertChildContexts(AbstractStructureTest.java:79) | at org.jboss.test.deployers.vfs.structure.ear.test.EARStructureUnitTestCase.testEARAnnotationScanning(EARStructureUnitTestCase.java:143) | | 0 DEBUG [EARStructureUnitTestCase] ==== Starting testEARAnnotationScanning ==== | 237 DEBUG [VFSStructuralDeployersImpl] Added structure deployer org.jboss.deployers.vfs.plugins.structure.file.FileStructure@c832d2 | 237 DEBUG [VFSStructuralDeployersImpl] Added structure deployer org.jboss.deployers.vfs.plugins.structure.war.WARStructure@1808199 | 237 DEBUG [VFSStructuralDeployersImpl] Added structure deployer org.jboss.deployers.vfs.plugins.structure.jar.JARStructure@1bc887b | 237 DEBUG [VFSStructuralDeployersImpl] Added structure deployer org.jboss.test.deployers.vfs.structure.ear.support.MockEarStructureDeployer@ | a46701 | 245 TRACE [VFSStructuralDeployersImpl] Determining structure for scanning.ear deployers=[org.jboss.deployers.vfs.plugins.structure.war.WARSt | ructure@1808199, org.jboss.test.deployers.vfs.structure.ear.support.MockEarStructureDeployer@a46701, org.jboss.deployers.vfs.plugins.structu | re.jar.JARStructure@1bc887b, org.jboss.deployers.vfs.plugins.structure.file.FileStructure@c832d2] | 259 TRACE [WARStructure] ... no - doesn't look like a war and no WEB-INF subdirectory. | 259 TRACE [WARStructure] Not recognised: scanning.ear | 622 TRACE [VFSStructuralDeployersImpl] scanning.ear recognised by org.jboss.test.deployers.vfs.structure.ear.support.MockEarStructureDeploye | r@a46701 | 623 TRACE [VFSStructureBuilder] Populating deployment vfsfile:/home/ejort/jboss-deployers/deployers-vfs/target/tests-classes/structure/ear/s | canning.ear/ metaData=StructureMetaDataImpl{contexts=[ContextInfoImpl{path= metaData=[META-INF] classPath=null}]} | 644 TRACE [VFSStructureBuilder] Apply context: vfsfile:/home/ejort/jboss-deployers/deployers-vfs/target/tests-classes/structure/ear/scanning | .ear/ ContextInfoImpl{path= metaData=[META-INF] classPath=null} | 646 TRACE [VFSStructureBuilder] Populating Context vfsfile:/home/ejort/jboss-deployers/deployers-vfs/target/tests-classes/structure/ear/scan | ning.ear/ metaData=StructureMetaDataImpl{contexts=[ContextInfoImpl{path= metaData=[META-INF] classPath=null}]} | 647 DEBUG [EARStructureUnitTestCase] testEARAnnotationScanning took 647ms | 647 DEBUG [EARStructureUnitTestCase] ==== Stopping testEARAnnotationScanning ==== | | | junit.framework.AssertionFailedError: null | at junit.framework.Assert.fail(Assert.java:47) | at junit.framework.Assert.assertTrue(Assert.java:20) | at junit.framework.Assert.assertNotNull(Assert.java:214) | at junit.framework.Assert.assertNotNull(Assert.java:207) | at org.jboss.test.deployers.vfs.deployer.bean.test.BeanScanningUnitTestCase.testNoOverride(BeanScanningUnitTestCase.java:124) | | 0 DEBUG [BeanScanningUnitTestCase] ==== Starting testNoOverride ==== | 43 DEBUG [KernelFactory] Starting JBoss Kernel construction... | 282 DEBUG [KernelFactory] Completed JBoss Kernel construction. Duration: 239 milliseconds | 314 DEBUG [DeployersImpl] Added stage Not Installed before null | 315 DEBUG [DeployersImpl] Added stage Parse before ControllerState@1506dc4{PreInstall} | 315 DEBUG [DeployersImpl] Added stage PostParse before ControllerState@1506dc4{PreInstall} | 315 DEBUG [DeployersImpl] Added stage PreDescribe before ControllerState@1506dc4{PreInstall} | 315 DEBUG [DeployersImpl] Added stage Describe before ControllerState@1506dc4{PreInstall} | 315 DEBUG [DeployersImpl] Added stage ClassLoader before ControllerState@1506dc4{PreInstall} | 316 DEBUG [DeployersImpl] Added stage PostClassLoader before ControllerState@1506dc4{PreInstall} | 316 DEBUG [DeployersImpl] Added stage PreReal before ControllerState@1506dc4{PreInstall} | 316 DEBUG [DeployersImpl] Added stage Real before ControllerState@1506dc4{PreInstall} | 316 DEBUG [DeployersImpl] Added stage Installed before ControllerState@1506dc4{PreInstall} | 328 DEBUG [VFSStructuralDeployersImpl] Added structure deployer org.jboss.deployers.vfs.plugins.structure.jar.JARStructure@1a52fdf | 329 DEBUG [VFSStructuralDeployersImpl] Added structure deployer org.jboss.deployers.vfs.plugins.structure.file.FileStructure@3e89c3 | 781 DEBUG [ClassLoaderSystem] DefaultClassLoaderSystem@11dba45 registered domain=ClassLoaderDomain@b03be0{name=DefaultDomain parentPolicy=BE | FORE parent=sun.misc.Launcher$AppClassLoader@13f5d07} | 805 DEBUG [DeployersImpl] Added deployer org.jboss.deployers.vfs.deployer.kernel.BeanDeployer@acb158 for stage Parse | org.jboss.deployers.vfs.deployer.kernel.BeanDeployer@acb158{inputs=[] outputs=[org.jboss.kernel.spi.deployment.KernelDeployment]} | | 806 DEBUG [DeployersImpl] Added deployer org.jboss.deployers.plugins.classloading.ClassLoadingDefaultDeployer@384065 for stage PreDescribe | org.jboss.deployers.plugins.classloading.ClassLoadingDefaultDeployer(a)384065{inputs=[org.jboss.classloading.spi.metadata.ClassLoadingMetaData | ] outputs=[org.jboss.classloading.spi.metadata.ClassLoadingMetaData]} | | 806 DEBUG [DeployersImpl] Added deployer org.jboss.deployers.vfs.plugins.classloader.VFSClassLoaderDescribeDeployer@10bbf9e for stage Descri | be | org.jboss.deployers.vfs.plugins.classloader.VFSClassLoaderDescribeDeployer(a)10bbf9e{inputs=[org.jboss.classloading.spi.metadata.ClassLoadingM | etaData] outputs=[]} | | 806 DEBUG [DeployersImpl] Added deployer org.jboss.deployers.plugins.classloading.AbstractLevelClassLoaderSystemDeployer@513d61 for stage Cl | assLoader | org.jboss.deployers.plugins.classloading.AbstractLevelClassLoaderSystemDeployer(a)513d61{inputs=[org.jboss.deployers.structure.spi.ClassLoader | Factory] outputs=[]} | | 806 DEBUG [DeployersImpl] Added deployer org.jboss.deployers.plugins.annotations.GenericAnnotationDeployer@194d372 for stage PreReal | org.jboss.deployers.plugins.annotations.GenericAnnotationDeployer(a)194d372{inputs=[org.jboss.classloading.spi.dependency.Module] outputs=[org | .jboss.deployers.spi.annotations.AnnotationEnvironment]} | | 806 DEBUG [DeployersImpl] Added deployer org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer@1c5fde0 for stage Real | org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer(a)1c5fde0{inputs=[org.jboss.beans.metadata.spi.BeanMetaData, org.jboss.kernel | .spi.deployment.KernelDeployment] outputs=[org.jboss.beans.metadata.spi.BeanMetaData]} | | 806 DEBUG [DeployersImpl] Added deployer org.jboss.deployers.vfs.deployer.kernel.BeanScanningDeployer@19e8329 for stage Real | org.jboss.deployers.vfs.deployer.kernel.BeanScanningDeployer(a)19e8329{inputs=[org.jboss.beans.metadata.api.annotations.BeanFactory, org.jboss | .deployers.spi.annotations.AnnotationEnvironment, org.jboss.beans.metadata.api.annotations.Bean] outputs=[org.jboss.beans.metadata.spi.BeanM | etaData]} | org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer(a)1c5fde0{inputs=[org.jboss.beans.metadata.spi.BeanMetaData, org.jboss.kernel | .spi.deployment.KernelDeployment] outputs=[org.jboss.beans.metadata.spi.BeanMetaData]} | | 806 DEBUG [DeployersImpl] Added deployer org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer@1b5340c for stage Real | org.jboss.deployers.vfs.deployer.kernel.BeanScanningDeployer(a)19e8329{inputs=[org.jboss.beans.metadata.api.annotations.BeanFactory, org.jboss | .deployers.spi.annotations.AnnotationEnvironment, org.jboss.beans.metadata.api.annotations.Bean] outputs=[org.jboss.beans.metadata.spi.BeanM | etaData]} | org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer(a)1c5fde0{inputs=[org.jboss.beans.metadata.spi.BeanMetaData, org.jboss.kernel | .spi.deployment.KernelDeployment] outputs=[org.jboss.beans.metadata.spi.BeanMetaData]} | org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer(a)1b5340c{inputs=[org.jboss.beans.metadata.spi.BeanMetaData] outputs=[]} | | 869 DEBUG [MainDeployerImpl] Add deployment: vfsfile:/home/ejort/jboss-deployers/deployers-vfs/target/tests-classes/bean/scan_no_override/ | 908 DEBUG [MainDeployerImpl] Scheduling deployment: vfsfile:/home/ejort/jboss-deployers/deployers-vfs/target/tests-classes/bean/scan_no_over | ride/ parent=null | 909 DEBUG [DeployersImpl] Deploying vfsfile:/home/ejort/jboss-deployers/deployers-vfs/target/tests-classes/bean/scan_no_override/ | 937 DEBUG [Domain] org.jboss.classloading.spi.dependency.Domain@3ae941{DefaultDomain} add module VFSDeploymentClassLoaderPolicyModule scan_n | o_override:0.0.0 | 952 DEBUG [BaseClassLoader] Created BaseClassLoader@1e808ca{vfsfile:/home/ejort/jboss-deployers/deployers-vfs/target/tests-classes/bean/scan | _no_override/} with policy VFSClassLoaderPolicy@992bae{name=vfsfile:/home/ejort/jboss-deployers/deployers-vfs/target/tests-classes/bean/scan | _no_override/ domain=null roots=[FileHandler@179514[path=scan_no_override context=file:/home/ejort/jboss-deployers/deployers-vfs/target/test | s-classes/bean real=file:/home/ejort/jboss-deployers/deployers-vfs/target/tests-classes/bean/scan_no_override/]] delegates=null exported=[] | } | 953 DEBUG [BaseClassLoaderDomain] ClassLoaderDomain@b03be0{DefaultDomain} registerClassLoader BaseClassLoader@1e808ca{vfsfile:/home/ejort/jb | oss-deployers/deployers-vfs/target/tests-classes/bean/scan_no_override/} | 1090 DEBUG [DeployersImpl] Fully Deployed vfsfile:/home/ejort/jboss-deployers/deployers-vfs/target/tests-classes/bean/scan_no_override/ | 1090 DEBUG [BeanScanningUnitTestCase] testNoOverride took 1089ms | 1091 DEBUG [BeanScanningUnitTestCase] ==== Stopping testNoOverride ==== | anonymous wrote : | Since I don't use Eclipse, by design. :-) | It's not difficult to start eclipse and do file/import/existing projects into workspace, especially since maven will update the eclipse files for you when change the pom. I'm not saying you have to develop with eclipse, but it's a lot easier if you could debug the problem directly instead of me proxying stacktraces and logs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166431#4166431 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166431

17 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: Whitespace trimming in metadata

by alex.loubyansky＠jboss.com

This is done. The testcase is org.jboss.test.xb.builder.object.jbossxmlpreservewhitespace.test.JBossXmlPreserveWhitespaceUnitTestCase View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166429#4166429 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166429

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Eclipse deployer-vfs tests

by alesj

Do you know which one? Can you re-create the problem? Since I don't use Eclipse, by design. :-) And it should probably be useful to fix any real (non-test) issues before we put that code into AS5 action. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166428#4166428 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166428

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Eclipse deployer-vfs tests

by adrian＠jboss.org

I forget to mention a couple of weeks ago that the deployer-vfs tests were failing again in the annotation scanning when running under eclipse. Last time, the fixes weren't eclipse configuration changes so I'm assuming there is a fundamental problem (bad assumption) with the way this code is working. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166425#4166425 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166425

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBoss with spaces in the directory name

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : It should NOT come in with %20 unless it is from the URLHandler. | i.e. it is an encoded url. | In case it is not obvious, it is the URLHandler that should do the decoding if it is necessary. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166423#4166423 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166423

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBoss with spaces in the directory name

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : It should NOT come in with %20 unless it is from the URLHandler. | i.e. it is an encoded url. | Or you are creating the name from a URI. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166422#4166422 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166422

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBoss with spaces in the directory name

by adrian＠jboss.org

It should come in with %20 unless it is from the URLHandler. i.e. it is an encoded url. Magically changing values on people just leads to all sorts of trouble. e.g. the uppercase/lowercase problem on windows A further example. What if I do mkdir temp/my%20dir I then do temp.getChild("my%20dir"); Oops! Not found because it looked for "my dir" !!!! But the way, the correct URL for the above is file:///.../temp/my%2520dir which decodes to my%20dir :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166421#4166421 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166421

17 years, 8 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 July 2008