[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-12802 at 10/15/13 11:17 AM:
-------------------------------------------------------------
Couple of additional refactorings, we have discussed offline:
* -Create interface for method {{advance()}}-
{code}
AdvancedInteractions<T> {
T advanced();
}
{code}
-We can document the method more easily - the fragment will implement that interface-
* -provide a way to set JS strategy in {{arquillian.xml}} - e.g.
{code:xml}
<extension name="richfacesPageFragments"><property name="controlStrategy">interactive</property>
{code}
-See ARQGRA-325 comments as well.-
* -waiting API - put {{withTimeout}} right to the wrapper, so the public API methods do not have call for the actual timeout value-
* -rename the parameter for setting of the timeout from _timeout_ to something which shows in what time unit it is - e.g. miliseconds-
* -move fields which hold timeout value to the {{AdvancedInteraction}} classes-
* -use miliseconds in waiting API instead of seconds as we found them to be more used accros tests-
* -review exception throwing - throw them where it is necessary, make the method no operation where it is not necessary- did not spend much time with this one, imho we are still in Alpha and we will find out by using the fragments which exceptions are in place and which one do not. Currently I agree with all exception which are thrown.
* -make an attribute from [this|https://github.com/richfaces/richfaces-qa/blob/master/page-fragments...
* make a pull request with moved repository
* write Javadoc
I will cross already done parts.
was (Author: jhuska):
Couple of additional refactorings, we have discussed offline:
* -Create interface for method {{advance()}}-
{code}
AdvancedInteractions<T> {
T advanced();
}
{code}
-We can document the method more easily - the fragment will implement that interface-
* provide a way to set JS strategy in {{arquillian.xml}} - e.g.
{code:xml}
<extension name="richfacesPageFragments"><property name="controlStrategy">interactive</property>
{code}
See ARQGRA-325 comments as well.
* -waiting API - put {{withTimeout}} right to the wrapper, so the public API methods do not have call for the actual timeout value-
* -rename the parameter for setting of the timeout from _timeout_ to something which shows in what time unit it is - e.g. miliseconds-
* -move fields which hold timeout value to the {{AdvancedInteraction}} classes-
* -use miliseconds in waiting API instead of seconds as we found them to be more used accros tests-
* -review exception throwing - throw them where it is necessary, make the method no operation where it is not necessary- did not spend much time with this one, imho we are still in Alpha and we will find out by using the fragments which exceptions are in place and which one do not. Currently I agree with all exception which are thrown.
* -make an attribute from [this|https://github.com/richfaces/richfaces-qa/blob/master/page-fragments...
* make a pull request with moved repository
* write Javadoc
I will cross already done parts.
> Move page fragments from repository qa to richfaces5
> ----------------------------------------------------
>
> Key: RF-12802
> URL: https://issues.jboss.org/browse/RF-12802
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.Alpha1
> Reporter: Pavol Pitonak
> Assignee: Juraj Húska
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
> We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations.
--
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
12 years, 5 months
[JBoss JIRA] (RF-13264) rich:menuGroup drop down menu hidden in richAccordion
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13264?page=com.atlassian.jira.plugin.s... ]
Matej Novotny commented on RF-13264:
------------------------------------
The problem is very similar to this one.
> rich:menuGroup drop down menu hidden in richAccordion
> -----------------------------------------------------
>
> Key: RF-13264
> URL: https://issues.jboss.org/browse/RF-13264
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-menu
> Affects Versions: 4.3.4
> Environment: RichFaces 4.3.4.Final
> Metamer 4.3.5-SNAPSHOT
> JBoss Application Server: Weld Integration 7.1.1.Final
> JBoss AS 7.1.1.Final
> Java(TM) SE Runtime Environment 1.7.0_25-b15 @ Linux
> Firefox 24.0 @ Linux x86_64
> Reporter: Matej Novotny
>
> Dropdown menu inside richAccordion template is clipped by accordion instead of being "on top".
> There is a very similar RF issue [here|https://issues.jboss.org/browse/RF-12592], which leads to [this|https://issues.jboss.org/browse/RF-11842] issue both of which are unresolved.
> As for conformation of this bug (and later solution) Metamer test can be run with the following command: _mvn clean verify -Pjbossas-remote-7-1 -Dtest=TestMenuGroup#testDirection -Dtemplates=richAccordion_
> Meanwhile richAccordion template will be excluded from tests.
--
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
12 years, 5 months
[JBoss JIRA] (RF-13264) rich:menuGroup drop down menu hidden in richAccordion
by Matej Novotny (JIRA)
Matej Novotny created RF-13264:
----------------------------------
Summary: rich:menuGroup drop down menu hidden in richAccordion
Key: RF-13264
URL: https://issues.jboss.org/browse/RF-13264
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-menu
Affects Versions: 4.3.4
Environment: RichFaces 4.3.4.Final
Metamer 4.3.5-SNAPSHOT
JBoss Application Server: Weld Integration 7.1.1.Final
JBoss AS 7.1.1.Final
Java(TM) SE Runtime Environment 1.7.0_25-b15 @ Linux
Firefox 24.0 @ Linux x86_64
Reporter: Matej Novotny
Dropdown menu inside richAccordion template is clipped by accordion instead of being "on top".
There is a very similar RF issue [here|https://issues.jboss.org/browse/RF-12592], which leads to [this|https://issues.jboss.org/browse/RF-11842] issue both of which are unresolved.
As for conformation of this bug (and later solution) Metamer test can be run with the following command: _mvn clean verify -Pjbossas-remote-7-1 -Dtest=TestMenuGroup#testDirection -Dtemplates=richAccordion_
Meanwhile richAccordion template will be excluded from tests.
--
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
12 years, 5 months
[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-12802 at 10/15/13 9:37 AM:
------------------------------------------------------------
Couple of additional refactorings, we have discussed offline:
* -Create interface for method {{advance()}}-
{code}
AdvancedInteractions<T> {
T advanced();
}
{code}
-We can document the method more easily - the fragment will implement that interface-
* provide a way to set JS strategy in {{arquillian.xml}} - e.g.
{code:xml}
<extension name="richfacesPageFragments"><property name="controlStrategy">interactive</property>
{code}
See ARQGRA-325 comments as well.
* -waiting API - put {{withTimeout}} right to the wrapper, so the public API methods do not have call for the actual timeout value-
* -rename the parameter for setting of the timeout from _timeout_ to something which shows in what time unit it is - e.g. miliseconds-
* -move fields which hold timeout value to the {{AdvancedInteraction}} classes-
* -use miliseconds in waiting API instead of seconds as we found them to be more used accros tests-
* -review exception throwing - throw them where it is necessary, make the method no operation where it is not necessary- did not spend much time with this one, imho we are still in Alpha and we will find out by using the fragments which exceptions are in place and which one do not. Currently I agree with all exception which are thrown.
* -make an attribute from [this|https://github.com/richfaces/richfaces-qa/blob/master/page-fragments...
* make a pull request with moved repository
* write Javadoc
I will cross already done parts.
was (Author: jhuska):
Couple of additional refactorings, we have discussed offline:
* -Create interface for method {{advance()}}-
{code}
AdvancedInteractions<T> {
T advanced();
}
{code}
-We can document the method more easily - the fragment will implement that interface-
* provide a way to set JS strategy in {{arquillian.xml}} - e.g.
{code:xml}
<extension name="richfacesPageFragments"><property name="controlStrategy">interactive</property>
{code}
See ARQGRA-325 comments as well.
* -waiting API - put {{withTimeout}} right to the wrapper, so the public API methods do not have call for the actual timeout value-
* -rename the parameter for setting of the timeout from _timeout_ to something which shows in what time unit it is - e.g. miliseconds-
* -move fields which hold timeout value to the {{AdvancedInteraction}} classes-
* -use miliseconds in waiting API instead of seconds as we found them to be more used accros tests-
* -review exception throwing - throw them where it is necessary, make the method no operation where it is not necessary- did not spend much time with this one, imho we are still in Alpha and we will find out by using the fragments which exceptions are in place and which one do not. Currently I agree with all exception which are thrown.
* make an attribute from [this|https://github.com/richfaces/richfaces-qa/blob/master/page-fragments...].
* make a pull request with moved repository
* write Javadoc
I will cross already done parts.
> Move page fragments from repository qa to richfaces5
> ----------------------------------------------------
>
> Key: RF-12802
> URL: https://issues.jboss.org/browse/RF-12802
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.Alpha1
> Reporter: Pavol Pitonak
> Assignee: Juraj Húska
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
> We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations.
--
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
12 years, 5 months
[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-12802 at 10/15/13 9:09 AM:
------------------------------------------------------------
Couple of additional refactorings, we have discussed offline:
* -Create interface for method {{advance()}}-
{code}
AdvancedInteractions<T> {
T advanced();
}
{code}
-We can document the method more easily - the fragment will implement that interface-
* provide a way to set JS strategy in {{arquillian.xml}} - e.g.
{code:xml}
<extension name="richfacesPageFragments"><property name="controlStrategy">interactive</property>
{code}
See ARQGRA-325 comments as well.
* -waiting API - put {{withTimeout}} right to the wrapper, so the public API methods do not have call for the actual timeout value-
* -rename the parameter for setting of the timeout from _timeout_ to something which shows in what time unit it is - e.g. miliseconds-
* -move fields which hold timeout value to the {{AdvancedInteraction}} classes-
* -use miliseconds in waiting API instead of seconds as we found them to be more used accros tests-
* -review exception throwing - throw them where it is necessary, make the method no operation where it is not necessary- did not spend much time with this one, imho we are still in Alpha and we will find out by using the fragments which exceptions are in place and which one do not. Currently I agree with all exception which are thrown.
* make an attribute from [this|https://github.com/richfaces/richfaces-qa/blob/master/page-fragments...].
* make a pull request with moved repository
* write Javadoc
I will cross already done parts.
was (Author: jhuska):
Couple of additional refactorings, we have discussed offline:
* -Create interface for method {{advance()}}-
{code}
AdvancedInteractions<T> {
T advanced();
}
{code}
-We can document the method more easily - the fragment will implement that interface-
* provide a way to set JS strategy in {{arquillian.xml}} - e.g.
{code:xml}
<extension name="richfacesPageFragments"><property name="controlStrategy">interactive</property>
{code}
See ARQGRA-325 comments as well.
* -waiting API - put {{withTimeout}} right to the wrapper, so the public API methods do not have call for the actual timeout value-
* -rename the parameter for setting of the timeout from _timeout_ to something which shows in what time unit it is - e.g. miliseconds-
* -move fields which hold timeout value to the {{AdvancedInteraction}} classes-
* -use miliseconds in waiting API instead of seconds as we found them to be more used accros tests-
* review exception throwing - throw them where it is necessary, make the method no operation where it is not necessary
* make an attribute from [this|https://github.com/richfaces/richfaces-qa/blob/master/page-fragments...].
* make a pull request with moved repository
* write Javadoc
I will cross already done parts.
> Move page fragments from repository qa to richfaces5
> ----------------------------------------------------
>
> Key: RF-12802
> URL: https://issues.jboss.org/browse/RF-12802
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.Alpha1
> Reporter: Pavol Pitonak
> Assignee: Juraj Húska
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
> We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations.
--
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
12 years, 5 months
[JBoss JIRA] (RF-13263) RichFocus does not set focus properly in some templates
by Matej Novotny (JIRA)
Matej Novotny created RF-13263:
----------------------------------
Summary: RichFocus does not set focus properly in some templates
Key: RF-13263
URL: https://issues.jboss.org/browse/RF-13263
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.3.4
Environment: RichFaces 4.3.4.Final
Metamer 4.3.5-SNAPSHOT
JBoss Application Server: Weld Integration 7.1.1.Final
JBoss AS 7.1.1.Final
Java(TM) SE Runtime Environment 1.7.0_25-b15 @ Linux
Firefox 24.0 @ Linux x86_64
Reporter: Matej Novotny
Rich Focus Component does not set focus properly after validating inputs.
Does not work with validationAware attribute false as well (which should change focused component after validation).
This only happens in the following templates - richAccordion, richCollapsiblePanel, richTabPanel.
Here is the exception thrown after following "Steps to reproduce":
{code}
14:06:21,629 SEVERE [org.richfaces.log.Context] (http--127.0.0.1-8080-1) containerItem3: java.lang.IllegalArgumentException: containerItem3
at javax.faces.component.UIComponentBase.findComponent(UIComponentBase.java:606) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at org.richfaces.renderkit.util.RendererUtils.findComponentFor(RendererUtils.java:759) [richfaces-components-ui-4.3.4.Final.jar:4.3.4.Final]
at org.richfaces.renderkit.focus.AbstractFocusRenderStrategy.getFocusedComponent(AbstractFocusRenderStrategy.java:91) [richfaces-components-ui-4.3.4.Final.jar:4.3.4.Final]
at org.richfaces.renderkit.focus.AbstractFocusRenderStrategy.getSubmittedFocus(AbstractFocusRenderStrategy.java:79) [richfaces-components-ui-4.3.4.Final.jar:4.3.4.Final]
at org.richfaces.renderkit.focus.AbstractFocusRenderStrategy.getFocusCandidates(AbstractFocusRenderStrategy.java:40) [richfaces-components-ui-4.3.4.Final.jar:4.3.4.Final]
at org.richfaces.renderkit.focus.AbstractFocusRenderStrategy.getFocusCandidatesAsString(AbstractFocusRenderStrategy.java:24) [richfaces-components-ui-4.3.4.Final.jar:4.3.4.Final]
at org.richfaces.renderkit.focus.FormFocusRenderStrategy.getFocusCandidatesAsString(FormFocusRenderStrategy.java:65) [richfaces-components-ui-4.3.4.Final.jar:4.3.4.Final]
at org.richfaces.renderkit.FocusRendererBase.getFocusCandidatesAsString(FocusRendererBase.java:38) [richfaces-components-ui-4.3.4.Final.jar:4.3.4.Final]
at org.richfaces.renderkit.html.FocusRenderer.doEncodeEnd(FocusRenderer.java:91) [richfaces-components-ui-4.3.4.Final.jar:4.3.4.Final]
at org.richfaces.renderkit.RendererBase.encodeEnd(RendererBase.java:175) [richfaces-components-ui-4.3.4.Final.jar:4.3.4.Final]
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at org.richfaces.context.ExtendedPartialViewContextImpl$RenderVisitCallback.visit(ExtendedPartialViewContextImpl.java:557) [richfaces-core-impl-4.3.4.Final.jar:4.3.4.Final]
at org.richfaces.context.RenderExtendedVisitContext.invokeVisitCallbackForImplicitComponent(RenderExtendedVisitContext.java:71) [richfaces-core-impl-4.3.4.Final.jar:4.3.4.Final]
at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:333) [richfaces-core-impl-4.3.4.Final.jar:4.3.4.Final]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1612) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at org.richfaces.component.AbstractTogglePanel.visitTree(AbstractTogglePanel.java:924) [richfaces-components-ui-4.3.4.Final.jar:4.3.4.Final]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at javax.faces.component.UIForm.visitTree(UIForm.java:371) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:310) [richfaces-core-impl-4.3.4.Final.jar:4.3.4.Final]
at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:213) [richfaces-core-impl-4.3.4.Final.jar:4.3.4.Final]
at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:981) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:391) [jsf-impl-2.1.7-jbossorg-2.jar:]
at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.7-jbossorg-2.jar:]
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.7-jbossorg-2.jar:]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:]
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.7-jbossorg-2.jar:]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
{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
12 years, 5 months