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=detail&atid=376685&aid=996536&group_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=bb&op=viewtopic&t=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="Filter">org.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=detail&atid=376685&aid=996536&group_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
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to