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

[Design of EJB 3.0] - Re: @SecurityDomain changes from AS42 to AS5

by anil.saldhana＠jboss.com

I have been handling the EJB3 security for JBoss5. I will have to take a look at why there are two different annotations representing the same. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138221#4138221 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138221

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: testNotAnEar

by adrian＠jboss.org

I'm going to assume it is cross test pollution since under eclipse the order of tests is deterministic since I use TestSuites. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138220#4138220 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138220

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - testNotAnEar

by adrian＠jboss.org

I'm seeing this test fail "randomly" under maven, but I don't see it fail in Eclipse. What's the story here? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138218#4138218 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138218

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JarEntry as VFS root does not return empty vfspath

by adrian＠jboss.org

"mstruk" wrote : | Lazy init of contextPath is also a mine that makes things blow up when you poke around and play with code. Things would be much more predictable if we just set it through constructor and make it non transient. | I don't remember the code being that difficult, but then I haven't worked on it for a while? IIRC, the path originally was setup lazily, except for the now obsolete jar handler that went through every entry up-front? I don't understand why you can't fall back to getParent().getParent().etc. at the worst? anonymous wrote : | To stick to the issue - I think it would be best to introduce non-transient field boolean isContextRoot to AbstractVirtualFileHandler and init it through constructor. | Sounds like a simple solution, but maybe not so good on memory usage? anonymous wrote : | BTW: Is there a wiki page I can use for a little VFS guide I'm putting together? Where others in-the-know can point out inaccuracies I commit :) | Besides this, I don't know? :-) http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5VirtualFileSystem The original design(s) - it's been few a couple of iterations - were mostly described in the forums. I don't know that anybody has collected the implementation details into a more formal document? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138216#4138216 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138216

18 years

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Possible regression in aop?

by adrian＠jboss.org

If you look at the following test in deployers: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/jboss-deploye... it uses the AOPProxyFactory to test that deployments are getting constructed with the correct scope/metadata, but it is currently failing with the latest aop upgrade. This is the deployer that creates the proxy http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/jboss-deploye... I've confirmed that the metadata passed to the proxy factory has the annotation, but its not triggering the advice getting called when it invokes upon the proxy. That this test fails is not a big issue, since nobody is really using the scoped metadata setup by the deployers, but it could be indicitive of some other problem in aop (assuming its not a broken test that just happened to work before by some fluke? ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138215#4138215 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138215

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: Weird pom in snapshots

by pgier

"adrian(a)jboss.org" wrote : I've found a different problem. | | How does it work out which snapshot is the latest? | | I've got a problem where it should be using snapshot 144 | http://snapshots.jboss.org/maven2/org/jboss/microcontainer/jboss-dependen... | but its actually using snapshot 143 from 4 minutes earlier (but note the time part of the id is before the snapshot number) | http://snapshots.jboss.org/maven2/org/jboss/microcontainer/jboss-dependen... | Maven looks at the metadata file it says which one is the latest. I think I was trying to deploy at the same time as you, so that's how there ended up with some incorrect metadata. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138212#4138212 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138212

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: Weird pom in snapshots

by adrian＠jboss.org

Bizarrely, after doing another snapshot we know how two #144 ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138210#4138210 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138210

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: Weird pom in snapshots

by adrian＠jboss.org

I've found a different problem. How does it work out which snapshot is the latest? I've got a problem where it should be using snapshot 144 http://snapshots.jboss.org/maven2/org/jboss/microcontainer/jboss-dependen... but its actually using snapshot 143 from 4 minutes earlier (but note the time part of the id is before the snapshot number) http://snapshots.jboss.org/maven2/org/jboss/microcontainer/jboss-dependen... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138208#4138208 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138208

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JarEntry as VFS root does not return empty vfspath

by mstruk

Ok, I'm implementing the fix to work with root-name-not-an-empty-string contract. Root node test: | isContextRoot = parent == null | does not work for situations where context root is not the jar itself but a path within it (jar://some/path.jar!/child). In the absence of isRoot field on AbstractVirtualFileHandler one approach is along the line: | public boolean isContextRoot() { | | try | { | VirtualFileHandler ctxRoot = getVFSContext().getRoot(); | return this == ctxRoot; | } | catch (IOException e) | { | throw new RuntimeException("Failed to get context root: ", e); | } | | } | but it blows up on getVFSContext() if handler has been closed - it goes into infinite recursion (because I call isContextRoot() inside initPath() which is called from getPathName() which is called from toString() which is called from Exception generating constructor within getVFSContext()... a mess :) I think it's overkill to blow on getVFSContext() which is just a field retrieval - no logic invoked. We should let the code retrieve the context and let the context blow up later if some operation is invoked on it. Lazy init of contextPath is also a mine that makes things blow up when you poke around and play with code. Things would be much more predictable if we just set it through constructor and make it non transient. To stick to the issue - I think it would be best to introduce non-transient field boolean isContextRoot to AbstractVirtualFileHandler and init it through constructor. BTW: Is there a wiki page I can use for a little VFS guide I'm putting together? Where others in-the-know can point out inaccuracies I commit :) - marko View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138206#4138206 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138206

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: Weird pom in snapshots

by adrian＠jboss.org

"pgier" wrote : "adrian(a)jboss.org" wrote : "pgier" wrote : Sorry, that was me again. I seem to have the touch of destruction lately :( | | | I'm trying to deploy the snapshot-temp version of mc now. Is that in the REFACTORING branch? | | | | | | | No, I was going to update your branch once I had the proper releases. | | Saves me figuring out how to do a mvn release manually. ;-) | | Which branch do you mean? The maven-thirdpary one? If you just update trunk it would be better for me. Then I'll just create a new branch off that one to continue with the thirdparty stuff. | Ok, saves me some work then. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138202#4138202 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138202

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