January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-557) MuxChannel should not receive views after it disconnects

by Vladimir Blagojevic (JIRA)

MuxChannel should not receive views after it disconnects -------------------------------------------------------- Key: JGRP-557 URL: http://jira.jboss.com/jira/browse/JGRP-557 Project: JGroups Issue Type: Bug Affects Versions: 2.5 Reporter: Vladimir Blagojevic Assigned To: Bela Ban Brian Stansberry said: Noticed a behavior difference between a MuxChannel and a regular JChannel. If a service uses a regular JChannel and calls disconnect, it does not get a viewAccepted callback with the new view that excludes itself. If the service uses a MuxChannel, it does get the callback. I have a vague memory that this came up in discussions a long time ago (and that maybe we decided to ignore it???). Couldn't find anything in the archive though. In a way it's nice to get the view, but if we leave this as is, services that can handle either type of channel (e.g. JBoss Cache) will need to properly handle both cases. -- 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

18 years, 5 months

1
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1315) Rule that uses a 'collect' and 'from' clause together causes problem

by Igor Bolic (JIRA)

Rule that uses a 'collect' and 'from' clause together causes problem -------------------------------------------------------------------- Key: JBRULES-1315 URL: http://jira.jboss.com/jira/browse/JBRULES-1315 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 4.0.3 Reporter: Igor Bolic Test case: Write a Rule that uses a 'collect' and 'from' clause together, example: package com.sample.mypackage rule "Apply discount" when $order: Order(); $items : ArrayList() from collect (OrderItem() from $order.items) then #apply discount end first i add the package to RuleBase object, everthing works fine. When i try to 'refresh' my rules, i.e. first remove the package and again add the same (modified) package to the RuleBase object, following error occurs: java.lang.IllegalArgumentException: Cannot remove a sink, when the list of sinks is null at org.drools.reteoo.ObjectSource.removeObjectSink(ObjectSource.java:116) at org.drools.reteoo.AlphaNode.remove(AlphaNode.java:181) at org.drools.reteoo.LeftInputAdapterNode.remove(LeftInputAdapterNode.java:204) at org.drools.reteoo.FromNode.remove(FromNode.java:153) at org.drools.reteoo.RightInputAdapterNode.remove(RightInputAdapterNode.java:167) at org.drools.reteoo.BetaNode.remove(BetaNode.java:186) at org.drools.reteoo.RuleTerminalNode.remove(RuleTerminalNode.java:461) at org.drools.reteoo.ReteooBuilder.removeRule(ReteooBuilder.java:224) at org.drools.reteoo.ReteooRuleBase.removeRule(ReteooRuleBase.java:272) at org.drools.common.AbstractRuleBase.removePackage(AbstractRuleBase.java:460) ... I've found a workaround for this error by writing my .drl code as following: package com.sample.mypackage rule "Explode Cart" salience 11 dialect "java" when $order: Order() $item : OrderItem() from $order.items then insert( $item ); end rule "Apply discount" no-loop true when $order : Order(); $items : ArrayList() from collect (OrderItem()) then #apply discount end Now, my rules are 'refreshed' without any error. -- 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

18 years, 5 months

4
11
0 / 0

[JBoss JIRA] Created: (JBAS-4215) Need to externalize the web container class loader to use outside of the web container

by Scott M Stark (JIRA)

Need to externalize the web container class loader to use outside of the web container -------------------------------------------------------------------------------------- Key: JBAS-4215 URL: http://jira.jboss.com/jira/browse/JBAS-4215 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services, Web (Tomcat) service Reporter: Scott M Stark Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta3 We need a WarClassLoadingDeployer that allows for the creation of the web container class loader during the DeploymentUnit processing based on the class loading metadata. In the absence of jboss UCL or osgi bundle metadata, this should create the standard tomcat war first class loader. Not having this at the DeploymentUnit level does not allow other deployers to interact with war deployments properly. -- 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

18 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-3883) JBoss ignores "Class-Path" attribute in WAR's MANIFEST.MF

by Amit Kasher (JIRA)

JBoss ignores "Class-Path" attribute in WAR's MANIFEST.MF --------------------------------------------------------- Key: JBAS-3883 URL: http://jira.jboss.com/jira/browse/JBAS-3883 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading, Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Amit Kasher Assigned To: Scott M Stark An EAR file that deploys well in JBoss4.0.5 fails to deploy in JBoss5.0Beta1 when initializing the web application (NoClassDefFound). However, this ear does deploy well when taking the required jar files (the WAR dependencies) out of the EAR and placing them inside the .war/WEB-INF/lib folder, as well as removing the "Class-Path" entry in the WAR's MANIFEST.MF. Documents stating, as far as I understand, the existence of the requirement that this should work are here: http://java.sun.com/j2ee/verified/packaging.html ... as well as in the spec ... (http://jcp.org/en/jsr/detail?id=244) in section EE.8.2.1 (Bundled Libraries) starting in page 155. It's related to Tomcat's classpath (or to the classpath augmentation JBoss performs, where there were probably recent changes to support resource injection into web clients, like servlets). This is why I indicated Tomcat as an additional affected component. -- 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

18 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4333) JBoss DD shemas should use a jboss specific namespace

by Thomas Diesler (JIRA)

JBoss DD shemas should use a jboss specific namespace ----------------------------------------------------- Key: JBAS-4333 URL: http://jira.jboss.com/jira/browse/JBAS-4333 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossAS-5.0.0.CR1 Curently the documentation for jboss_5_0.xsd reads This is the XML Schema for the JBoss 5.0 deployment descriptor. The deployment descriptor must be named "META-INF/jboss.xml" in the EJB's jar file. All EJB deployment descriptors must indicate the JBoss schema by using the Java EE namespace: http://www.jboss.org/j2ee/schema and by indicating the version of the schema by using the version element as shown below: <jboss xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.org/j2ee/schema http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" version="5.0"> ... </jboss> The instance documents may indicate the published version of the schema using the xsi:schemaLocation attribute for the Java EE namespace with the following location: http://www.jboss.org/j2ee/schema/jboss_5_0.xsd Note, that the default namespace for element is http://java.sun.com/xml/ns/javaee, which is IMHO incorrect. This is the namespace reserved for standard JavaEE5 elements -- 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

18 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4306) Invalid invoker mbean names in standardjboss.xml

by Scott M Stark (JIRA)

Invalid invoker mbean names in standardjboss.xml ------------------------------------------------ Key: JBAS-4306 URL: http://jira.jboss.com/jira/browse/JBAS-4306 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 The following invoker-proxy-binding is useless in terms of defining the invoker-mbean such that it can be used as a ejb container dependency: <invoker-proxy-binding> <name>message-driven-bean</name> <invoker-mbean>default</invoker-mbean> <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory> <proxy-factory-config> <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI> <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI> <CreateJBossMQDestination>false</CreateJBossMQDestination>  <MinimumSize>1</MinimumSize> <MaximumSize>15</MaximumSize> <KeepAliveMillis>30000</KeepAliveMillis> <MaxMessages>1</MaxMessages> <MDBConfig> <ReconnectIntervalSec>10</ReconnectIntervalSec> <DLQConfig> <DestinationQueue>queue/DLQ</DestinationQueue> <MaxTimesRedelivered>10</MaxTimesRedelivered> <TimeToLive>0</TimeToLive> </DLQConfig> </MDBConfig> </proxy-factory-config> </invoker-proxy-binding> Either there should be an mbean representing the state of the default invoker, or the mdb invoker config specified in another way such that dependencies can be configured. -- 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

18 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4756) Fix org.jboss.test.cluster.multicfg.web.test.ScopedAttrBasedTestCase failures

by Brian Stansberry (JIRA)

Fix org.jboss.test.cluster.multicfg.web.test.ScopedAttrBasedTestCase failures ----------------------------------------------------------------------------- Key: JBAS-4756 URL: http://jira.jboss.com/jira/browse/JBAS-4756 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta3 Seeing intermittent failures with all the tests in org.jboss.test.cluster.multicfg.web.test.ScopedAttrBasedTestCase when running with a TCP config -- 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

18 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-116) Move SecurityConstants to SPI

by Anil Saldhana (JIRA)

Move SecurityConstants to SPI ----------------------------- Key: SECURITY-116 URL: http://jira.jboss.com/jira/browse/SECURITY-116 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Affects Versions: 2.0.2-BETA4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA5 Move it to SPI for usage in JBoss AS5. -- 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

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-115) Move SecurityContextAssociation to SPI

by Anil Saldhana (JIRA)

Move SecurityContextAssociation to SPI -------------------------------------- Key: SECURITY-115 URL: http://jira.jboss.com/jira/browse/SECURITY-115 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Affects Versions: 2.0.2-BETA4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA5 Move it to SPI for usage in JBoss AS5. -- 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

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-108) Replace Roles from Data Map in Security Context with RoleGroup in SubjectInfo

by Anil Saldhana (JIRA)

Replace Roles from Data Map in Security Context with RoleGroup in SubjectInfo ----------------------------------------------------------------------------- Key: SECURITY-108 URL: http://jira.jboss.com/jira/browse/SECURITY-108 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Identity, JBossSX, Security SPI Affects Versions: 2.0.2-BETA3 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA4 Migrate the previous roles storage in the Security Context data map into a RoleGroup construct in SubjectInfo. -- 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

18 years, 5 months

1
2
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 2008