September 2008 - jboss-dev-forums

[Design of EJB 3.0] - Re: EJBTHREE-1454 Encapsulate Container infomation in TO/VO

by bstansberry＠jboss.com

I ran the clustered tests on Friday and saw some errors that weren't there last time I looked a couple weeks ago. I see 4 in ForeignPartitionLocalInterceptorUnitTestCase, 3 in SimpleIsLocalInterceptorUnitTestCase, 1 in NestedBeanUnitTestCase. The last one is expected, the first two are new. All are repeated with buddy replication (BR) enabled and disabled. I tell you this so you don't freak and think you broke something. I suspect the new ones are some simple deployment problem; will look closer on Monday. Also, the tests in the org.jboss.ejb3.test.clusteredentity.unit package are not relevant to this work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176395#4176395 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176395

17 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-1454 Encapsulate Container infomation in TO/VO

by ALRubinger

* The patch has a series of errors in the Proxy SessionContainerTestCase, references to container.getName(). How were we handling this in InvokableContext - is "getName" valid, or should these references be using "getGuid" or "getDispatcherRegistrationName"? * We should consider renaming "InvokableContext"; it contains a reference to JBossSessionBeanMetaData, so something denoting that this is related to sessions might be useful. Perhaps we introduce a hierarchy, where "InvokableContext" remains generic, and "InvokableSessionContext" inherits from this and add the "getMetadata" method. * There are some formatting-only changes in Core SessionSpecContainer. If possible can we exclude these? :) * Aside from that, the APIs are cleaned, all Unit Tests pass (with some fudging to work around the compiler errors mentioned above), so the only other prereq for a commit is to make sure that the Clustered Integration Tests in the EJB3 TestSuite continue to pass so that we don't give Brian a stroke. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176387#4176387 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176387

17 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: PackageInformation retrieved from wrong jar

by stan.silvert＠jboss.com

I committed the fix. The test now passes. Stan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176368#4176368 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176368

17 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: PackageInformation retrieved from wrong jar

by scott.stark＠jboss.org

I added the following test to classloading-vfs which is currently failing: | Failed tests: | testCorrectPackage(org.jboss.test.classloading.vfs.policy.test.PackageInfoUnitTestCase) | | Tests run: 101, Failures: 1, Errors: 0, Skipped: 0 | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176350#4176350 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176350

17 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: PackageInformation retrieved from wrong jar

by scott.stark＠jboss.org

Why we are returning the wrong package is that the search for the matching file via the findVirtualFileInfo is not precisce enough to locate a package. We just find the first matching file: | protected VirtualFileInfo findVirtualFileInfo(String path) | { | VirtualFileInfo result = vfsCache.get(path); | if (result != null) | return result; | | for (VirtualFile root : roots) | { | try | { | // Any jar with a class in the package or a subpackage will have a match | VirtualFile file = root.getChild(path); | Stan's patch requires that the match either be a file that is a leaf, or a directory that contains at least one leaf. Since this method is only used to find class files or packages, this seems like an acceptable restriction. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176348#4176348 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176348

17 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: PackageInformation retrieved from wrong jar

by stan.silvert＠jboss.com

"alesj" wrote : "scott.stark(a)jboss.org" wrote : Is this the same jboss-seam-booking.ear we are pulling into the jbossas testsuite? | | | Yes. | | Now I understand the cause behind why log info 'Seam version null' | sometimes popped up. :-) Right. That's the problem I've been working on. The Seam numberguess example exhibits the same behavior. I've attached a version to the jira that has a special value for the implementation version in the jboss-seam-numberguess.jar. So you should know be able to see clearly how it is getting the manifest from the wrong jar. Stan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176337#4176337 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176337

17 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-5895; Processing too many classes

by scott.stark＠jboss.org

I'll have to look into why that is. I thought there was an excluded notion added to the classpath so you have have a number of roots, and exclusions to further restrict what gets added. What we need out of the structure phase are the classpath roots + inclusion/exclusion filters. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176335#4176335 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176335

17 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - The PostgreSQL Issue

by thomas.diesler＠jboss.com

17 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-1454 Encapsulate Container infomation in TO/VO

by jaikiran

Andrew, I have attached a patch to the issue. Please review when you have some free time. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176307#4176307 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176307

17 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: PackageInformation retrieved from wrong jar

by alesj

"scott.stark(a)jboss.org" wrote : Is this the same jboss-seam-booking.ear we are pulling into the jbossas testsuite? | Yes. Now I understand the cause behind why log info 'Seam version null' sometimes popped up. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176305#4176305 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176305

17 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 2008