February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-763) Ensure JCA adapter from HEAD works with JBM

by Tim Fox (JIRA)

Ensure JCA adapter from HEAD works with JBM ------------------------------------------- Key: JBMESSAGING-763 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-763 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.CR1 Ensure JCA adapter from HEAD works with simple MDB uses cases. See forum thread -- 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

19 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-643) Revise Empty Failed Queues

by Clebert Suconic (JIRA)

Revise Empty Failed Queues -------------------------- Key: JBMESSAGING-643 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-643 Project: JBoss Messaging Issue Type: Sub-task Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov After we get the basics working, we will have to think about when/how to delete a queue without consumers. Router will still deliver messages to FailedOverQueues, even after there are no more clients on that queue. We will take care some of this with redelivery policies but we could just delete a queue after some time (+ transfering data to another LocalQueue) -- 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

19 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBBUILD-323) JBossBuild needs to be able to calculate component version using highest common denominator algorithm

by Alex Pinkin (JIRA)

JBossBuild needs to be able to calculate component version using highest common denominator algorithm ----------------------------------------------------------------------------------------------------- Key: JBBUILD-323 URL: http://jira.jboss.com/jira/browse/JBBUILD-323 Project: JBoss Build System Issue Type: Feature Request Affects Versions: JBossBuild-1.1 DR2 Reporter: Alex Pinkin We've already had this discussion, and thought that it's not easy to implement. However, I do think we need this done since I don't want all projects to enumerate all their 3rd party dependencies in build-thirdparty.xml. Example: these products include the following javassist versions 1. aop 1.5.0.GA: javassist 3.2.0.CR1, 3.2.0.CR2, 3.3.0.GA 2. ws 1.0.0.GA: javassist 3.2.0.CR1, 3.2.0.CR2, 3.3.0.GA 3. ejb3 1.0.0.CR8: javassist 3.2.0.CR1, 3.2.0.CR2, 3.2.0.GA JBossBuild needs to be able to determine that javassist 3.2.0.CR2 is the highest common denominator. Current behaviour is that JBossBuild takes the highest version of the component whenever it runs into it for the first time during the dependency graph traversal. Does Maven already support this? It seems like this should be one of the core maven features. Could you please look more info feasibility of implementing this in JBossBuild? -- 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

19 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-336) Create Maven pom for JBoss Test project

by Paul Gier (JIRA)

Create Maven pom for JBoss Test project --------------------------------------- Key: JBBUILD-336 URL: http://jira.jboss.com/jira/browse/JBBUILD-336 Project: JBoss Build System Issue Type: Feature Request Components: Maven Environment: All environments. Reporter: Paul Gier The jboss microcontainer is dependent on a recent version of JBoss Test. Since several projects are dependent on JBoss Test, it would be good to have a maven build of this project, and schedule it in cruise control. -- 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

19 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1198) Management Portlet does not Render in Portal 2.4 nor 2.6 when JAVA_HOME is set to JDK 6.0

by Matthew Martin (JIRA)

Management Portlet does not Render in Portal 2.4 nor 2.6 when JAVA_HOME is set to JDK 6.0 ----------------------------------------------------------------------------------------- Key: JBPORTAL-1198 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1198 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Environment: Windows XP SP2 Pentium D - 64Bit JDK 6.0 JBoss AS 4.0.5 JBoss Portal 2.4 thru 2.6 Reporter: Matthew Martin Steps to reproduce 1. JAVA_HOME environment variable is set to JDK 6.0 path 2. Deploy JBoss Portal 2.4 to JBOSS_HOME/server/default/deploy 3. Start JBoss AS 4.0.5 4. Login to JBoss Portal as admin/admin 5. Goto Admin tab - Management portlet does NOT display and renders following error: /WEB-INF/jsp/management/index.xhtml @41,58 rendered="#{!empty node.children}": Exception getting value of property children of base of type : org.jboss.portal.core.portlet.management.LazyPortalObjectTreeNode -- 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

19 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-788) [Identity component] ExpressionAssigmentHandler assigning group to pooled actors assigns group name not actors

by Luk Zdobylak (JIRA)

[Identity component] ExpressionAssigmentHandler assigning group to pooled actors assigns group name not actors -------------------------------------------------------------------------------------------------------------- Key: JBPM-788 URL: http://jira.jboss.com/jira/browse/JBPM-788 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Reporter: Luk Zdobylak Assigned To: Tom Baeyens FIle ExpressionAssigmentHandler.java from package org.jbpm.identity.assignment lines from 91-94 } else if (entity instanceof Group) { // put the group in the pool assignable.setPooledActors(new String []{entity.getName()}); } It seems that in line : assignable.setPooledActors(new String []{entity.getName()}); should be put not entity name but there should be code that retreives all actors assigned to group and prepares String[] array of their ids. -- 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

19 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-734) org.jbpm.util.XmlException: couldn't parse xml

by Ivan Garcia (JIRA)

org.jbpm.util.XmlException: couldn't parse xml ---------------------------------------------- Key: JBPM-734 URL: http://jira.jboss.com/jira/browse/JBPM-734 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Reporter: Ivan Garcia Assigned To: Tom Baeyens This code try{ String cfg = "<jbpm-configuration>"; cfg += "</jbpm-configuration>"; jbpmConfiguration = JbpmConfiguration.parseXmlString(cfg); }catch(Exception e){ e.printStackTrace(); } launch this exception, org.jbpm.util.XmlException: couldn't parse xml at org.jbpm.util.XmlUtil.parseXmlInputSource(XmlUtil.java:78) at org.jbpm.util.XmlUtil.parseXmlResource(XmlUtil.java:60) at org.jbpm.configuration.ObjectFactoryParser.parseElementsFromResource(ObjectFactoryParser.java:104) at org.jbpm.JbpmConfiguration.parseObjectFactory(JbpmConfiguration.java:299) at org.jbpm.JbpmConfiguration.parseXmlString(JbpmConfiguration.java:318) Caused by: java.net.MalformedURLException at java.net.URL.<init>(URL.java:601) at java.net.URL.<init>(URL.java:464) at java.net.URL.<init>(URL.java:413) at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.jbpm.util.XmlUtil.parseXmlInputSource(XmlUtil.java:76) ... 6 more and i dont know why :-( Thanks -- 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

19 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBBUILD-338) Create parent maven pom for all JBoss project poms to inherit from.

by Paul Gier (JIRA)

Create parent maven pom for all JBoss project poms to inherit from. ------------------------------------------------------------------- Key: JBBUILD-338 URL: http://jira.jboss.com/jira/browse/JBBUILD-338 Project: JBoss Build System Issue Type: Feature Request Components: Maven Reporter: Paul Gier Assigned To: Paul Gier Create a generic parent pom with default configuration for all jboss projects. This pom should include repository configuration, organization, default plugin configuration, and other configuration that is common to all jboss projects. Each top-level project pom should specify this pom as their parent. -- 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

19 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-622) JBossMessage.setJMSReplyTo() method does not allow to set up nulls

by Ilya Bochkov (JIRA)

JBossMessage.setJMSReplyTo() method does not allow to set up nulls ------------------------------------------------------------------ Key: JBMESSAGING-622 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-622 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.0.1.GA Reporter: Ilya Bochkov Assigned To: Ovidiu Feodorov The method body checks if a destination is an instance of JBossDestination. If you pass null then an exception is thrown, though null is a valid value. public void setJMSReplyTo(Destination replyTo) throws JMSException { if (!(replyTo instanceof JBossDestination)) { throw new InvalidDestinationException("Replyto cannot be foreign"); } this.replyToDestination = (JBossDestination)replyTo; } I've changed the method definition to: public void setJMSReplyTo(Destination replyTo) throws JMSException { if(replyTo == null){ this.replyToDestination = null; return; } if (!(replyTo instanceof JBossDestination)) { throw new InvalidDestinationException("Replyto cannot be foreign"); } this.replyToDestination = (JBossDestination)replyTo; } Please, if this is a correct fix incorporate it in future releases. Thanks! -- 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

19 years, 2 months

6
11
0 / 0

[JBoss JIRA] Created: (JBCACHE-956) Use LockParentForChildInsertRemove flag to control Optimistic node versioning

by Brian Stansberry (JIRA)

Use LockParentForChildInsertRemove flag to control Optimistic node versioning ----------------------------------------------------------------------------- Key: JBCACHE-956 URL: http://jira.jboss.com/jira/browse/JBCACHE-956 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani See JBCACHE-955 for background on locking issues related to inserting and removing child nodes. This JIRA is to look into using JBCACHE-955's LockParentForChildInsertRemove flag to control whether the insertion or removal of a child node affects a workspace node's data version. -- 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

19 years, 2 months

3
9
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 2007