February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3370) Array fields are not supported in declared facts

by Davide Sottara (JIRA)

Davide Sottara created JBRULES-3370: --------------------------------------- Summary: Array fields are not supported in declared facts Key: JBRULES-3370 URL: https://issues.jboss.org/browse/JBRULES-3370 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Reporter: Davide Sottara Assignee: Mark Proctor Priority: Minor it should be possible to do declare Bean arrayField : SomeObject[] end optionally, declare Bean arrayField : SomeObject[] = new SomeObject[3] end -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
2
0 / 0

[JBoss JIRA] (JBRULES-3341) Specify .drl file encoding when creating resource

by Miles Wen (Created) (JIRA)

Specify .drl file encoding when creating resource ------------------------------------------------- Key: JBRULES-3341 URL: https://issues.jboss.org/browse/JBRULES-3341 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.3.0.Final Environment: drools 5.3.0 final, ubuntu linux 11.04, amd64, sun jdk 1.6u27 Reporter: Miles Wen Assignee: Mark Proctor Would you please provide a method in 'org.drools.io.ResourceFactory' like this: public static Resource newReaderResource(InputStream stream, String encoding); then I can use this method to load drl files as a stream while explicitly specify its ecoding? And in line: 287 of class 'org.drools.compiler.DrlParser': lexer = new DRLLexer( new ANTLRInputStream( is ) ); no encoding specified as well. The ANTLRInputStream has constructors which allows you to specify the encoding, otherwise it would figure out the encoding according to the environment, which is unpredictable some times. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
4
0 / 0

[JBoss JIRA] (JBRULES-3383) Order of fact retractions causes NPE

by Wolfgang Laun (JIRA)

Wolfgang Laun created JBRULES-3383: -------------------------------------- Summary: Order of fact retractions causes NPE Key: JBRULES-3383 URL: https://issues.jboss.org/browse/JBRULES-3383 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core, drools-core (expert) Affects Versions: 5.3.0.Final Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Critical Insert one from each, the second referencing the first: class Event{ String name; } class Monitor{ Event event; String name; } The following rule runs into a NPE, except when reversing the marked lines. rule "timeout" timer( int: 10s ) when $m: Monitor( name == $name ) $e: Event($name: name) then retract( $m ); // ======================= retract( $m.getEvent() ); // ======================== end Exception in thread "main" Exception executing consequence for rule "start monitoring" in hashcode: java.lang.NullPointerException at org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1101) at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1029) at org.drools.common.DefaultAgenda.fireUntilHalt(DefaultAgenda.java:1229) at org.drools.common.AbstractWorkingMemory.fireUntilHalt(AbstractWorkingMemory.java:753) at org.drools.common.AbstractWorkingMemory.fireUntilHalt(AbstractWorkingMemory.java:729) at org.drools.impl.StatefulKnowledgeSessionImpl.fireUntilHalt(StatefulKnowledgeSessionImpl.java:234) at hashcode.Main.execute(Main.java:148) at hashcode.Main.main(Main.java:206) Caused by: java.lang.NullPointerException at org.drools.base.hashcode.StateEvent42211789$getItemName.getValue(Unknown Source) at org.drools.base.ClassFieldReader.getValue(ClassFieldReader.java:87) at org.drools.rule.Declaration.getValue(Declaration.java:219) at hashcode.Rule_start_monitoringDefaultConsequenceInvoker.evaluate(Unknown Source) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1091) ... 7 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
3
0 / 0

[JBoss JIRA] (AS7-3363) Admin console: Creating a connector should show a list of available socket bindings

by Jan Martiska (JIRA)

Jan Martiska created AS7-3363: --------------------------------- Summary: Admin console: Creating a connector should show a list of available socket bindings Key: AS7-3363 URL: https://issues.jboss.org/browse/AS7-3363 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Heiko Braun Priority: Optional Attachments: connector.png For better usability experience: there should be a combobox or something listing the current possibilities (existing socket bindings), because if you enter a socket binding name that does not exist, the creation of connector will fail. Screenshot shows it all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JGRP-1025) Harden FLUSH

by Bela Ban (JIRA)

Harden FLUSH ------------ Key: JGRP-1025 URL: https://jira.jboss.org/jira/browse/JGRP-1025 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Vladimir Blagojevic Fix For: 2.9 Make sure no FLUSH is left hanging, e.g. due to the crash of the flush leader after the START-FLUSH round. In other words, make analyze the code and make sure STOP-FLUSH is eventually called. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
8
0 / 0

[JBoss JIRA] (AS7-3427) CLI archive

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-3427: -------------------------------------- Summary: CLI archive Key: AS7-3427 URL: https://issues.jboss.org/browse/AS7-3427 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Bernard Tison The idea is to have an archive containing deployment archives along with the cli script files: one of which deploys and sets up/configures the necessary resources and the other one undeploys and cleans things up, if necessary. The idea has been discussed http://lists.jboss.org/pipermail/jboss-as7-dev/2011-May/001836.html https://community.jboss.org/thread/164554 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-2166) Alternative JDKs for building and running - OpenJDK 6, 7, Sun JDK 7, IcedTea

by Ondrej Zizka (Created) (JIRA)

Alternative JDKs for building and running - OpenJDK 6, 7, Sun JDK 7, IcedTea ---------------------------------------------------------------------------- Key: AS7-2166 URL: https://issues.jboss.org/browse/AS7-2166 Project: Application Server 7 Issue Type: Sub-task Reporter: Ondrej Zizka James Perkins: {quote} At one point there was a JIRA for OpenJDK 6, in fact I think a couple. The issue with OpenJDK 6 is in the build we use some JavaScript and OpenJDK 6 doesn't come with a JavaScript engine. I tried a couple things to get Rhino working with it as that's what the Sun JDK uses, but I think it needs to implement an SPI to get it to work. I didn't look into it much beyond that. JDK 7 is a different issue. It's a bug in the annotation processing API which the JBoss Logging Tooling uses. I just refreshed my OpenJDK 7 update source and it looks like the bug is fixed in there. It's fixed in IcedTea as well. There could be the JavaScript issue here as well I can't actually remember, but I thought I had some successful builds with custom JDK's I compiled. I did just try with IcedTea 7 and got some other errors. I'm building the latest upstream of OpenJDK 7 now and we'll see if it works. I'll let you know either way. Let me know if you have any more questions on this. I did dig into a while ago a little. {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

7
8
0 / 0

[JBoss JIRA] Created: (JBAS-9121) CLONE - Cannot build JBoss AS 7 using OpenJDK

by Shelly McGowan (JIRA)

CLONE - Cannot build JBoss AS 7 using OpenJDK --------------------------------------------- Key: JBAS-9121 URL: https://issues.jboss.org/browse/JBAS-9121 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Affects Versions: 7.0.0.Beta1 Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 7.0.0.Beta2 Compilation fails with: ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.1:compile (default-compile) on project jboss-as-arquillian-common: Compilation failure [ERROR] /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-7.0.x-testSuite-openjdk/arquillian/common/src/main/java/org/jboss/as/arquillian/container/JBossASDeploymentPackager.java:[59,16] inconvertible types [ERROR] found : org.jboss.shrinkwrap.api.Archive<capture#470 of ?> [ERROR] required: org.jboss.shrinkwrap.api.spec.WebArchive I've confirmed this is the latest version of OpenJDK: java-1.6.0-openjdk-1.6.0.0-1.20.b17.el5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

7
10
0 / 0

[JBoss JIRA] (AS7-2999) Integrate Remoting / SASL based authentication with EJB3

by Darran Lofthouse (Created) (JIRA)

Integrate Remoting / SASL based authentication with EJB3 -------------------------------------------------------- Key: AS7-2999 URL: https://issues.jboss.org/browse/AS7-2999 Project: Application Server 7 Issue Type: Bug Components: EJB, Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker We need two approaches: - 1 - Support for the PLAIN SASL mechanism to pass the username and password straight to JAAS. 2 - Full SASL support with the JAAS security domain trusting the SASL Principal -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
12
0 / 0

[JBoss JIRA] Created: (AS7-1625) Cookies version 0 value rejected by org.apache.tomcat.util.http.Cookies

by Ondrej Zizka (JIRA)

Cookies version 0 value rejected by org.apache.tomcat.util.http.Cookies ----------------------------------------------------------------------- Key: AS7-1625 URL: https://issues.jboss.org/browse/AS7-1625 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.0.1.Final Environment: standalone Reporter: Ondrej Zizka Assignee: Remy Maucherat I have a cookie in browser which was set for redhat.com, so my AS 7 on ozizka.brq.redhat.com is receiving it to. Now that "version 0" cookie contains characters illegal acc. to RFC-2109 and RFC-2068: {code} Cookie: s_vi=[CS]v1|261............[CE]; ... {code} AS 7 logs: {code} 22:18:13,365 INFO [org.apache.tomcat.util.http.Cookies] (http--0.0.0.0-8080-2) Cookies: Invalid cookie. Value not a token or quoted value {code} I haven't checked whether only the single value is discarded or all cookies. Possibly related: JBPAPP-5813 Some related links: Discussion http://old.nabble.com/DO-NOT-REPLY--Bug-49525--New%3A-IE8%3A-Unabled-to-s... and bug https://issues.apache.org/bugzilla/show_bug.cgi?id=49525 about Tomcat 7's bug. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
13
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 February 2012