May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1468) Authentication error for portal with just view permission

by John Gilbert (JIRA)

Authentication error for portal with just view permission --------------------------------------------------------- Key: JBPORTAL-1468 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1468 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Security Affects Versions: 2.6.CR2 Reporter: John Gilbert Assigned To: Julien Viet i changed the default portal to just require view and personalize permission and it works fine. i then created a new portal and set it up for view and personalize permission, but i get a 401 error when trying to access it. it will only grant access if i setup this portal up for viewrecursive permissions. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4457) org.jboss.test.classloader.test.CircularityUnitTestCase: testRecursiveMT fails with an MBean exception

by Richard Achmatowicz (JIRA)

org.jboss.test.classloader.test.CircularityUnitTestCase: testRecursiveMT fails with an MBean exception ------------------------------------------------------------------------------------------------------ Key: JBAS-4457 URL: http://jira.jboss.com/jira/browse/JBAS-4457 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-4.2.0.GA Environment: Windows 2003, x86_64, BEA JVM Windows 2003, x86, Sun JVM Reporter: Richard Achmatowicz Assigned To: Scott M Stark This test involves making an invovation, testRecursiveLoadMT, on a deployed MBean, jboss.test:name=CircularityError. The test fails repeatably. The exception raised on the client side is: Testcase: testRecursiveLoadMT took 5.218 sec Caused an ERROR null javax.management.MBeanException at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) Caused by: java.lang.Exception: Thread1 failed to load HARMIServerImpl_Stub, class=null at org.jboss.test.classloader.circularity.test.RecursiveCCETests.testRecursiveLoadMT(RecursiveCCETests.java:98) at org.jboss.test.classloader.circularity.Starter.testRecursiveLoadMT(Starter.java:154) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) PLEASE SEE THE LINKED ISSUE JBPAPP-203 FOR DETAILS -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1087) Add collection modification notifications

by Jason T. Greene (JIRA)

Add collection modification notifications ----------------------------------------- Key: JBCACHE-1087 URL: http://jira.jboss.com/jira/browse/JBCACHE-1087 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Jason T. Greene Assigned To: Jason T. Greene Fix For: 2.0.0.CR3, 2.0.0.GA -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-407) Target is not available on Constructor Caller Interception (genadvisor mode)

by Flavia Rainone (JIRA)

Target is not available on Constructor Caller Interception (genadvisor mode) ---------------------------------------------------------------------------- Key: JBAOP-407 URL: http://jira.jboss.com/jira/browse/JBAOP-407 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha4 Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.0.0.alpha5 The caller object (@Caller) is not available during constructor caller interceptions. This problem happens only when using annotated-parameter signature. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-976) EJB3 does not properly escape SQL keywords in postgres, fails to create tables

by Ariane van der Steldt (JIRA)

EJB3 does not properly escape SQL keywords in postgres, fails to create tables ------------------------------------------------------------------------------ Key: EJBTHREE-976 URL: http://jira.jboss.com/jira/browse/EJBTHREE-976 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: AS 4.2.0 GA Reporter: Ariane van der Steldt EJB3 does not properly escape SQL keywords in postgres, for example a table called 'group' (which is a keyword in group by). This problem is known at JBoss and a work around, using backticks, exists: http://jira.jboss.org/jira/browse/EJBTHREE-637?page=all However this work around is unsatisfactory and fails in numerous ways: - it is in-elegant - it is in violation with the EJB spec (JSR 220) which imples that column and table names are names, rather than SQL escaped names - it triggers bugs in JBoss, where column names consisting of concatenations (because of a ManyTo... relation); example: an entity E refering to an entity A with primary key column 'group' will generate queries like: select ... from E inner join A on (E.A_`group` = A."group") This also happens with automatic columns in ManyToMany join tables. - using backticks is not portable: many, if not all, other application servers will assume they have to escape the column and table names, causing @Column(name="`backtick`") to have a completely different meaning on different application servers. - triggering this bug in while performing table creation, may result in columns, constraints or even tables not being created, due to transactions failing because of invalid sql (could not create column A_`group`). -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Commented: (JBPM-165) process instance versioning

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-165?page=comments#action_12363719 ] Tom Baeyens commented on JBPM-165: ---------------------------------- if we add a log that marks the conversion, it might actually be a much simpler and still very good solution ! > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: http://jira.jboss.com/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.2 > > > i think jbpm could offer some degree of assistence in process instance versioning. > when a new version of a process is deployed, jbpm could do the following conversion for a process instance : > * input required: mapping of the nodes from the old to the new definition. > * cancel the old process instance > * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance. > * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance. > this way we can avoid the problematic conversion of logs, while still keeping them in the system. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-521) Create POM file and script for deploying JGroups build to JBoss Maven2 repo

by Manik Surtani (JIRA)

Create POM file and script for deploying JGroups build to JBoss Maven2 repo --------------------------------------------------------------------------- Key: JGRP-521 URL: http://jira.jboss.com/jira/browse/JGRP-521 Project: JGroups Issue Type: Task Reporter: Manik Surtani Assigned To: Manik Surtani Priority: Minor Fix For: 2.5 -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Commented: (JBPM-165) process instance versioning

by Bernd Ruecker (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-165?page=comments#action_12363704 ] Bernd Ruecker commented on JBPM-165: ------------------------------------ Hi Tom. Maybe a misunderstanding: I don't create a new process instance, I really change the existing one to point to the new process definition. So I "just" change the references to ProcessDefinition, Nodes, ... After that, the process instance is running in the new version, which works quite weill for most of the cases where we needed it. But maybe it is not so nice for the log... > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: http://jira.jboss.com/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.2 > > > i think jbpm could offer some degree of assistence in process instance versioning. > when a new version of a process is deployed, jbpm could do the following conversion for a process instance : > * input required: mapping of the nodes from the old to the new definition. > * cancel the old process instance > * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance. > * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance. > this way we can avoid the problematic conversion of logs, while still keeping them in the system. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-578) remove JbpmSession and JbpmSessionFactory

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-578?page=all ] Tom Baeyens updated JBPM-578: ----------------------------- Fix Version/s: jBPM 4.0 > remove JbpmSession and JbpmSessionFactory > ----------------------------------------- > > Key: JBPM-578 > URL: http://jira.jboss.com/jira/browse/JBPM-578 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM 4.0 > > > those are deprecated in jbpm 3.1 and will be removed in 3.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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-578) remove JbpmSession and JbpmSessionFactory

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-578?page=all ] Tom Baeyens closed JBPM-578. ---------------------------- Resolution: Deferred > remove JbpmSession and JbpmSessionFactory > ----------------------------------------- > > Key: JBPM-578 > URL: http://jira.jboss.com/jira/browse/JBPM-578 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM 4.0 > > > those are deprecated in jbpm 3.1 and will be removed in 3.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

19 years, 1 month

1
0
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 May 2007