[JBoss JIRA] (RF-13205) Photoalbum: Hibernate error during deployment
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13205?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak updated RF-13205:
-------------------------------
Labels: (was: needs-qe)
> Photoalbum: Hibernate error during deployment
> ---------------------------------------------
>
> Key: RF-13205
> URL: https://issues.jboss.org/browse/RF-13205
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.3.4
> Environment: Photoalbum 4.3.4.20130912-Final
> Reporter: Pavol Pitonak
> Assignee: Brian Leathem
> Priority: Blocker
> Fix For: 4.3.4
>
>
> # build photoalbum and deploy to EAP 6.1.1
> result:
> * there is error during deployment
> * when you open http://localhost:8080/richfaces-photoalbum, you can see application and basic functionality works, however you cannot create a new user
> {quote}
> 17:10:35,171 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (ServerService Thread Pool -- 48) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
> 17:10:35,346 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 48) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 17:10:35,361 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 48) HHH000431: Unable to determine H2 database version, certain features may not work
> 17:10:35,389 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (ServerService Thread Pool -- 48) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
> 17:10:35,392 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 48) HHH000397: Using ASTQueryTranslatorFactory
> 17:10:35,444 INFO [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool -- 48) HV000001: Hibernate Validator 4.3.1.Final-redhat-1
> 17:10:35,866 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000227: Running hbm2ddl schema export
> 17:10:35,874 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Album drop constraint FK_maso23c869ch22pa5q0sh6tok
> 17:10:35,874 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "ALBUM" not found; SQL statement:
> alter table Album drop constraint FK_maso23c869ch22pa5q0sh6tok [42102-168]
> 17:10:35,875 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Album drop constraint FK_j8gbvffe8l1pvbewibj4ft62m
> 17:10:35,875 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "ALBUM" not found; SQL statement:
> alter table Album drop constraint FK_j8gbvffe8l1pvbewibj4ft62m [42102-168]
> 17:10:35,875 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Comment drop constraint FK_j94pith5sd971k29j6ysxuk7
> 17:10:35,875 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "COMMENT" not found; SQL statement:
> alter table Comment drop constraint FK_j94pith5sd971k29j6ysxuk7 [42102-168]
> 17:10:35,875 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Comment drop constraint FK_qh25b5js0rt4fqv9syhyjv781
> 17:10:35,876 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "COMMENT" not found; SQL statement:
> alter table Comment drop constraint FK_qh25b5js0rt4fqv9syhyjv781 [42102-168]
> 17:10:35,876 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Image drop constraint FK_62s883scl1tf1fl7357bbtxy9
> 17:10:35,876 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "IMAGE" not found; SQL statement:
> alter table Image drop constraint FK_62s883scl1tf1fl7357bbtxy9 [42102-168]
> 17:10:35,876 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Image_MetaTag drop constraint FK_qw6hpgbun1gnhr0nimrao8gxc
> 17:10:35,877 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "IMAGE_METATAG" not found; SQL statement:
> alter table Image_MetaTag drop constraint FK_qw6hpgbun1gnhr0nimrao8gxc [42102-168]
> 17:10:35,877 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Image_MetaTag drop constraint FK_rb6l6aoyv7bss6hto77wqnvfg
> 17:10:35,877 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "IMAGE_METATAG" not found; SQL statement:
> alter table Image_MetaTag drop constraint FK_rb6l6aoyv7bss6hto77wqnvfg [42102-168]
> 17:10:35,877 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Shelf drop constraint FK_3unm5rbreqkjurmy4hpfl89yr
> 17:10:35,878 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "SHELF" not found; SQL statement:
> alter table Shelf drop constraint FK_3unm5rbreqkjurmy4hpfl89yr [42102-168]
> 17:10:36,026 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000230: Schema export complete
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (RF-13205) Photoalbum: Hibernate error during deployment
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13205?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-13205:
------------------------------------
I verified that this particular issue was resolved. Issue is ready to be closed.
> Photoalbum: Hibernate error during deployment
> ---------------------------------------------
>
> Key: RF-13205
> URL: https://issues.jboss.org/browse/RF-13205
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.3.4
> Environment: Photoalbum 4.3.4.20130912-Final
> Reporter: Pavol Pitonak
> Assignee: Brian Leathem
> Priority: Blocker
> Fix For: 4.3.4
>
>
> # build photoalbum and deploy to EAP 6.1.1
> result:
> * there is error during deployment
> * when you open http://localhost:8080/richfaces-photoalbum, you can see application and basic functionality works, however you cannot create a new user
> {quote}
> 17:10:35,171 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (ServerService Thread Pool -- 48) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
> 17:10:35,346 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 48) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 17:10:35,361 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 48) HHH000431: Unable to determine H2 database version, certain features may not work
> 17:10:35,389 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (ServerService Thread Pool -- 48) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
> 17:10:35,392 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 48) HHH000397: Using ASTQueryTranslatorFactory
> 17:10:35,444 INFO [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool -- 48) HV000001: Hibernate Validator 4.3.1.Final-redhat-1
> 17:10:35,866 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000227: Running hbm2ddl schema export
> 17:10:35,874 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Album drop constraint FK_maso23c869ch22pa5q0sh6tok
> 17:10:35,874 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "ALBUM" not found; SQL statement:
> alter table Album drop constraint FK_maso23c869ch22pa5q0sh6tok [42102-168]
> 17:10:35,875 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Album drop constraint FK_j8gbvffe8l1pvbewibj4ft62m
> 17:10:35,875 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "ALBUM" not found; SQL statement:
> alter table Album drop constraint FK_j8gbvffe8l1pvbewibj4ft62m [42102-168]
> 17:10:35,875 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Comment drop constraint FK_j94pith5sd971k29j6ysxuk7
> 17:10:35,875 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "COMMENT" not found; SQL statement:
> alter table Comment drop constraint FK_j94pith5sd971k29j6ysxuk7 [42102-168]
> 17:10:35,875 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Comment drop constraint FK_qh25b5js0rt4fqv9syhyjv781
> 17:10:35,876 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "COMMENT" not found; SQL statement:
> alter table Comment drop constraint FK_qh25b5js0rt4fqv9syhyjv781 [42102-168]
> 17:10:35,876 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Image drop constraint FK_62s883scl1tf1fl7357bbtxy9
> 17:10:35,876 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "IMAGE" not found; SQL statement:
> alter table Image drop constraint FK_62s883scl1tf1fl7357bbtxy9 [42102-168]
> 17:10:35,876 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Image_MetaTag drop constraint FK_qw6hpgbun1gnhr0nimrao8gxc
> 17:10:35,877 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "IMAGE_METATAG" not found; SQL statement:
> alter table Image_MetaTag drop constraint FK_qw6hpgbun1gnhr0nimrao8gxc [42102-168]
> 17:10:35,877 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Image_MetaTag drop constraint FK_rb6l6aoyv7bss6hto77wqnvfg
> 17:10:35,877 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "IMAGE_METATAG" not found; SQL statement:
> alter table Image_MetaTag drop constraint FK_rb6l6aoyv7bss6hto77wqnvfg [42102-168]
> 17:10:35,877 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Shelf drop constraint FK_3unm5rbreqkjurmy4hpfl89yr
> 17:10:35,878 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Table "SHELF" not found; SQL statement:
> alter table Shelf drop constraint FK_3unm5rbreqkjurmy4hpfl89yr [42102-168]
> 17:10:36,026 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000230: Schema export complete
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (RF-13209) RichTree JS onselectionchange() with a4jregion template
by Matej Novotny (JIRA)
Matej Novotny created RF-13209:
----------------------------------
Summary: RichTree JS onselectionchange() with a4jregion template
Key: RF-13209
URL: https://issues.jboss.org/browse/RF-13209
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.3.3, 4.2.3.Final, 4.3.4
Reporter: Matej Novotny
There is a bug when using onselectionchange() JS API in RichTree component using A4jRegion template (rest of the templates cause no problems).
The event will be called twice - in my case I tested it with simple alert("text") in Metamer using JBoss AS 7.1.
This bug appears in older version as well, so far I have tested it with 4.3.4, 4.3.3 and 4.2.3 Final builds all of which caused the same double event.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (RF-13208) Push: error "not well-formed" appears in browser console in Firefox
by Pavol Pitonak (JIRA)
Pavol Pitonak created RF-13208:
----------------------------------
Summary: Push: error "not well-formed" appears in browser console in Firefox
Key: RF-13208
URL: https://issues.jboss.org/browse/RF-13208
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.3.4
Environment: RichFaces 4.3.4.Final
Metamer 4.3.4.20130919-Final
Mojarra 2.1.19
EAP 6.1.1
OpenJDK Runtime Environment 1.7.0_40-mockbuild_2013_09_19_20_10-b00 @ Linux
Firefox 24.0 @ Linux x86_64
Reporter: Pavol Pitonak
Attachments: firefox_console.png
# deploy Metamer and open http://127.0.0.1:8080/metamer/faces/components/a4jPush/twoPush.xhtml
# open browser console
# click "Push 2!" button
result:
* browser console contains "not well-formed" JavaScript error (see screenshot)
* when you click on the error, you can see something like this:
{quote}
<"topic":"jmsSampleAddress2","data":"day: 23, month: 9, time: 11:01:12.829","number":0>
{quote}
* component seems to work fine despite this error
* I couldn't see this error in Chrome 29
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (RF-13208) Push: error "not well-formed" appears in browser console in Firefox
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13208?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak updated RF-13208:
-------------------------------
Attachment: firefox_console.png
> Push: error "not well-formed" appears in browser console in Firefox
> -------------------------------------------------------------------
>
> Key: RF-13208
> URL: https://issues.jboss.org/browse/RF-13208
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.4
> Environment: RichFaces 4.3.4.Final
> Metamer 4.3.4.20130919-Final
> Mojarra 2.1.19
> EAP 6.1.1
> OpenJDK Runtime Environment 1.7.0_40-mockbuild_2013_09_19_20_10-b00 @ Linux
> Firefox 24.0 @ Linux x86_64
> Reporter: Pavol Pitonak
> Attachments: firefox_console.png
>
>
> # deploy Metamer and open http://127.0.0.1:8080/metamer/faces/components/a4jPush/twoPush.xhtml
> # open browser console
> # click "Push 2!" button
> result:
> * browser console contains "not well-formed" JavaScript error (see screenshot)
> * when you click on the error, you can see something like this:
> {quote}
> <"topic":"jmsSampleAddress2","data":"day: 23, month: 9, time: 11:01:12.829","number":0>
> {quote}
> * component seems to work fine despite this error
> * I couldn't see this error in Chrome 29
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (RF-13082) Change the orderingList component to use the new orderingList widget
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13082?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13082:
-------------------------------
Description:
Attributes to be dropped in the RF5 implementation:
* disabledClass
* headerClass
* itemClass
* selectItemClass
* listHeight
* listWidth
* listMaxHeight
* listMaxWidth
It is felt that the *Class attributes are redundant. Custom component styling can be achieved with the combination of the CSS class specified by the _styleClass_ attribute, along with the relevant stateful CSS class (_disabled_, _header_, _ui-selectee_, ui-selected_).
Similarly the height/width CSS attributes are better set with CSS styles, rather than via facelet attributes.
Additionally, we should consider dropping the onlist* event handlers, as there is considerable overlap with their on* counterparts. For instance, are there really use cases that require differentiating between onmouveover and onlistmouseover?
> Change the orderingList component to use the new orderingList widget
> --------------------------------------------------------------------
>
> Key: RF-13082
> URL: https://issues.jboss.org/browse/RF-13082
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-selects
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Attributes to be dropped in the RF5 implementation:
> * disabledClass
> * headerClass
> * itemClass
> * selectItemClass
> * listHeight
> * listWidth
> * listMaxHeight
> * listMaxWidth
> It is felt that the *Class attributes are redundant. Custom component styling can be achieved with the combination of the CSS class specified by the _styleClass_ attribute, along with the relevant stateful CSS class (_disabled_, _header_, _ui-selectee_, ui-selected_).
> Similarly the height/width CSS attributes are better set with CSS styles, rather than via facelet attributes.
> Additionally, we should consider dropping the onlist* event handlers, as there is considerable overlap with their on* counterparts. For instance, are there really use cases that require differentiating between onmouveover and onlistmouseover?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (RF-13082) Change the orderingList component to use the new orderingList widget
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13082?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13082:
------------------------------------
[~lfryc] I'd appreciate any comments you have on the removal of the above attributes, in particular the onlist* attributes.
> Change the orderingList component to use the new orderingList widget
> --------------------------------------------------------------------
>
> Key: RF-13082
> URL: https://issues.jboss.org/browse/RF-13082
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-selects
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Attributes to be dropped in the RF5 implementation:
> * disabledClass
> * headerClass
> * itemClass
> * selectItemClass
> * listHeight
> * listWidth
> * listMaxHeight
> * listMaxWidth
> It is felt that the *Class attributes are redundant. Custom component styling can be achieved with the combination of the CSS class specified by the _styleClass_ attribute, along with the relevant stateful CSS class (_disabled_, _header_, _ui-selectee_, ui-selected_).
> Similarly the height/width CSS attributes are better set with CSS styles, rather than via facelet attributes.
> Additionally, we should consider dropping the onlist* event handlers, as there is considerable overlap with their on* counterparts. For instance, are there really use cases that require differentiating between onmouveover and onlistmouseover?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (RF-13206) Failure to reset ClassLoader when AWT Initialization errors
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13206?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13206:
-------------------------------
Description:
In org.richfaces.application.InitializationListener.AWTInitializer, the initalize() method can fail to reset the context ClassLoader despite the finally block that should do that (from line 195):
{code:title=org.richfaces.application.InitializationListener.AWTInitializer#195}
} finally {
if (testStream != null) {
try {
testStream.close();
} catch (IOException e) {
LOGGER.error(e.getMessage(), e);
}
}
thread.setContextClassLoader(initialTCCL);
}
{code}
In my OSGi environment, the testStream.close() invocation throws the NoClassDefFoundError pasted below. This circumvents the subsequent intention to restore the context ClassLoader. In effect, if AWT initialization fails the context ClassLoader is left in a bad state that prevents future ServiceTracker processing and hoses up the Faces initialization.
{code}
java.lang.NoClassDefFoundError: javax/imageio/stream/ImageInputStream
at org.richfaces.application.InitializationListener$AWTInitializer.initialize(InitializationListener.java:198)
at org.richfaces.application.InitializationListener.initializeAWT(InitializationListener.java:94)
at org.richfaces.application.InitializationListener.onStart(InitializationListener.java:78)
at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:152)
at javax.faces.event.SystemEvent.processListener(SystemEvent.java:43)
at org.apache.myfaces.application.ApplicationImpl._traverseListenerList(ApplicationImpl.java:2471)
at org.apache.myfaces.application.ApplicationImpl.access$000(ApplicationImpl.java:120)
at org.apache.myfaces.application.ApplicationImpl$SystemListenerEntry.publish(ApplicationImpl.java:2662)
at org.apache.myfaces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:601)
at org.apache.myfaces.webapp.AbstractFacesInitializer._dispatchApplicationEvent(AbstractFacesInitializer.java:286)
at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:154)
at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119)
{code}
was:
In org.richfaces.application.InitializationListener.AWTInitializer, the initalize() method can fail to reset the context ClassLoader despite the finally block that should do that (from line 195):
} finally {
if (testStream != null) {
try {
testStream.close();
} catch (IOException e) {
LOGGER.error(e.getMessage(), e);
}
}
thread.setContextClassLoader(initialTCCL);
}
In my OSGi environment, the testStream.close() invocation throws the NoClassDefFoundError pasted below. This circumvents the subsequent intention to restore the context ClassLoader. In effect, if AWT initialization fails the context ClassLoader is left in a bad state that prevents future ServiceTracker processing and hoses up the Faces initialization.
java.lang.NoClassDefFoundError: javax/imageio/stream/ImageInputStream
at org.richfaces.application.InitializationListener$AWTInitializer.initialize(InitializationListener.java:198)
at org.richfaces.application.InitializationListener.initializeAWT(InitializationListener.java:94)
at org.richfaces.application.InitializationListener.onStart(InitializationListener.java:78)
at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:152)
at javax.faces.event.SystemEvent.processListener(SystemEvent.java:43)
at org.apache.myfaces.application.ApplicationImpl._traverseListenerList(ApplicationImpl.java:2471)
at org.apache.myfaces.application.ApplicationImpl.access$000(ApplicationImpl.java:120)
at org.apache.myfaces.application.ApplicationImpl$SystemListenerEntry.publish(ApplicationImpl.java:2662)
at org.apache.myfaces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:601)
at org.apache.myfaces.webapp.AbstractFacesInitializer._dispatchApplicationEvent(AbstractFacesInitializer.java:286)
at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:154)
at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119)
> Failure to reset ClassLoader when AWT Initialization errors
> -----------------------------------------------------------
>
> Key: RF-13206
> URL: https://issues.jboss.org/browse/RF-13206
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 4.3.3
> Environment: ServiceMix
> Reporter: Donald Oakes
> Priority: Minor
>
> In org.richfaces.application.InitializationListener.AWTInitializer, the initalize() method can fail to reset the context ClassLoader despite the finally block that should do that (from line 195):
> {code:title=org.richfaces.application.InitializationListener.AWTInitializer#195}
> } finally {
> if (testStream != null) {
> try {
> testStream.close();
> } catch (IOException e) {
> LOGGER.error(e.getMessage(), e);
> }
> }
> thread.setContextClassLoader(initialTCCL);
> }
> {code}
> In my OSGi environment, the testStream.close() invocation throws the NoClassDefFoundError pasted below. This circumvents the subsequent intention to restore the context ClassLoader. In effect, if AWT initialization fails the context ClassLoader is left in a bad state that prevents future ServiceTracker processing and hoses up the Faces initialization.
> {code}
> java.lang.NoClassDefFoundError: javax/imageio/stream/ImageInputStream
> at org.richfaces.application.InitializationListener$AWTInitializer.initialize(InitializationListener.java:198)
> at org.richfaces.application.InitializationListener.initializeAWT(InitializationListener.java:94)
> at org.richfaces.application.InitializationListener.onStart(InitializationListener.java:78)
> at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:152)
> at javax.faces.event.SystemEvent.processListener(SystemEvent.java:43)
> at org.apache.myfaces.application.ApplicationImpl._traverseListenerList(ApplicationImpl.java:2471)
> at org.apache.myfaces.application.ApplicationImpl.access$000(ApplicationImpl.java:120)
> at org.apache.myfaces.application.ApplicationImpl$SystemListenerEntry.publish(ApplicationImpl.java:2662)
> at org.apache.myfaces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:601)
> at org.apache.myfaces.webapp.AbstractFacesInitializer._dispatchApplicationEvent(AbstractFacesInitializer.java:286)
> at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:154)
> at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months