This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | JBoss AOP Exception when deploying WAR file for JBoss 5.x AS | ||
---|---|---|---|
Product: | serverplugins | Reporter: | toni_braecksten |
Component: | JBoss | Assignee: | Petr Hejl <phejl> |
Status: | RESOLVED INCOMPLETE | ||
Severity: | normal | CC: | dkonecny, phejl, pjiricka |
Priority: | P3 | ||
Version: | 7.0 | ||
Hardware: | PC | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Maven war project failing to auto deploy on JBoss AS 5.x |
Description
toni_braecksten
2011-01-05 08:58:16 UTC
Changed component to JBoss Deploy on Save has never been supported on JBoss. The exception is just info. If it does not cause other problems it is ok. Would be interesting to know the exact version and configuration of server/domain possibly with sample to app to reproduce. Thanks for feedback. Since I am a Netbeans newbie - but enthusiastic one - I wasn't aware that there is no DeployOnSave support for JBoss AS. The problem is quite easy to reproduce because the automatic update of the JBoss deployment fails overtime - that was my experience. I assume the main problem is that the war/ear artifact is not deployed as an exploded file by the Netbeans IDE. If the Netbeans Maven plugin would deploy the file in exploded mode - e.g. like the maven-cargo-plugin - then the DeployOnSave function might work. Nevertheless I will attach a sample project. For my tests I use the JBoss AS version 5.0.0 with default server configuration. Created attachment 104947 [details]
Maven war project failing to auto deploy on JBoss AS 5.x
Maven war project that cannot be automatically deployed on save for JBoss AS 5.x
|