[JBoss JIRA] (RF-13629) popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13629?page=com.atlassian.jira.plugin.s... ]
Juraj Húska closed RF-13629.
----------------------------
Verified. Closing.
> popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
> -------------------------------------------------------------------------------------------
>
> Key: RF-13629
> URL: https://issues.jboss.org/browse/RF-13629
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.7
> Environment: Firefox
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Critical
> Labels: regression
> Fix For: 4.3.7
>
> Attachments: popupPanelGood.png, popupPanelResizedAndBroken_2.png, popupPanelWrong.png, popupResizedAndBroken_1.png, sample.zip
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> -In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.-
> -When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.-
> Note that the above was original issue, which as you can see in the comments we identified as a correct change of behavior. In the comments below you can also find other issues which emerged when fixing RF-13616.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13629) popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13629?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13629:
-----------------------------
Description:
-In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.-
-When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.-
Note that the above was original issue, which as you can see in the comments we identified as a correct change of behavior. In the comments below you can also find other issues which emerged when fixing
was:
-In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.-
-When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.-
> popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
> -------------------------------------------------------------------------------------------
>
> Key: RF-13629
> URL: https://issues.jboss.org/browse/RF-13629
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.7
> Environment: Firefox
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Critical
> Labels: regression
> Fix For: 4.3.7
>
> Attachments: popupPanelGood.png, popupPanelResizedAndBroken_2.png, popupPanelWrong.png, popupResizedAndBroken_1.png, sample.zip
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> -In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.-
> -When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.-
> Note that the above was original issue, which as you can see in the comments we identified as a correct change of behavior. In the comments below you can also find other issues which emerged when fixing
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13629) popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13629?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13629:
-----------------------------
Description:
-In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.-
-When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.-
Note that the above was original issue, which as you can see in the comments we identified as a correct change of behavior. In the comments below you can also find other issues which emerged when fixing RF-13616.
was:
-In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.-
-When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.-
Note that the above was original issue, which as you can see in the comments we identified as a correct change of behavior. In the comments below you can also find other issues which emerged when fixing
> popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
> -------------------------------------------------------------------------------------------
>
> Key: RF-13629
> URL: https://issues.jboss.org/browse/RF-13629
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.7
> Environment: Firefox
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Critical
> Labels: regression
> Fix For: 4.3.7
>
> Attachments: popupPanelGood.png, popupPanelResizedAndBroken_2.png, popupPanelWrong.png, popupResizedAndBroken_1.png, sample.zip
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> -In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.-
> -When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.-
> Note that the above was original issue, which as you can see in the comments we identified as a correct change of behavior. In the comments below you can also find other issues which emerged when fixing RF-13616.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13629) popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13629?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13629:
-----------------------------
Description:
-In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.-
-When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.-
was:
In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.
When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.
> popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
> -------------------------------------------------------------------------------------------
>
> Key: RF-13629
> URL: https://issues.jboss.org/browse/RF-13629
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.7
> Environment: Firefox
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Critical
> Labels: regression
> Fix For: 4.3.7
>
> Attachments: popupPanelGood.png, popupPanelResizedAndBroken_2.png, popupPanelWrong.png, popupResizedAndBroken_1.png, sample.zip
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> -In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.-
> -When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.-
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13629) popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13629?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13629:
-----------------------------
Steps to Reproduce: (was: # deploy Metamer and load http://localhost:8080/metamer/faces/components/richPopupPanel/simple.xhtml
# set "Popup's paragraph width:" input to {{100}}
# set {{resizeable}} to {{false}}
# set {{autosized}} to {{true}}
# set {{width}} to ""
# set {{height}} to ""
# click on the Call popup button
# see that popup panel adjusted only its height, width stays the same)
> popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
> -------------------------------------------------------------------------------------------
>
> Key: RF-13629
> URL: https://issues.jboss.org/browse/RF-13629
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.7
> Environment: Firefox
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Critical
> Labels: regression
> Fix For: 4.3.7
>
> Attachments: popupPanelGood.png, popupPanelResizedAndBroken_2.png, popupPanelWrong.png, popupResizedAndBroken_1.png, sample.zip
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.
> When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13629) popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13629?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13629:
-----------------------------
Labels: regression (was: needs-qe regression)
> popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
> -------------------------------------------------------------------------------------------
>
> Key: RF-13629
> URL: https://issues.jboss.org/browse/RF-13629
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.7
> Environment: Firefox
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Critical
> Labels: regression
> Fix For: 4.3.7
>
> Attachments: popupPanelGood.png, popupPanelResizedAndBroken_2.png, popupPanelWrong.png, popupResizedAndBroken_1.png, sample.zip
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.
> When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13640) autocomplete cant select by mouse
by liumin hu (JIRA)
liumin hu created RF-13640:
------------------------------
Summary: autocomplete cant select by mouse
Key: RF-13640
URL: https://issues.jboss.org/browse/RF-13640
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.3.6
Reporter: liumin hu
the suggestion list of autocomplete can not be selected by mouse, always the first one selected.
there is not this bug before 4.3.6.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13637) Refresh the dist zip for RF 4.5
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13637?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-13637:
------------------------------------
[~bleathem], why did you rename jar artifacts in distribution zip?
> Refresh the dist zip for RF 4.5
> -------------------------------
>
> Key: RF-13637
> URL: https://issues.jboss.org/browse/RF-13637
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 2 days
> Time Spent: 1 day
> Remaining Estimate: 1 day
>
> The distribution zip for RichFaces 4.5 needs to be refreshed to account for the module and repository changes.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13611) RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final
by Jozef Hartinger (JIRA)
[ https://issues.jboss.org/browse/RF-13611?page=com.atlassian.jira.plugin.s... ]
Jozef Hartinger commented on RF-13611:
--------------------------------------
You can use current WildFly snapshot with Weld 2.2 patch applied. The build is available here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Weld/view/Weld%202%...
Alternatively, a patch that can be applied on top of WildFly 8.1.0.CR1 is available here: https://sourceforge.net/projects/jboss/files/Weld/2.2.1.Final/
> RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final
> ---------------------------------------------------------
>
> Key: RF-13611
> URL: https://issues.jboss.org/browse/RF-13611
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 5.0.0.Alpha3
> Reporter: Juergen Zimmermann
> Assignee: Brian Leathem
> Labels: waiting_on_user
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> I'm using WildFly 8.0.0.CR1 and Weld 2.2.0.Final (via the WildFly patch mechanism). However, I'm getting the stacktrace below. When I patch WildFly 8.0.0.CR1 with the predecessor version Weld 2.2.0.CR2, then the issue is gone.
> {code}
> ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.deployment.unit."shop.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."shop.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:1142) [rt.jar:1.8.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
> Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> org.jboss.weld.exceptions.DefinitionException: WELD-000412: ObserverMethod.getReception() returned null for org.richfaces.push.cdi.PushCDIExtension$PushObserverMethod@31e23242
> at org.jboss.weld.util.Observers.validateObserverMethod(Observers.java:118)
> at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addObserverMethod(AfterBeanDiscoveryImpl.java:158)
> at org.richfaces.push.cdi.PushCDIExtension.afterBeanDiscovery(PushCDIExtension.java:99)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:90)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:271)
> at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:258)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:237)
> at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:174)
> at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:133)
> at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:107)
> at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42)
> at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59)
> at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:744)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44)
> at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59)
> at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
> 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}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13611) RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final
by Juergen Zimmermann (JIRA)
[ https://issues.jboss.org/browse/RF-13611?page=com.atlassian.jira.plugin.s... ]
Juergen Zimmermann commented on RF-13611:
-----------------------------------------
Weld 2.2 was included in the WildFly snapshots for some time. About a week ago Weld was downgraded from 2.2 back to 2.1. I don't know why. Maybe there was a TCK issue since Weld 2.2 is implementing the new spec CDI 1.2MR.
> RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final
> ---------------------------------------------------------
>
> Key: RF-13611
> URL: https://issues.jboss.org/browse/RF-13611
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 5.0.0.Alpha3
> Reporter: Juergen Zimmermann
> Assignee: Brian Leathem
> Labels: waiting_on_user
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> I'm using WildFly 8.0.0.CR1 and Weld 2.2.0.Final (via the WildFly patch mechanism). However, I'm getting the stacktrace below. When I patch WildFly 8.0.0.CR1 with the predecessor version Weld 2.2.0.CR2, then the issue is gone.
> {code}
> ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.deployment.unit."shop.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."shop.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:1142) [rt.jar:1.8.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
> Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> org.jboss.weld.exceptions.DefinitionException: WELD-000412: ObserverMethod.getReception() returned null for org.richfaces.push.cdi.PushCDIExtension$PushObserverMethod@31e23242
> at org.jboss.weld.util.Observers.validateObserverMethod(Observers.java:118)
> at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addObserverMethod(AfterBeanDiscoveryImpl.java:158)
> at org.richfaces.push.cdi.PushCDIExtension.afterBeanDiscovery(PushCDIExtension.java:99)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:90)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:271)
> at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:258)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:237)
> at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:174)
> at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:133)
> at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:107)
> at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42)
> at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59)
> at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:744)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44)
> at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59)
> at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
> 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}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months