July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3621) Declared types : Constructor with more than 255 parameters

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3621?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on JBRULES-3621: -------------------------------------------------- Amana <ajuricic(a)redhat.com> made a comment on [bug 990701|https://bugzilla.redhat.com/show_bug.cgi?id=990701] Description of problem: When creating fact types declaratively in BRMS (5.2 and 5.3.0) no more than 255 fields can be added. We need to create fact types with more than 255 fields. In the GUI, when clicking "Validate" after adding enough fields to a declared fact type to exceed a total of about 255, we get a popup saying: "400 Sorry, a technical error occurred. Please contact a system administrator." In the console stack trace we see "java.lang.ClassFormatError: Too many arguments in method signature" > Declared types : Constructor with more than 255 parameters > ---------------------------------------------------------- > > Key: JBRULES-3621 > URL: https://issues.jboss.org/browse/JBRULES-3621 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (expert) > Affects Versions: 5.4.0.Final > Reporter: JP Chemali > Assignee: Mario Fusco > Fix For: 5.5.0.Beta1 > > > When declaring a class type in a drools file > {code:Java} > declare MyType > i1:int > i2:int > ... > i256:int > end > {code} > The generated *MyType* bean contains a constructor with ALL fields parameters, which when they exceed 255, cause an unrecoverable ClassFormatError > Possible solutions: > - Check this limit to skip the constructor generation in org.drools.factmodel.DefaultBeanClassBuilder.generateConstructors() > - Maybe an explicit annotation to disable the behavior for those who don't need it? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-187) Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/JASSIST-187?page=com.atlassian.jira.plugi... ] Scott Marlow commented on JASSIST-187: -------------------------------------- Yes, that is the case. http://pastebin.com/0cHr6ySt shows ClassFile.write being called for enhancing an lazy entity when running jdb against the attached example. > Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux > --------------------------------------------------------------------------------------- > > Key: JASSIST-187 > URL: https://issues.jboss.org/browse/JASSIST-187 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.16.0-GA, 3.16.1-GA, 3.17.0-GA > Environment: Windows 7 x64 Oracle JVM x86/x64 1.6.37 - no error > Linux Ubuntu x64 Oracle JVM x64 1.6.37 - error > Reporter: Alexander Zinin > Assignee: Shigeru Chiba > Attachments: javassist-test.rar, javassist-test.zip > > > It will be difficult to describe what the error. > I will attach source code that reproduce error. > If you have hibernate entity with overrided getId() method, in hibernate session this method returns null instead of correct value. > Running on Windows: > 2012-12-16 17:33:19,332 INFO ru.zinin.service.SomeServiceImpl :44 - ID = 1 > Running on Linux: > 2012-12-16 17:41:47,772 INFO ru.zinin.service.SomeServiceImpl :44 - ID = null > 2012-12-16 17:41:47,772 ERROR ru.zinin.service.SomeServiceImpl :46 - ID IS NULL!!! > Bug appeared in version 3.16.0. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1791) Unable to use Filter Expressions in filter-spec

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1791?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1791: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=982303 > Unable to use Filter Expressions in filter-spec > ------------------------------------------------ > > Key: WFLY-1791 > URL: https://issues.jboss.org/browse/WFLY-1791 > Project: WildFly > Issue Type: Feature Request > Components: CLI > Reporter: Emmanuel Hugonnet > Assignee: Alexey Loubyansky > Priority: Minor > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1791) Unable to use Filter Expressions in filter-spec

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created WFLY-1791: --------------------------------------- Summary: Unable to use Filter Expressions in filter-spec Key: WFLY-1791 URL: https://issues.jboss.org/browse/WFLY-1791 Project: WildFly Issue Type: Feature Request Components: CLI Reporter: Emmanuel Hugonnet Assignee: Alexey Loubyansky Priority: Minor -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-187) Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/JASSIST-187?page=com.atlassian.jira.plugi... ] Scott Marlow commented on JASSIST-187: -------------------------------------- Perhaps javassist is being used to lazy fetch the entity (which doesn't require hibernate.ejb.use_class_enhancer persistence to be set) > Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux > --------------------------------------------------------------------------------------- > > Key: JASSIST-187 > URL: https://issues.jboss.org/browse/JASSIST-187 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.16.0-GA, 3.16.1-GA, 3.17.0-GA > Environment: Windows 7 x64 Oracle JVM x86/x64 1.6.37 - no error > Linux Ubuntu x64 Oracle JVM x64 1.6.37 - error > Reporter: Alexander Zinin > Assignee: Shigeru Chiba > Attachments: javassist-test.rar, javassist-test.zip > > > It will be difficult to describe what the error. > I will attach source code that reproduce error. > If you have hibernate entity with overrided getId() method, in hibernate session this method returns null instead of correct value. > Running on Windows: > 2012-12-16 17:33:19,332 INFO ru.zinin.service.SomeServiceImpl :44 - ID = 1 > Running on Linux: > 2012-12-16 17:41:47,772 INFO ru.zinin.service.SomeServiceImpl :44 - ID = null > 2012-12-16 17:41:47,772 ERROR ru.zinin.service.SomeServiceImpl :46 - ID IS NULL!!! > Bug appeared in version 3.16.0. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1769) 2 config updates for OpenJDK 8

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1769?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-1769: ------------------------------ Fix Version/s: 8.0.0.Alpha4 > 2 config updates for OpenJDK 8 > ------------------------------ > > Key: WFLY-1769 > URL: https://issues.jboss.org/browse/WFLY-1769 > Project: WildFly > Issue Type: Feature Request > Components: EE > Reporter: Juergen Zimmermann > Assignee: David Lloyd > Fix For: 8.0.0.Alpha4 > > > JDK 8 uses the Javascript Engine Nashorn instead of Rhino in JDK 7 (and 6). > Therefore, 2 additional config lines are required to support JDK 8 in addition to JDK 7: > After making the following 2 config updates for bean validation my web app is running with WildFly and OpenJDK 8: > 1) In modules/system/layers/base/sun/jdk/main/module.xml: add the following <path> declaration as the 2nd subtag inside <paths>, i.e. after the "com/sun/script/javascript" for JDK 7: > {code} > <path name="jdk/nashorn/api/scripting"/> > {code} > 2) In modules/system/layers/base/sun/jdk/main/service-loader-resources/META-INF/services/javax.script.ScriptEngineFactory add the following line as the 2nd service, i.e. as a alternative service for JDK 7: > {code} > jdk.nashorn.api.scripting.NashornScriptEngineFactory > {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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-208) Build 5.6.0-SNAPSHOT on jenkins and prepare for 5.6.0.Final release

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-208?page=com.atlassian.jira.plugin... ] Geoffrey De Smet updated DROOLS-208: ------------------------------------ Assignee: Michael Biarnes Kiefer (was: Geoffrey De Smet) > Build 5.6.0-SNAPSHOT on jenkins and prepare for 5.6.0.Final release > ------------------------------------------------------------------- > > Key: DROOLS-208 > URL: https://issues.jboss.org/browse/DROOLS-208 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Davide Sottara > Assignee: Michael Biarnes Kiefer > > Requirements: > 1) All repositories in the 5.6.x repository-list need to be branched from 5.5.x. > https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/5.6.x/scrip... > Note: the repository list is far less than master (so you can safely ignore uberfire etc). > Warning 1: some repo's are already branched! Do not rebranch these: droolsjbpm-build-bootstrap, droolsjbpm-knowledge, drools > Warning 2: You need to branch from 5.5.x (NOT master!) to this new branch 5.6.x > Warning 3: jbpm uses different version numbering. You need to branch from jbpm 5.4.x to 5.5.x (NOT 5.6.x). All other repo's use the normal version. > 2) All the 5.6.x branches (and 5.5.x for jbpm)'s versions need to change from 5.5.1-SNAPSHOT to 5.6.0-SNAPSHOT (and from 5.4.0-SNAPSHOT to 5.5.0-SNAPSHOT for jbpm). > Note: droolsjbpm-tools's will need changes from 5.5.1.qualifier to 5.6.0.qualifier > 3) Create a new jenkins view for "drools 5.6.x and jbpm 5.5.x" > 4) Clone the 5.5.x jobs for all these repo's as 5.6.x jobs. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-208) Build 5.6.0-SNAPSHOT on jenkins and prepare for 5.6.0.Final release

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-208?page=com.atlassian.jira.plugin... ] Geoffrey De Smet updated DROOLS-208: ------------------------------------ Description: Requirements: 1) All repositories in the 5.6.x repository-list need to be branched from 5.5.x. https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/5.6.x/scrip... Note: the repository list is far less than master (so you can safely ignore uberfire etc). Warning 1: some repo's are already branched! Do not rebranch these: droolsjbpm-build-bootstrap, droolsjbpm-knowledge, drools Warning 2: You need to branch from 5.5.x (NOT master!) to this new branch 5.6.x Warning 3: jbpm uses different version numbering. You need to branch from jbpm 5.4.x to 5.5.x (NOT 5.6.x). All other repo's use the normal version. 2) All the 5.6.x branches (and 5.5.x for jbpm)'s versions need to change from 5.5.1-SNAPSHOT to 5.6.0-SNAPSHOT (and from 5.4.0-SNAPSHOT to 5.5.0-SNAPSHOT for jbpm). Note: droolsjbpm-tools's will need changes from 5.5.1.qualifier to 5.6.0.qualifier 3) Create a new jenkins view for "drools 5.6.x and jbpm 5.5.x" 4) Clone the 5.5.x jobs for all these repo's as 5.6.x jobs. > Build 5.6.0-SNAPSHOT on jenkins and prepare for 5.6.0.Final release > ------------------------------------------------------------------- > > Key: DROOLS-208 > URL: https://issues.jboss.org/browse/DROOLS-208 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Davide Sottara > Assignee: Geoffrey De Smet > > Requirements: > 1) All repositories in the 5.6.x repository-list need to be branched from 5.5.x. > https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/5.6.x/scrip... > Note: the repository list is far less than master (so you can safely ignore uberfire etc). > Warning 1: some repo's are already branched! Do not rebranch these: droolsjbpm-build-bootstrap, droolsjbpm-knowledge, drools > Warning 2: You need to branch from 5.5.x (NOT master!) to this new branch 5.6.x > Warning 3: jbpm uses different version numbering. You need to branch from jbpm 5.4.x to 5.5.x (NOT 5.6.x). All other repo's use the normal version. > 2) All the 5.6.x branches (and 5.5.x for jbpm)'s versions need to change from 5.5.1-SNAPSHOT to 5.6.0-SNAPSHOT (and from 5.4.0-SNAPSHOT to 5.5.0-SNAPSHOT for jbpm). > Note: droolsjbpm-tools's will need changes from 5.5.1.qualifier to 5.6.0.qualifier > 3) Create a new jenkins view for "drools 5.6.x and jbpm 5.5.x" > 4) Clone the 5.5.x jobs for all these repo's as 5.6.x jobs. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-208) Build 5.6.0-SNAPSHOT on jenkins and prepare for 5.6.0.Final release

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-208?page=com.atlassian.jira.plugin... ] Geoffrey De Smet reassigned DROOLS-208: --------------------------------------- Assignee: Geoffrey De Smet (was: Mark Proctor) > Build 5.6.0-SNAPSHOT on jenkins and prepare for 5.6.0.Final release > ------------------------------------------------------------------- > > Key: DROOLS-208 > URL: https://issues.jboss.org/browse/DROOLS-208 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Davide Sottara > Assignee: Geoffrey De Smet > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-208) Build 5.6.0-SNAPSHOT on jenkins and prepare for 5.6.0.Final release

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-208: ------------------------------------- Summary: Build 5.6.0-SNAPSHOT on jenkins and prepare for 5.6.0.Final release Key: DROOLS-208 URL: https://issues.jboss.org/browse/DROOLS-208 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Davide Sottara Assignee: Mark Proctor -- 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, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2013