June 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Moved: (JBAS-8093) Weld should visibly log when /WEB-INF/beans.xml is not found.

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8093?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELD-553 to JBAS-8093: -------------------------------------- Project: JBoss Application Server (was: Weld) Key: JBAS-8093 (was: WELD-553) Affects Version/s: (was: 1.0.1.Final) Security: Public Component/s: Weld/CDI (was: Bootstrap and Metamodel API) > Weld should visibly log when /WEB-INF/beans.xml is not found. > ------------------------------------------------------------- > > Key: JBAS-8093 > URL: https://jira.jboss.org/browse/JBAS-8093 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Weld/CDI > Reporter: Lincoln Baxter III > > An INFO or WARNING level log message must be displayed when loading a web-application where /WEB-INF/beans.xml is missing. > "/WEB-INF/beans.xml is not present - Beans in WAR " +warName+ " will not be loaded." > The user needs to know this because weld is making an important decision. Also, a common pitfall, defining EJBs with @Injected dependencies will break because the EJB's are discovered, @Injection is attempted, but fails because no other beans were loaded. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1206) TCPGOSSIP: add operations to change initial_hosts at runtime

by Bela Ban (JIRA)

TCPGOSSIP: add operations to change initial_hosts at runtime ------------------------------------------------------------ Key: JGRP-1206 URL: https://jira.jboss.org/browse/JGRP-1206 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Vladimir Blagojevic Priority: Minor Fix For: 2.10 We should add the following operations (exposed as @ManagedOperation !): @ManagedOperation public void addInitialHost(String hostname, int port); @ManagedOperation public boolean removeInitialHost(String hostname, int port); The RouterStubManager should stop pinging removed members (if it was attempting to re-establish a connection). -- 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

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7991) Upgrade ha-server-api to 2.0.0.Final

by Brian Stansberry (JIRA)

Upgrade ha-server-api to 2.0.0.Final ------------------------------------ Key: JBAS-7991 URL: https://jira.jboss.org/jira/browse/JBAS-7991 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 6.0.0.CR1 Needed for Infinispan integration, plus some general major release cleanups in the HAPartition and related APIs. -- 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

16 years, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-282) Incompatible signature change in HATarget

by Brian Stansberry (JIRA)

Incompatible signature change in HATarget ----------------------------------------- Key: JBCLUSTER-282 URL: https://jira.jboss.org/browse/JBCLUSTER-282 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Components: HA-Server-API Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: HA-Server-API 1.2.0.Final , HA-Server-API 2.0.0.Final The 2.0.0.Alpha series changed the return type of HATarget.getReplicants from ArrayList to List. This is breaking EJB3 (see EJBTHREE-2112) even though they actually handle the return value as a List. EJB3 needs a compatible interface for the 1.x series (for their usage in EAP 5.x) and the 2.x series (for AS 6 and later). So, solution is, in ha-server-api trunk and in a 1.2 branch: 1) Restore ArrayList as the getReplicants() return type. 2) Add public List<?> getReplicantList() 3) Deprecate getReplicants() 4) Release a 2.0.0.Alpha5 and a 1.2.0.Final 5) Move AS trunk to 2.0.0.Alpha5 so EJB3 testsuite can work 6) At some date, remove all AS trunk usage of the deprecated method 7) When the JBPAPP_5_1 branch is available for commits again, move it to 1.2.0 8) THEN move ejb3-proxy-clustered to 1.2.0, and have it use the new method. -- 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

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2545) Exception handling of KnowledgeBuilder .add for ruleflows should report compilation errors, not null-pointer exception

by David Goldstein (JIRA)

Exception handling of KnowledgeBuilder .add for ruleflows should report compilation errors, not null-pointer exception ---------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2545 URL: https://jira.jboss.org/browse/JBRULES-2545 Project: Drools Issue Type: Support Patch Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.1.0.M2 Environment: Windows XP, Eclipse plugin Reporter: David Goldstein Assignee: Mark Proctor Compiling and adding a ruleflow via KnowledgeBuilder's add method often returns a simple null-pointer exception when information about the actual node that did not compile is available. While one can make a work-around using: try { kbuilder.add(workFlow, workFlowtype); } catch(Exception t){ KnowledgeBuilderErrors errors = kbuilder.getErrors(); if (errors.size() > 0) for (KnowledgeBuilderError error: errors) System.err.println(error); } } throw new IllegalArgumentException("Could not parse knowledge."); } ... } throwing an exception with the actual build problem in the message seems appropriate so that users see an error describing the build problem when using traditional exception handling: try { kbuilder.add(workFlow, workFlowtype); } catch (Exception t) { t.printStackTrace() } -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1808) error logs in ChannelSupport.afterRecoveryEx()

by Toshiya Kobayashi (JIRA)

error logs in ChannelSupport.afterRecoveryEx() ---------------------------------------------- Key: JBMESSAGING-1808 URL: https://jira.jboss.org/browse/JBMESSAGING-1808 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.6.GA.SP1, 1.4.0.SP3.CP10 Reporter: Toshiya Kobayashi ChannelSupport.afterRecoveryEx() logs error level messages which looks like temporary logs for development. public void afterRollbackEx(boolean onePhase, boolean isRecovered) throws Exception { ... synchronized (lock) { log.error("----xxxx---- afterRollbackEx, add back ref: " + ref); addReferenceInMemory(ref); performDelivery = true; } } catch (Throwable t) { throw new TransactionException("Failed to add reference", t); } deliveringCount.decrement(); log.error("----xxxx---- afterRollbackEx, now count: " + deliveringCount); } } } log.error("----xxxx---- afterRollbackEx, performDelivery: " + performDelivery); ... -- 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

16 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1807) JBMESSAGING-1667 breaks existing functionality

by Justin Bertram (JIRA)

JBMESSAGING-1667 breaks existing functionality ---------------------------------------------- Key: JBMESSAGING-1807 URL: https://jira.jboss.org/browse/JBMESSAGING-1807 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP09 Reporter: Justin Bertram Assignee: Howard Gao Fix For: 1.4.0.SP3.CP11 The fix for JBMESSAGING-1667 breaks existing functionality. The specific functionality that it breaks is an MDB listening to a non-existent destination whose name contains multiple '/' characters. When the MDB is deployed the container creates a temporary destination on the MDB's behalf. Please restore this functionality. -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8089) JndiLoginInitialContextFactory is using deprecated security API

by Marcus Moyses (JIRA)

JndiLoginInitialContextFactory is using deprecated security API --------------------------------------------------------------- Key: JBAS-8089 URL: https://jira.jboss.org/browse/JBAS-8089 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: 6.0.0.M3 Reporter: Marcus Moyses Assignee: Marcus Moyses Fix For: 6.0.0.M4 JndiLoginInitialContextFactory is still using SecurityAssociation legacy API. Need to change it to use SecurityContextAssociation. -- 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

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8091) Fix POM validation warnings in the AS build.

by Paul Gier (JIRA)

Fix POM validation warnings in the AS build. -------------------------------------------- Key: JBAS-8091 URL: https://jira.jboss.org/browse/JBAS-8091 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Paul Gier Assignee: Paul Gier Fix For: 6.0.0.M4 Maven 3 is exposing a bunch of POM validation warnings. The POMs should be fixed to remove these warnings. -- 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

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-1211) endless loop at SpeedTest

by Danny Lade (JIRA)

endless loop at SpeedTest ------------------------- Key: JGRP-1211 URL: https://jira.jboss.org/browse/JGRP-1211 Project: JGroups Issue Type: Bug Affects Versions: 2.10 Environment: Windows 2007 Reporter: Danny Lade Assignee: Bela Ban Priority: Minor See at org.jgroups.tests.SpeedTest: If pakets get lost - without using JGroups but pure sockets - the SpeedTest never ends. The solution is rather simple, at subclass Reciever add: run { ... if (num_received != number) { System.err.println(" lost packet "+ number); num_received = number; } ... num_received++; -- 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

16 years, 1 month

2
5
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 June 2010