January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-836) DSL expression browser

by Michael Neale (JIRA)

DSL expression browser ---------------------- Key: JBRULES-836 URL: http://jira.jboss.com/jira/browse/JBRULES-836 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8016) Complete Site and Documentation for AS6 Remoting

by Stan Silvert (JIRA)

Complete Site and Documentation for AS6 Remoting ------------------------------------------------ Key: JBAS-8016 URL: https://jira.jboss.org/jira/browse/JBAS-8016 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Stan Silvert -- 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

15 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-8832) Upgrade to Hibernate 3.6.1.Final

by Shelly McGowan (JIRA)

Upgrade to Hibernate 3.6.1.Final -------------------------------- Key: JBAS-8832 URL: https://issues.jboss.org/browse/JBAS-8832 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Hibernate service Reporter: Shelly McGowan Assignee: Steve Ebersole Fix For: 6.0.1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
11
0 / 0

[JBoss JIRA] Created: (JBRULES-2707) Split up drools-guvnor into drools-guvnor-gwtclient and drools-guvnor(-server)

by Geoffrey De Smet (JIRA)

Split up drools-guvnor into drools-guvnor-gwtclient and drools-guvnor(-server) ------------------------------------------------------------------------------ Key: JBRULES-2707 URL: https://jira.jboss.org/browse/JBRULES-2707 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: 5.2.0.M1 All classes/resources under the client/public package go to drools-guvnor-gwtclient. The drools-guvnor-gwtclient pom.xml - is of type war - has only the gwt dependencies All classes under the server package go to drools-guvnor(-server) The drools-guvnor(-server) pom.xml - is of type war - has a dependency on drools-guvnor-gwtclient (= war overlay!) - has dependencies on drools-core, drools-compiler (so on jdt too), ... What do we do with drools-ide-common and drools-factconstraints? Split them up to, or simply move the client package code into drools-guvnor? Where will the drools-ide-common and drools-factconstraints GWT modules be reused, besides in Guvnor? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
9
0 / 0

[JBoss JIRA] Created: (JBRULES-2337) Big performance issue caused by Task entity and I18N

by Julien Cheype (JIRA)

Big performance issue caused by Task entity and I18N ---------------------------------------------------- Key: JBRULES-2337 URL: https://jira.jboss.org/jira/browse/JBRULES-2337 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-process-task Reporter: Julien Cheype Assignee: Mark Proctor There is a big performance issue with the Task entity, for example query to TasksAssignedAsPotentialOwner can take more than 2 seconds for returning less than 20 records using a MySql server Correction consist in adding mappedBy="id" to subjects, names and description attributes -- 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

15 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JGRP-1268) Allow 0.0.0.0 as bind address

by Bela Ban (JIRA)

Allow 0.0.0.0 as bind address ----------------------------- Key: JGRP-1268 URL: https://issues.jboss.org/browse/JGRP-1268 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.12 Currently, bind_addr has to be a valid interface and the wildcard (0.0.0.0) address is not permitted. The reason is that bind_addr determines the physical address of a node, e.g. 192.168.1.5:46537, and using 0.0.0.0:46537 wouldn't allow us to identify the node in order to send it a message. To allow for TCP and UDP sockets to bind to the wildcard address, we could either use a bind_addr of 0.0.0.0 and introduce an additional property to pick the physical address (e.g. physical_addr="192.168.1.5" / physical_addr="GLOBAL"), or continue using bind_addr to determine the physical address and add a property (bind_to_wild_card_addr="true") to make the UDP and TCP sockets bind to the wildcard address (if true). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7049) tests-jacc-securitymgr test server fails to start with OpenJDK 6

by Shelly McGowan (JIRA)

tests-jacc-securitymgr test server fails to start with OpenJDK 6 ---------------------------------------------------------------- Key: JBAS-7049 URL: https://jira.jboss.org/jira/browse/JBAS-7049 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Reporter: Shelly McGowan Assignee: Anil Saldhana Fix For: JBossAS-5.2.0.Beta1 This test server runs with security manager and a server.policy file. The test target boots fine with Sun JDK 6. -- 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

15 years, 2 months

4
17
0 / 0

[JBoss JIRA] Created: (JBWEB-196) Version 0 cookies support

by Mike Millson (JIRA)

Version 0 cookies support ------------------------- Key: JBWEB-196 URL: https://issues.jboss.org/browse/JBWEB-196 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Affects Versions: JBossWeb-7.0.0.Beta1 Reporter: Mike Millson Assignee: Jean-Frederic Clere Version 0 cookies support. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-5345) New instance of resources injected on every onMessage MDB call

by Dok Tora (JIRA)

New instance of resources injected on every onMessage MDB call -------------------------------------------------------------- Key: JBAS-5345 URL: http://jira.jboss.com/jira/browse/JBAS-5345 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.0.5.GA Environment: Java version: 1.5.0_13,Apple Computer, Inc. OS-System: Mac OS X 10.4.11,i386 Reporter: Dok Tora Assigned To: Adrian Brock Priority: Critical A new instance of an injected bean is created every time the onMessage() method of an MDB is called. Details with sample code modifications to EJBTrailBlazer for reproduction can be found here: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132331 Problem was replicated in 4.0.5.GA, 4.2.1 and 4.2.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

5
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1945) RunAsIdentity is not propagated correctly

by Anton Kolmakov (JIRA)

RunAsIdentity is not propagated correctly ----------------------------------------- Key: EJBTHREE-1945 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1945 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: Plugin 1.0.17 Reporter: Anton Kolmakov I have one message driven bean A and two stateless beans B and C. A annotated with @RunAs, @RunAsPrincipal and @SecurityDomain. B and C annotated with @SecurityDomain. A receives message and calls B which calls C. RunAsPrincipal is propagated to B only but not to C. Why? Is it expected behavior? I expect propagation of RunAsPrinciapl to all beans in execution chain after bean with @RunAsPrincipal annotation. -- 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

15 years, 2 months

6
11
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 January 2011