March 2007 - jboss-jira - Jboss List Archives

[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, 3 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, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-877) jta configuration for process deployment in enterprise environment

by Tom Baeyens (JIRA)

jta configuration for process deployment in enterprise environment ------------------------------------------------------------------ Key: JBPM-877 URL: http://jira.jboss.com/jira/browse/JBPM-877 Project: JBoss jBPM Issue Type: Task Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2 another bug report from Jeff: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019684#4019684 " I have reported this before: 21:11:35,953 ERROR [[ProcessUploadServlet]] Servlet.service() for servlet Proces sUploadServlet threw exception org.hibernate.HibernateException: Unable to locate current JTA transaction at org.hibernate.context.JTASessionContext.currentSession(JTASessionCont it requires changes to jbpm.cfg.xml to set to false and CMTTransactionFactory to JTATransactionFactory org.hibernate.transaction.JTATransactionFactory " -- 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, 3 months

2
8
0 / 0

[JBoss JIRA] Created: (JBPM-889) fgdfgdfgfdg

by naeem ahmad (JIRA)

fgdfgdfgfdg ----------- Key: JBPM-889 URL: http://jira.jboss.com/jira/browse/JBPM-889 Project: JBoss jBPM Issue Type: Task Reporter: naeem ahmad Assigned To: Tom Baeyens -- 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, 3 months

3
2
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, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBPM-885) The Comment class taskes server time i.e. time on server machine at that time, buit few system may require feature to supply date and time while creating comment on a task node.

by Ashish Kumar Singh (JIRA)

The Comment class taskes server time i.e. time on server machine at that time, buit few system may require feature to supply date and time while creating comment on a task node. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBPM-885 URL: http://jira.jboss.com/jira/browse/JBPM-885 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1 Reporter: Ashish Kumar Singh Assigned To: Tom Baeyens Priority: Minor The Comment class taskes server time i.e. time on server machine at that time, buit few system may require feature to supply date and time while creating comment on a task node. To achieve this functionality we will need to extend Comment class. This will be great if we can include this functionality in Comment class itself by giving a seter method for Coment class. -- 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, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-353) Add controls to parent pom to build releases from jboss-repository.

by Paul Gier (JIRA)

Add controls to parent pom to build releases from jboss-repository. ------------------------------------------------------------------- Key: JBBUILD-353 URL: http://jira.jboss.com/jira/browse/JBBUILD-353 Project: JBoss Build System Issue Type: Feature Request Reporter: Paul Gier Assigned To: Paul Gier Fix For: MavenBuild 1.2 The jboss-parent pom should include some controls via profiles to ensure that release builds are dependent only on artifacts in the jboss-repository. In order to ensure that release builds are reproducible all artifacts should come from a repository controlled by jboss. -- 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, 3 months

1
1
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, 3 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, 3 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, 3 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 March 2007