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

[Design the new POJO MicroContainer] - Re: Class loading debugging

by scott.stark＠jboss.org

Another thing I would like to get is a directed graph of the domains/policies for a package. An example question to be able to answer is what applications are using what versions of an xml parser implementation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123691#4123691 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123691

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-232, VFSUtils.addManifestLocations

by alesj

"scott.stark(a)jboss.org" wrote : I don't know why we need to restrict redundant paths. Any combination of . and .. should be allowed and resolvable to the canonical form without any . or .. | I'll add this with the VFS Beta8 Dimitris mentioned today. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123690#4123690 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123690

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Class loading debugging

by scott.stark＠jboss.org

"adrian(a)jboss.org" wrote : | You mean locally. That's two different questions depending on whether | it exports those resources/classes. | I also assume you mean a domain or the classloading system? | | There's a different question as to whether it can see it from one of its imports | or the domain if it is importAll. But that's just the standard classloading api. | It looks like ClassLoading is best point. "adrian(a)jboss.org" wrote : | 3. What are the classpath elements that are visible starting from a ClassLoader. Sort of a URLClassLoader.toURLs() view. | There's no such thing in general. If the policy is a VFSClassLoaderPolicy then you can ask what its VFS roots are and you could ask what other policies it can see that are VFSClassLoaderPolicys or URLClassLoaders. But the new classloading system has been designed to be flexible. There's no direct dependency of URLs/VFS etc. Somebody can implement a policy how they want. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123688#4123688 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123688

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-232, VFSUtils.addManifestLocations

by alesj

"adrian(a)jboss.org" wrote : That should have been part of this | http://jira.jboss.com/jira/browse/JBMICROCONT-211 | but you only did .. ;-) I fail to see where JIRA issue is mentioning '.', except for stating the fact how its currently handled. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123675#4123675 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123675

18 years, 2 months

1
0
0 / 0

[Design of Management Features on JBoss] - Re: Using xinclude in config files

by snacker

Yeah, I tried a hack similar to that, too. So... I'm not using JBossXB. Thought I was this last time. Is there a setting to use JBossXB instead of the apache stuff? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123670#4123670 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123670

18 years, 2 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: transaction (crash recovery) tests.

by rrajesh

More info in this wiki: http://wiki.jboss.org/wiki/Wiki.jsp?page=TestsuiteGuide View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123668#4123668 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123668

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: ProfileService shutdown and undeploy order

by adrian＠jboss.org

"bstansberry(a)jboss.com" wrote : | BTW, IIRC the failure message has changed; used to mention org.jboss.iiop.naming.ORBInitialContextFactory, perhaps as a CNFE. Wouldn't surprise me if solving the current error condition just brings that one back. Yes, the way it was working, it couldn't see conf/jndi.properties either. When the latest MC code gets into trunk, your stop() will be invoked with the context classloader of your deploy/cluster deployment so all this hacking around with the context classloader in the profile service will go away. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123646#4123646 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123646

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: ProfileService shutdown and undeploy order

by adrian＠jboss.org

Actually there were two issues. 1) The issue described above where deployments were undeployed in random order so the conf/jboss-service.xml classloader which includes jndi.properties was removed too early. 2) The undeploy was using the NoAnnotationURLClassLoader of bootstrap-beans.xml as the context classloader which wouldn't be able to see that classloader anyway. I've fixed (1) http://jira.jboss.com/jira/browse/JBAS-5175 I've hacked around (2), but the proper fix will have to wait for the update to the MC that does the proper context classloader setting http://jira.jboss.com/jira/browse/JBAS-5176 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123642#4123642 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123642

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: ProfileService shutdown and undeploy order

by bstansberry＠jboss.com

The HAPartition bean is just doing this in stopService(): ctx = new InitialContext(); ctx.unbind(boundName); In startService() it's more complicated, but essentially creates a new default InitialContext and does a rebind. So, no accessing a different dependency in stopService(). The bean has a depends on jboss:service=NamingService. Looking at the javax.naming code, it looks like the only way the reported error would happen would be if the conf/jndi.properties file were no longer on the classpath. Would the incorrect ordering problem Adrian's mentioned result in conf/ being taken off the classpath prematurely? BTW, IIRC the failure message has changed; used to mention org.jboss.iiop.naming.ORBInitialContextFactory, perhaps as a CNFE. Wouldn't surprise me if solving the current error condition just brings that one back. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123638#4123638 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123638

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-232, VFSUtils.addManifestLocations

by adrian＠jboss.org

That should have been part of this http://jira.jboss.com/jira/browse/JBMICROCONT-211 but you only did .. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123628#4123628 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123628

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