[JBoss JIRA] Resolved: (JBAS-6722) Hot deployment broken with JBoss 5.0.1.GA
by Dimitris Andreadis (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-6722?page=com.atlassian.jira.plug... ]
Dimitris Andreadis resolved JBAS-6722.
--------------------------------------
Resolution: Done
> Hot deployment broken with JBoss 5.0.1.GA
> -----------------------------------------
>
> Key: JBAS-6722
> URL: https://jira.jboss.org/jira/browse/JBAS-6722
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Component
> Environment: JBoss 5.0.1 GA
> JDK 5 update 16
> Seam trunk
> Reporter: Jozef Hartinger
> Assignee: Ales Justin
> Priority: Critical
> Fix For: JBossAS-5.2.0.Beta1
>
>
> Hot deployment does not seem to work. I am using seam-gen to create a war packaged application and deploy it on JBoss 5.0.1 GA. It deploys fine, but:
> a) deployment of XHTML template
> modified facelet templates are not being picked up
> b) deployment of action Java Bean
> I run new-action to create a ping action component and run "explode" target. Component does not deploy. There is nothing in the server log that would indicate that server is even trying to load the component.
> All mentioned above works fine on JBoss 4.2.3 and JBoss 5.0.0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Created: (JBAS-7309) Seam Navigation Fails with Jboss AS 5.2Beta1
by Cody Lerum (JIRA)
Seam Navigation Fails with Jboss AS 5.2Beta1
--------------------------------------------
Key: JBAS-7309
URL: https://jira.jboss.org/jira/browse/JBAS-7309
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-5.2.0.Beta1
Environment: Windows 7 x64. Java 6 Update 16 x64. JBoss 5.2Beta1. Seam 2.2.0GA or Seam 2.2.1Nightly
Reporter: Cody Lerum
When a Seam-Gen generated project is deployed as an ear (compressed or exploded) to the server everything appears to deploy without error. The app can be brought up to the main page but if you click login and then submit the form via the Login button a blank page is rendered.
I have tested this both Seam 2.2.0GA and Seam 2.2.1Nightly.
To reproduce generate a new ear project via seam-gen. deploy to server and navigate to the login.seam page. Fill out the form and click login.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Created: (JBAS-7183) RepositoryClassLoader tries to call ClassNotFoundException.initCause
by Markus Kilås (JIRA)
RepositoryClassLoader tries to call ClassNotFoundException.initCause
--------------------------------------------------------------------
Key: JBAS-7183
URL: https://jira.jboss.org/jira/browse/JBAS-7183
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.2.3.GA
Environment: OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu11), OpenJDK 64-Bit Server VM (build 14.0-b08, mixed mode)
Reporter: Markus Kilås
After redeployment of one of two enterprise applications living on the server I get an "IllegalStateException: Can't overwrite cause" from the RepositoryClassLoader (see attached stacktrace) when a web module is being initialized. After some investigation I suspect the reason for an error could be that both applications shares some utility class and therefore both the enterprise applications has to be undeployed.
This however should not cause an illegal state exception. Looking in the source of RepositoryClassLoader indicates that the intended error message should be "Invalid use of destroyed classloader UCL destroyed" but the code tries to call Throwable.initCause() on an java.lang.ClassNotFoundException which is not allowed causing an IllegalStateException.
A simple fix would be to use the constructor that takes a cause instead of explicitly call initCause() (see attached patch (untested)).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months