September 2007 - jboss-dev-forums

[Design the new POJO MicroContainer] - NumberFormatExceptions when mixing annotations and number fo

by kabir.khan＠jboss.com

Some of the aop-mc-int tests are failing. Why are they not being run in cruisecontrol? They all seem to be doing something like the following (taken from MetaDataTestCase): | <bean name="Bean1" class="org.jboss.test.microcontainer.support.PropertyBean"> | <property name="intProperty">10 | <annotation>@org.jboss.test.microcontainer.support.Test</annotation> | </property> | <property name="stringProperty">Bean1</property> | </bean> | This used to work, but now gives the following error: | *** DEPLOYMENTS IN ERROR: Name -> Error | Bean1 -> java.lang.NumberFormatException: For input string: "10 | | " | | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalValidate(AbstractKernelDeployer.java:260) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(AbstractKernelDeployer.java:174) | at org.jboss.test.kernel.junit.MicrocontainerTestDelegate.validate(MicrocontainerTestDelegate.java:223) | at org.jboss.test.kernel.junit.MicrocontainerTest.setUp(MicrocontainerTest.java:68) | at junit.framework.TestCase.runBare(TestCase.java:125) | at junit.framework.TestResult$1.protect(TestResult.java:106) | at junit.framework.TestResult.runProtected(TestResult.java:124) | at junit.framework.TestResult.run(TestResult.java:109) | at junit.framework.TestCase.run(TestCase.java:118) | at junit.framework.TestSuite.runTest(TestSuite.java:208) | at junit.framework.TestSuite.run(TestSuite.java:203) | at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) | at junit.extensions.TestSetup$1.protect(TestSetup.java:19) | at junit.framework.TestResult.runProtected(TestResult.java:124) | at junit.extensions.TestSetup.run(TestSetup.java:23) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) | at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138) | at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:163) | at org.apache.maven.surefire.Surefire.run(Surefire.java:84) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:244) | at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:814) | | testPropertyMetaData(org.jboss.test.microcontainer.test.MetaDataTestCase) Time elapsed: 0 sec <<< ERROR! | java.lang.IllegalStateException: Incompletely deployed: | If I get rid of all line breaks in the property it works, i.e. | <bean name="Bean1" class="org.jboss.test.microcontainer.support.PropertyBean"> | <property name="intProperty">10<annotation>@org.jboss.test.microcontainer.support.Test</annotation></property> | <property name="stringProperty">Bean1</property> | </bean> | But this would make it less readable in case of multiple annotations. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087370#4087370 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087370

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Beta3 blocking issues

by charles.crouch＠jboss.com

So comparing your list will all the Beta3 critical/blockers in jira: http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=true&&fixfor=... You don't have in your list: http://jira.jboss.com/jira/browse/JBAS-4687 Use a tagged release for the new jboss-ejb3-cache module http://jira.jboss.com/jira/browse/JBAS-4660 Fix jboss-head-testsuite-sun-1.5 regression when the testsuite runs under hudson I guess if these shouldn't be in the release we should drop them from being critical. What about the other subtasks and dependencies of http://jira.jboss.com/jira/browse/JBAS-4562 Track jboss and thirdparty dependencies upgrades for JBoss 5.0.0.Beta3, which are currently only marked as major, i.e. http://jira.jboss.com/jira/browse/JBAS-4689 Upgrade JBoss messaging to 1.4.0.GA http://jira.jboss.com/jira/browse/JBAS-4716 Update common-core to 2.2.2.GA Should these be upped to being critical? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087369#4087369 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087369

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Beta3 blocking issues

by scott.stark＠jboss.org

Note that the DataSource deployment template stuff needed to get the ProfileServiceUnitTestCase running (could be part of http://jira.jboss.com/jira/browse/JBAS-3415, Port RARDeployer) is something Weston is working. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087353#4087353 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087353

18 years, 6 months

2
1
0 / 0

[Design of POJO Server] - Beta3 blocking issues

by scott.stark＠jboss.org

The blocking/critical issue status is: http://jira.jboss.com/jira/browse/JBAS-4562 - Need an MC 2.0.0.Beta5 release, Ales has changes, we need to synch on any other changes. I created a JBossMC-2.0.0.Beta5 release due on 24/Sep/07 for these. Assigned to Scott. http://jira.jboss.com/jira/browse/JBAS-4562,JBAS-4506 - Need a jboss-metadata release and unifying metadata. I'm working on the legacy org.jboss.metadata usage in the server module. We need to agree on a model that allows the ejb3 deployers to work with annotations, metadata complete/incomplete descriptors, profileservice overrides. Assigned to Scott. http://jira.jboss.com/jira/browse/JBAS-4744 - Update to JBossXB 2.0.0.CR5, this is blocking the jboss-metadata release. We need to get sufficient implementation for the legacy metadata dom element wildcards to handle current uses. Assigned to Alexey. http://jira.jboss.com/jira/browse/JBAS-3410,JBAS-3412 - VDF Deployer migration tasks (JBAS-3410), Port ClientDeployer and complete JavaEE5 support. The client deployer needs the unified metadata. Assigned to Scott. http://jira.jboss.com/jira/browse/JBAS-4620 - NPE in EJB3 Authentication Interceptor. Needs to be validated by Anil. http://jira.jboss.com/jira/browse/JBAS-4675,JBAS-4690 - transaction local issues Johnathon is working on. http://jira.jboss.com/jira/browse/JBAS-3350 - NPE on service-ref in web.xml, old issue that needs to be verified. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087349#4087349 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087349

18 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Cosmetic change. MC annotations. Is it worth it?

by alesj

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

18 years, 6 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Cannot see uploaded common-core snapshot

by pgier

"dimitris(a)jboss.org" wrote : Let me understand this better. | | I upload (mvn deploy) a snapshot here: | https://snapshots.jboss.org/maven2/org/jboss/jboss-common-core/2.2.2-SNAP... | | You say that the following will be automatically updated: | https://svn.jboss.org/repos/repository.jboss.org/jboss/common-core/2.2.2.... | | ? It won't be automatically updated. For the common-core build to deploy to the old repository, you have to either deploy it manually, or use the jboss-deploy plugin http://labs.jboss.com/maven-jboss-deploy-plugin/ The jboss-deploy plugin will copy the jar files to a local checkout of repository.jboss.org, and attempt to create a component-info.xml file. Then you still have to do an svn commit. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087346#4087346 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087346

18 years, 6 months

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: TxServerInterceptor hardwiring

by jhalliday

Is the 4.2/EAP using this integration.jar already or is it going to? The new API will need backporting at some point or we won't be able to do JTS in the EAP. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087341#4087341 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087341

18 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Cosmetic change. MC annotations. Is it worth it?

by alesj

OK, I'll be moving all those IoC to annotations to .api. package + fixing kernel's pom.xml to build this annotation artifact separate. And this should then go into Scott's changes regarding MC beta5 for AS beta3. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087320#4087320 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087320

18 years, 6 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Trying to release jboss-ejb3-cache

by pgier

Maybe you can try running again from a fresh svn checkout? I've had problems similar to this before with the svn metadata getting out of sync. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087316#4087316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087316

18 years, 6 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Snapshot thirdparty dependencies

by pgier

It should follow the same rules a jboss projects. Meaning if the dependencies are release versions, then they should go into repository.jboss.org. Otherwise, if you are building a snapshot version of the dependency from source, then it should go into the snapshot repo. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087313#4087313 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087313

18 years, 6 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 September 2007