You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Eelco Hillenius (JIRA)" <ji...@apache.org> on 2007/10/16 07:51:52 UTC

[jira] Resolved: (WICKET-384) JMC registration with JBoss 4.x

     [ https://issues.apache.org/jira/browse/WICKET-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eelco Hillenius resolved WICKET-384.
------------------------------------

    Resolution: Won't Fix

Seems to be a stale issue.

> JMC registration with JBoss 4.x
> -------------------------------
>
>                 Key: WICKET-384
>                 URL: https://issues.apache.org/jira/browse/WICKET-384
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 2.0 branch (discontinued)
>         Environment: Jave 1.5_11, Win XP, JBoss 4.0.4
>            Reporter: Stefan Lindner
>            Priority: Minor
>
> After a wicket application's war file once is deployed, it can't be deployed a second time. All JBoss 4.x versioins throw an Exception that this application was already undeployed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.