[JBoss-dev] [ jboss-Bugs-996536 ] Wrong deployment state for non deployable files
Bugs item #996536, was opened at 2004-07-23 06:28 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=996536group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Bernd Zeitler (frito) Assigned to: Adrian Brock (ejort) Summary: Wrong deployment state for non deployable files Initial Comment: Hi! When deploying files without any suitable deployer in jboss (JBoss 3.2.5), the jar deployer is trying to open this file. This ends up with a ZipException. The ZipException is cought within the class SubDeployerSupport (processNestedDeployments) and a warning is logged. The file is listed within the deployed list with status: deployed and state: STARTED. I assume this file should show up within the incomplete deployment list with state: FAILED. Instead of logging this warning, a DeploymentException should be thrown as mentioned there in the source code. I changed this (attached file) and it works for me. Greetings, Bernd -- Comment By: Scott M Stark (starksm) Date: 2004-12-29 12:52 Message: Logged In: YES user_id=175228 All issues have been moved to http://jira.jboss.com. Existing issues have been moved. New issues will be closed with this canned reponse. -- Comment By: Bernd Zeitler (frito) Date: 2004-09-14 07:33 Message: Logged In: YES user_id=603154 After posting this to the forum, Scott Stark suggested to reopen the bug. The files mentioned above should show up in the incomplete deployment list with state FAILED. The forum post: http://www.jboss.org/index.html?module=bbop=viewtopict=54103 -- Comment By: Adrian Brock (ejort) Date: 2004-08-26 09:51 Message: Logged In: YES user_id=9459 Your change would mean typos are unexpectedly ignored. You can exclude files using a filter. See conf/jboss-service.xml !-- The Filter specifies a java.io.FileFilter for scanned directories. Any file not accepted by this filter will not be deployed. The org.jboss.deployment.scanner.DeploymentFilter rejects the following patterns: #*, %*, ,*, .*, _$*, *#, *$, *%, *.BAK, *.old, *.orig, *.rej, *.bak, *,v, *~, .make.state, .nse_depinfo, CVS, CVS.admin, RCS, RCSLOG, SCCS, TAGS, core, tags -- attribute name=Filterorg.jboss.deployment.scanner.DeploymentFilter/attribute -- Comment By: Bernd Zeitler (frito) Date: 2004-07-23 07:17 Message: Logged In: YES user_id=603154 ... better: don't deploy these files while adding them to the waiting for deployer list. The jar deployer should not try to deploy it. Greetings, Bernd -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=996536group_id=22866 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-996536 ] Wrong deployment state for non deployable files
Bugs item #996536, was opened at 2004-07-23 13:28 Message generated for change (Comment added) made by frito You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=996536group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Bernd Zeitler (frito) Assigned to: Adrian Brock (ejort) Summary: Wrong deployment state for non deployable files Initial Comment: Hi! When deploying files without any suitable deployer in jboss (JBoss 3.2.5), the jar deployer is trying to open this file. This ends up with a ZipException. The ZipException is cought within the class SubDeployerSupport (processNestedDeployments) and a warning is logged. The file is listed within the deployed list with status: deployed and state: STARTED. I assume this file should show up within the incomplete deployment list with state: FAILED. Instead of logging this warning, a DeploymentException should be thrown as mentioned there in the source code. I changed this (attached file) and it works for me. Greetings, Bernd -- Comment By: Bernd Zeitler (frito) Date: 2004-09-14 14:33 Message: Logged In: YES user_id=603154 After posting this to the forum, Scott Stark suggested to reopen the bug. The files mentioned above should show up in the incomplete deployment list with state FAILED. The forum post: http://www.jboss.org/index.html?module=bbop=viewtopict=54103 -- Comment By: Adrian Brock (ejort) Date: 2004-08-26 16:51 Message: Logged In: YES user_id=9459 Your change would mean typos are unexpectedly ignored. You can exclude files using a filter. See conf/jboss-service.xml !-- The Filter specifies a java.io.FileFilter for scanned directories. Any file not accepted by this filter will not be deployed. The org.jboss.deployment.scanner.DeploymentFilter rejects the following patterns: #*, %*, ,*, .*, _$*, *#, *$, *%, *.BAK, *.old, *.orig, *.rej, *.bak, *,v, *~, .make.state, .nse_depinfo, CVS, CVS.admin, RCS, RCSLOG, SCCS, TAGS, core, tags -- attribute name=Filterorg.jboss.deployment.scanner.DeploymentFilter/attribute -- Comment By: Bernd Zeitler (frito) Date: 2004-07-23 14:17 Message: Logged In: YES user_id=603154 ... better: don't deploy these files while adding them to the waiting for deployer list. The jar deployer should not try to deploy it. Greetings, Bernd -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=996536group_id=22866 --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-996536 ] Wrong deployment state for non deployable files
Bugs item #996536, was opened at 2004-07-23 13:28 Message generated for change (Comment added) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=996536group_id=22866 Category: JBossServer Group: v3.2 Status: Closed Resolution: Wont Fix Priority: 5 Submitted By: Bernd Zeitler (frito) Assigned to: Adrian Brock (ejort) Summary: Wrong deployment state for non deployable files Initial Comment: Hi! When deploying files without any suitable deployer in jboss (JBoss 3.2.5), the jar deployer is trying to open this file. This ends up with a ZipException. The ZipException is cought within the class SubDeployerSupport (processNestedDeployments) and a warning is logged. The file is listed within the deployed list with status: deployed and state: STARTED. I assume this file should show up within the incomplete deployment list with state: FAILED. Instead of logging this warning, a DeploymentException should be thrown as mentioned there in the source code. I changed this (attached file) and it works for me. Greetings, Bernd -- Comment By: Adrian Brock (ejort) Date: 2004-08-26 16:51 Message: Logged In: YES user_id=9459 Your change would mean typos are unexpectedly ignored. You can exclude files using a filter. See conf/jboss-service.xml !-- The Filter specifies a java.io.FileFilter for scanned directories. Any file not accepted by this filter will not be deployed. The org.jboss.deployment.scanner.DeploymentFilter rejects the following patterns: #*, %*, ,*, .*, _$*, *#, *$, *%, *.BAK, *.old, *.orig, *.rej, *.bak, *,v, *~, .make.state, .nse_depinfo, CVS, CVS.admin, RCS, RCSLOG, SCCS, TAGS, core, tags -- attribute name=Filterorg.jboss.deployment.scanner.DeploymentFilter/attribute -- Comment By: Bernd Zeitler (frito) Date: 2004-07-23 14:17 Message: Logged In: YES user_id=603154 ... better: don't deploy these files while adding them to the waiting for deployer list. The jar deployer should not try to deploy it. Greetings, Bernd -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=996536group_id=22866 --- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-996536 ] Wrong deployment state for non deployable files
Bugs item #996536, was opened at 2004-07-23 13:28 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=996536group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Bernd Zeitler (frito) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong deployment state for non deployable files Initial Comment: Hi! When deploying files without any suitable deployer in jboss (JBoss 3.2.5), the jar deployer is trying to open this file. This ends up with a ZipException. The ZipException is cought within the class SubDeployerSupport (processNestedDeployments) and a warning is logged. The file is listed within the deployed list with status: deployed and state: STARTED. I assume this file should show up within the incomplete deployment list with state: FAILED. Instead of logging this warning, a DeploymentException should be thrown as mentioned there in the source code. I changed this (attached file) and it works for me. Greetings, Bernd -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=996536group_id=22866 --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-996536 ] Wrong deployment state for non deployable files
Bugs item #996536, was opened at 2004-07-23 13:28 Message generated for change (Comment added) made by frito You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=996536group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Bernd Zeitler (frito) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong deployment state for non deployable files Initial Comment: Hi! When deploying files without any suitable deployer in jboss (JBoss 3.2.5), the jar deployer is trying to open this file. This ends up with a ZipException. The ZipException is cought within the class SubDeployerSupport (processNestedDeployments) and a warning is logged. The file is listed within the deployed list with status: deployed and state: STARTED. I assume this file should show up within the incomplete deployment list with state: FAILED. Instead of logging this warning, a DeploymentException should be thrown as mentioned there in the source code. I changed this (attached file) and it works for me. Greetings, Bernd -- Comment By: Bernd Zeitler (frito) Date: 2004-07-23 14:17 Message: Logged In: YES user_id=603154 ... better: don't deploy these files while adding them to the waiting for deployer list. The jar deployer should not try to deploy it. Greetings, Bernd -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=996536group_id=22866 --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
