[Design the new POJO MicroContainer] - Re: Remaing classLoader changes
by alesj
"adrian(a)jboss.org" wrote :
| I'd start with finding out what adds -exp to the name and copies it to tmp
|
| | URL: null, relative: file:/C:/proj
| | ects/jboss5/trunk/build/output/jboss-5.0.0.Beta4/server/default/tmp/deploy/jboss-seam-booking19541-e
| | xp.war/WEB-INF/lib/jboss-seam-debug.jar!/seam.properties
| |
|
| And then sees who references that copy of the information.
It's AbstractWarDeployer, AbstractWarDeployment and TomcatDeployment.
| unit.addAttachment("org.jboss.web.expandedWarClasspath", classpath);
| }
|
| // Indicate that an expanded URL exists
| unit.addAttachment("org.jboss.web.expandedWarURL", expWarUrl, URL.class);
| ...
| // Get the war URL
| // FIXME: JBAS-3812 - TomcatDeployment should use modified WebMetaData
| URL warURL = unit.getAttachment("org.jboss.web.expandedWarURL", URL.class);
| ...
| ArrayList<URL> classpath = (ArrayList<URL>)unit.getAttachment("org.jboss.web.expandedWarClasspath");
|
But I have no idea what's done right and what wrong, to know what causes that duplicate. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122325#4122325
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122325
18 years, 2 months
[Design of JBoss jBPM] - Re: Potential enhancement to jbpm
by kukeltje
Just to make sure we are talking about the same 'problem': jBPM by itself does not deploy anything automatically or even automagically (and certainly not blindly ;-). Something has to call a method on the jBPM API to deploy things (sometimes a startup servlet).
As you mentioned, your application does this, so it is the responsibility of that application to check whether a new version should be deployed. There are multiple reasons for this but one of the major ones is how to determine what a new version is... a hash? timestamp? version number? There has been a lot of discussion about this in the forum. You can have a look at it if you want.
In our company we deploy a processdefinition, or rather a processarchive, the moment a new version of the full application is deployed, even if there is NO new processdefinition or whatever. We keep everything in sync by using CVS, a very reliable way if you 'tag' everything.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122310#4122310
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122310
18 years, 2 months
[Design the new POJO MicroContainer] - Re: Remaing classLoader changes
by adrian@jboss.org
"alesj" wrote : "scott.stark(a)jboss.org" wrote : One difference in behavior I'm seeing that we don't appear to have control over is duplicate resource ordering.
| |
| OK, I must admit I'm not entirely following the discussion. :-)
| But has this got to do something with this:
|
| | 2008-01-22 17:37:32,796 TRACE [org.jboss.seam.as5.vfs.VFSScanner] Root url: vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta4/server/default/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jboss-seam-debug.jar/seam.properties
| | 2008-01-22 17:37:32,796 TRACE [org.jboss.seam.as5.vfs.VFSScanner] File: C:\projects\jboss5\trunk\build\output\jboss-5.0.0.Beta4\server\default\deploy\jboss-seam-booking.ear\jboss-seam-booking.war\WEB-INF\lib\jboss-seam-debug.jar\seam.properties
| | 2008-01-22 17:37:32,796 TRACE [org.jboss.seam.as5.vfs.VFSScanner] URL: file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta4/server/default/deploy/jboss-seam-booking.ear, relative: jboss-seam-booking.war/WEB-INF/lib/jboss-seam-debug.jar/seam.properties
| |
| | 2008-01-22 17:37:33,687 TRACE [org.jboss.seam.as5.vfs.VFSScanner] Root url: jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta4/server/default/tmp/deploy/jboss-seam-booking19541-exp.war/WEB-INF/lib/jboss-seam-debug.jar!/seam.properties
| | 2008-01-22 17:37:33,687 TRACE [org.jboss.seam.as5.vfs.VFSScanner] File: file:\C:\projects\jboss5\trunk\build\output\jboss-5.0.0.Beta4\server\default\tmp\deploy\jboss-seam-booking19541-exp.war\WEB-INF\lib\jboss-seam-debug.jar!\seam.properties
| | 2008-01-22 17:37:33,687 TRACE [org.jboss.seam.as5.vfs.VFSScanner] URL: null, relative: file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta4/server/default/tmp/deploy/jboss-seam-booking19541-exp.war/WEB-INF/lib/jboss-seam-debug.jar!/seam.properties
| |
| I do a ClassLoader.getResources("seam.properties") inside Seam app, and I'm not expecting any non vfs URLs.
| Where does that 'jar:file' come from?
No. As I told you last week, this is showing that both the original and the tmp jar are being added
to the list of VFS files/urls in the classpath. You need to determine what is doing this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122304#4122304
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122304
18 years, 2 months