August 2006 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: First real SARDeployer porting issue

by adrian＠jboss.org

"scott.stark(a)jboss.org" wrote : One way to handle this and maintain backward compatibility with implicit classpath jars nested in a deployment would be to add a notion to the AspectDeployer interface regarding whether deployment content that is not accepted by a deployer should be added to the containing deployment classpath. | This is what I originally defined as the JAR structure deployer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964462#3964462 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964462

19 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-100, lifecycle dispatch thread context class

by adrian＠jboss.org

This should really be done for all callouts to the bean. i.e. it should be in KernelControllerContextAction::dispatchJoinPoint() View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964460#3964460 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964460

19 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Pushing beans into the kernel

by adrian＠jboss.org

It's related but not the same. The feature there was to pass an Object and some metadata. It goes through all the normal lifecycle except instantation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964458#3964458 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964458

19 years, 8 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: classloader problems in doing injection framework

by scott.stark＠jboss.org

It should be fully setup at that time. Is there a deployment in the testsuite that shows what you are trying to do? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964457#3964457 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964457

19 years, 8 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: classloader problems in doing injection framework

by bill.burke＠jboss.com

I'm still having problems with classloading. I moved the annotation processing for WARs in the start() method of the WebappLoader to make absolutely sure that the classloader is initialized and ready to go before processing annotations. I'm still getting the same exact problem at boot time of not being able to discover a WS class that is deployed in a JAR the same level as the WAR (see above) Is there any classloader procesing that happens after the WebappLoader has started? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964440#3964440 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964440

19 years, 8 months

1
0
0 / 0

[Design of POJO Server] - First real SARDeployer porting issue

by scott.stark＠jboss.org

The SARDeployer is getting deployed in the MC and the legacy jmx kernel is setup for the mbeans, and the SARDeployer is attempting to deploy the *-service.xml mbeans. This is currently failing due to a change in how the deployment class loader is handled In jboss-4.0.x some deployers have a classpath notion, others do not. For the current failing deployment (jboss-aop-jdk50.deployer, ignoring this needs to be ported to the new VDF) , there are nested jars that are not getting added to the deployment classpath. In jboss-4.0.x this would be done by the nested jars falling through the JARDeployer, which added any jars not looking like deployments to the classpath. In the new VDF, the deployment classpath is managed by the ClassLoadingDeployer, and it operates on classpath metadata from the deployment (META-INF/Class-Path, jars a deployer says should be on the classpath (ear/lib, war/lib), custom classloading.xml descriptor, etc.). A JARDeployer does not really fit into the VDF scheme because every deployer sees every deployment. One way to handle this and maintain backward compatibility with implicit classpath jars nested in a deployment would be to add a notion to the AspectDeployer interface regarding whether deployment content that is not accepted by a deployer should be added to the containing deployment classpath. For the SARDeployer this would be, for the EARDeployer, WARDeployer it would be false. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964433#3964433 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964433

19 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: JPDL Eclipse Graphical Editor - problem building.

by falazar

Ok, we have built and installed the Site GPD a couple times now, but it appears that when we create a new process, I can add all the node types, but cannot use the transition connection tool. It allows me to click the start point, and tries to draw the line, but will not attach to the end point. (Eclipse 3.2.0) Is it working for or only for 3.1 versions still or? Also, what is the technical difference between the site and the feature installations that are built? We have been using the Site installation always. Can we get a small readme.html file in the upper directory there just to briefly say what the two directories represent. That would go a long way towards clearing that up for newer users. Also in the site readme, it says: anonymous wrote : | <h4>If you extracted the archive :</h4> | On the next page, press the 'New Archived Site...' button. Navigate to the archive | containing this file, select it and press the 'Open' button. | | <h4>If you did not extract the archive or if you are using the starters kit :</h4> | | On the next page, press the 'New Local Site...' button. Navigate to the folder containing this file, select it and press the 'Open' button. | I assume, and tried to see, from looking, that it should be reversed shouldnt it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964402#3964402 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964402

19 years, 8 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - JBoss deleting HttpSession on each call to Post-Method?

by Stichel

Hi, I am observing that JBoss (3.2.3 and 3.2.8) kills the HttpSession object on each call do the doPost()-Method executed by the same client. That's why session.isNew() always gives back 'true' (session-Object was newly created). I override the default HttpSession timeout on a per-webapp basis in web.xml with the entry: <session-config> <session-timeout>-1</session-timeout> </session-config> There is no other call to session.setMaxInactiveInterval() in my application. Any suggestions? Thanks! P.S.: Using JDK 1.4 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964336#3964336 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964336

19 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: JPDL Eclipse Graphical Editor - problem building.

by kukeltje

no, it is the project file on the top level... I'll add the target to .cvsignore (still a little hasitation on checking things in, I do not want to do the WRONG things and get spanked ;-) Normally I'm the one doing the spanking) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964284#3964284 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964284

19 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-100, lifecycle dispatch thread context class

by scott.stark＠jboss.org

Adding the following code to the installAction does solve the problem. | // Dispatch the joinpoint using the target class loader | joinpoint.setTarget(target); | ClassLoader tcl = Thread.currentThread().getContextClassLoader(); | try | { | if( cl != null ) | Thread.currentThread().setContextClassLoader(cl); | dispatchJoinPoint(context, joinpoint); | } | finally | { | if( cl != null ) | Thread.currentThread().setContextClassLoader(tcl); | } | I checked this in with similar additions to the uninstallAction. If this looks fine I'll close the issue tomorrow. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964224#3964224 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964224

19 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 August 2006