[JBoss JIRA] (RF-13707) Photoalbum: incorrect account details shown after creating a new one
by Juraj Húska (JIRA)
Juraj Húska created RF-13707:
--------------------------------
Summary: Photoalbum: incorrect account details shown after creating a new one
Key: RF-13707
URL: https://issues.jboss.org/browse/RF-13707
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: examples
Affects Versions: 4.3.8
Reporter: Juraj Húska
When user create a new account in Photoalbum application there are shown account details, which are incorrect:
* missing login, first name, surname
* wrong sex value (there is always female)
* missing Birthday and email
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated
by Marcel Kolsteren (JIRA)
[ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.s... ]
Marcel Kolsteren updated RF-13706:
----------------------------------
Component/s: core
> dequeued Ajax request not processed correctly if its source element has been updated
> ------------------------------------------------------------------------------------
>
> Key: RF-13706
> URL: https://issues.jboss.org/browse/RF-13706
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core, core
> Affects Versions: 4.3.7
> Reporter: Marcel Kolsteren
> Attachments: queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip
>
>
> I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page.
> The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen.
> To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked:
> {noformat}
> <!DOCTYPE html>
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:a4j="http://richfaces.org/a4j">
> <h:head/>
> <h:body>
> <form action="http://www.meandi.nl"/>
> <h:form>
> <a4j:commandLink action="#{richBean.waitThreeSeconds}" value="Click Me" render="@this"/>
> </h:form>
> </h:body>
> </html>
> {noformat}
> The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7.
> The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated
by Marcel Kolsteren (JIRA)
[ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.s... ]
Marcel Kolsteren updated RF-13706:
----------------------------------
Component/s: (was: component-a4j-core)
> dequeued Ajax request not processed correctly if its source element has been updated
> ------------------------------------------------------------------------------------
>
> Key: RF-13706
> URL: https://issues.jboss.org/browse/RF-13706
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 4.3.7
> Reporter: Marcel Kolsteren
> Attachments: queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip
>
>
> I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page.
> The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen.
> To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked:
> {noformat}
> <!DOCTYPE html>
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:a4j="http://richfaces.org/a4j">
> <h:head/>
> <h:body>
> <form action="http://www.meandi.nl"/>
> <h:form>
> <a4j:commandLink action="#{richBean.waitThreeSeconds}" value="Click Me" render="@this"/>
> </h:form>
> </h:body>
> </html>
> {noformat}
> The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7.
> The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated
by Marcel Kolsteren (JIRA)
[ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.s... ]
Marcel Kolsteren updated RF-13706:
----------------------------------
Attachment: richfaces-core-4.3.8-SNAPSHOT.patch.zip
> dequeued Ajax request not processed correctly if its source element has been updated
> ------------------------------------------------------------------------------------
>
> Key: RF-13706
> URL: https://issues.jboss.org/browse/RF-13706
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.7
> Reporter: Marcel Kolsteren
> Attachments: queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip
>
>
> I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page.
> The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen.
> To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked:
> {noformat}
> <!DOCTYPE html>
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:a4j="http://richfaces.org/a4j">
> <h:head/>
> <h:body>
> <form action="http://www.meandi.nl"/>
> <h:form>
> <a4j:commandLink action="#{richBean.waitThreeSeconds}" value="Click Me" render="@this"/>
> </h:form>
> </h:body>
> </html>
> {noformat}
> The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7.
> The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated
by Marcel Kolsteren (JIRA)
[ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.s... ]
Marcel Kolsteren edited comment on RF-13706 at 6/30/14 4:04 AM:
----------------------------------------------------------------
Added attachments
was (Author: marcelkolsteren):
Maven project with sample application
> dequeued Ajax request not processed correctly if its source element has been updated
> ------------------------------------------------------------------------------------
>
> Key: RF-13706
> URL: https://issues.jboss.org/browse/RF-13706
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.7
> Reporter: Marcel Kolsteren
> Attachments: queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip
>
>
> I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page.
> The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen.
> To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked:
> {noformat}
> <!DOCTYPE html>
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:a4j="http://richfaces.org/a4j">
> <h:head/>
> <h:body>
> <form action="http://www.meandi.nl"/>
> <h:form>
> <a4j:commandLink action="#{richBean.waitThreeSeconds}" value="Click Me" render="@this"/>
> </h:form>
> </h:body>
> </html>
> {noformat}
> The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7.
> The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated
by Marcel Kolsteren (JIRA)
[ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.s... ]
Marcel Kolsteren updated RF-13706:
----------------------------------
Attachment: queuetest.zip
Maven project with sample application
> dequeued Ajax request not processed correctly if its source element has been updated
> ------------------------------------------------------------------------------------
>
> Key: RF-13706
> URL: https://issues.jboss.org/browse/RF-13706
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.7
> Reporter: Marcel Kolsteren
> Attachments: queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip
>
>
> I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page.
> The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen.
> To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked:
> {noformat}
> <!DOCTYPE html>
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:a4j="http://richfaces.org/a4j">
> <h:head/>
> <h:body>
> <form action="http://www.meandi.nl"/>
> <h:form>
> <a4j:commandLink action="#{richBean.waitThreeSeconds}" value="Click Me" render="@this"/>
> </h:form>
> </h:body>
> </html>
> {noformat}
> The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7.
> The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated
by Marcel Kolsteren (JIRA)
Marcel Kolsteren created RF-13706:
-------------------------------------
Summary: dequeued Ajax request not processed correctly if its source element has been updated
Key: RF-13706
URL: https://issues.jboss.org/browse/RF-13706
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.3.7
Reporter: Marcel Kolsteren
I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page.
The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen.
To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked:
{noformat}
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:a4j="http://richfaces.org/a4j">
<h:head/>
<h:body>
<form action="http://www.meandi.nl"/>
<h:form>
<a4j:commandLink action="#{richBean.waitThreeSeconds}" value="Click Me" render="@this"/>
</h:form>
</h:body>
</html>
{noformat}
The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7.
The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13692) Photoalbum can not be deployed to WildFly 8.0.x or 8.1.x due to Weld exception
by Jozef Hartinger (JIRA)
[ https://issues.jboss.org/browse/RF-13692?page=com.atlassian.jira.plugin.s... ]
Jozef Hartinger commented on RF-13692:
--------------------------------------
CDI 1.1 requires strict checking of when BeanManager methods are invoked. The non-portable mode is the correct solution in this case. The rules got more lenient in CDI 1.2 so the non-portable mode will not be required again with Weld 2.2.
As for the other issue the log message describes the problem clearly. The interceptors specification requires that:
{quote}
Lifecycle callback interceptor methods defined on a target class have the following signature:
void <METHOD>()
{quote}
org.richfaces.photoalbum.manager.Authenticator violates this requirement.
In previos versions of Weld this was not checked properly thus the application works on EAP.
> Photoalbum can not be deployed to WildFly 8.0.x or 8.1.x due to Weld exception
> ------------------------------------------------------------------------------
>
> Key: RF-13692
> URL: https://issues.jboss.org/browse/RF-13692
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.5.0.Alpha3
> Reporter: Juraj Húska
>
> There is an error during deployment of Photoalbum example on WildFly 8.1.0.Final or 8.0.0.Final
> {code}
> 09:28:51,675 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55]
> Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getBeans() is not available during application initialization
> at org.jboss.weld.bean.builtin.BeanManagerProxy.checkContainerValidated(BeanManagerProxy.java:159)
> at org.jboss.weld.bean.builtin.BeanManagerProxy.getBeans(BeanManagerProxy.java:91)
> at org.jboss.solder.core.CoreExtension.failIfWeldExtensionsDetected(CoreExtension.java:215)
> at org.jboss.solder.core.CoreExtension.afterBeanDiscovery(CoreExtension.java:208)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:93)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:266)
> at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:125)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:232)
> at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:169)
> at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:128)
> at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:102)
> at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:63)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:35)
> at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:55)
> at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:372)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:79)
> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:92)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:37)
> at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:55)
> at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:372)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:79)
> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:92)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> ... 3 more
> {code}
> and
> {code}
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.deployment.unit."richfaces-photoalbum.war".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService, JBAS014799: ... and 23 more ]
> service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService, JBAS014799: ... and 22 more ]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.VIEW."org.richfaces.photoalbum.model.actions.IAlbumAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.VIEW."org.richfaces.photoalbum.model.actions.IEventAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInstantiator]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.VIEW."org.richfaces.photoalbum.model.actions.IImageAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInstantiator]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.VIEW."org.richfaces.photoalbum.search.ISearchAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.VIEW."org.richfaces.photoalbum.model.actions.IShelfAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInstantiator]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.VIEW."org.richfaces.photoalbum.model.actions.IUserAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInstantiator]
> service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START]
> service jboss.deployment.unit."richfaces-photoalbum.war".ee.ComponentRegistry (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> service jboss.deployment.unit."richfaces-photoalbum.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START, service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START, JBAS014799: ... and 16 more ]
> service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformation (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START, JBAS014799: ... and 4 more ]
> service jboss.persistenceunit."richfaces-photoalbum.war#photoAlbum" (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START, service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService, JBAS014799: ... and 13 more ]
> service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService]
> service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum]
> service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.codec (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService]
> {code}
> Note that it *works* on EAP 6.2.3.GA and EAP 6.3.0.ER8
> Both WildFly containers use Weld 2.1.x, so it is not a problem with Weld 2.2.x integration.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months