Bug 1265600

Summary: WAS: ClassNotFoundException: org.uberfire.ext.widgets.common.client.tables.popup.DataGridFilterSummary
Product: [Retired] JBoss BRMS Platform 6 Reporter: Zuzana Krejčová <zkrejcov>
Component: Business CentralAssignee: Neus Miras <nmirasch>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: medium Docs Contact:
Priority: high    
Version: 6.2.0CC: kverlaen, lpetrovi, rsynek
Target Milestone: ER4   
Target Release: 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:38:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Zuzana Krejčová 2015-09-23 10:30:52 UTC
Description of problem:
On Websphere only, we get multiple instances of "ClassNotFoundException: org.uberfire.ext.widgets.common.client.tables.popup.DataGridFilterSummary" logged into server log (while deploying the business-central). 
The effect is otherwise unknown.


AnnotatedElementFactory error Unable to create AnnotatedType for class : [org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$Marshaller_for_org_uberfire_ext_widgets_common_client_tables_popup_DataGridFilterSummaryImpl]. Exception cause : [java.lang.ClassNotFoundException: org.uberfire.ext.widgets.common.client.tables.popup.DataGridFilterSummary]
                                 java.lang.TypeNotPresentException: Type org.uberfire.ext.widgets.common.client.tables.popup.DataGridFilterSummary not present
...
Caused by: java.lang.ClassNotFoundException: org.uberfire.ext.widgets.common.client.tables.popup.DataGridFilterSummary
...


Version-Release number of selected component (if applicable):
6.2

Comment 3 Neus Miras 2015-10-01 10:27:51 UTC
This message is related with the use of the annotation @Portable in a client side class. It had been fixed at master but it didn't come at the release. This problem don't affects the behavior, the effect is show an ugly message on server.

Now I have created a PR fix it in the branch release 0.7.x.