March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBTM-173) Integrate with AS 4.2

by Mark Little (JIRA)

Integrate with AS 4.2 --------------------- Key: JBTM-173 URL: http://jira.jboss.com/jira/browse/JBTM-173 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Release Reporter: Mark Little Assigned To: Jonathan Halliday Fix For: 4.2.3 -- 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: (JBPORTAL-1317) Role Management Portlet: Create New Role Broken

by Bernard Tison (JIRA)

Role Management Portlet: Create New Role Broken ----------------------------------------------- Key: JBPORTAL-1317 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1317 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha2 Environment: Portal 2.6 trunk on JBoss AS 4.0.5 Fedora FC6, Firefox Browser 1.5 Reporter: Bernard Tison Assigned To: Julien Viet The create new role link in the role management portlet is broken. The link calls a javascript function. This javascript is defined in the jboss-portlet.xml of the portlet. <portlet> <portlet-name>RolePortlet</portlet-name> <transaction> <trans-attribute>Required</trans-attribute> </transaction> <header-content> <script type="text/javascript" language="javascript"> function hideShow(id) { var navpoint = document.getElementById(id); if (navpoint.className == 'hidden') { navpoint.className = 'shown'; } else { navpoint.className = 'hidden'; } } </script> </header-content> </portlet> This javascript does not get injected into the rendered HTML. The resulting HTML fragment looks like:  <script type="text/javascript"></script> I also tested this with the sample HeaderContentPortlet. I defined the following fragment in the jboss-portlet.xml of the HeaderContentPortlet: <header-content> <link rel="stylesheet" type="text/css" href="/portlet-styles/HeaderContent.css" media="screen"/> <script type="text/javascript" language="javascript"> function hideShow(id) { var navpoint = document.getElementById(id); if (navpoint.className == 'hidden') { navpoint.className = 'shown'; } else { navpoint.className = 'hidden'; } } </script> <meta name="description" content="test"/> </header-content> The resulting HTML:  <link type="text/css" rel="stylesheet" href="/portal-samples/portlet-styles/HeaderContent.css" media="screen"/> <script type="text/javascript"></script> <meta name="description" content="test"/> Wrapping the javascript function in a CDATA element did not solve the problem. -- 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
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1184) Update CMS TestSuite with workflow usecases

by Sohil Shah (JIRA)

Update CMS TestSuite with workflow usecases ------------------------------------------- Key: JBPORTAL-1184 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1184 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.Alpha1 Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 2.6.Beta1 -- 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
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1185) Update CMS TestSuite with fine grained security usecases

by Sohil Shah (JIRA)

Update CMS TestSuite with fine grained security usecases -------------------------------------------------------- Key: JBPORTAL-1185 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1185 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.Alpha1 Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 2.6.Beta1 -- 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
2
0 / 0

[JBoss JIRA] Created: (JBAS-3724) NotFoundInDispatcherException from InvokerLocator when accessing remote calls when on a non default port

by Grant Quimby (JIRA)

NotFoundInDispatcherException from InvokerLocator when accessing remote calls when on a non default port -------------------------------------------------------------------------------------------------------- Key: JBAS-3724 URL: http://jira.jboss.com/jira/browse/JBAS-3724 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services, EJB3, Remoting Affects Versions: JBossAS-4.0.4.GA Environment: One JBoss 4.0.4.GA install with two instances, one on the default ports and one on ports with an increase of 1000 on all port numbers. Reporter: Grant Quimby Assigned To: Dimitris Andreadis Priority: Blocker When trying to access a remote application that is running in a server instance that does not have the default InvokerLocator port (3873) the remote caller recieves a NotFoundInDispatcherException when trying to call a method in the EJB3 Stateless Session Bean as the EJB3 Session Bean's InvokerLocator is at port 4873 and not port 3873 where the Remote Proxy looks. Similar issue for Service Beans at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89537 This is okay presently but in approximately two weeks we need to be running four instances with Session beans in two of them, which is currently not possible in a production 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
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-347) Add dynamic generation of includes based on dependencies in pom

by Paul Gier (JIRA)

Add dynamic generation of includes based on dependencies in pom --------------------------------------------------------------- Key: JBBUILD-347 URL: http://jira.jboss.com/jira/browse/JBBUILD-347 Project: JBoss Build System Issue Type: Feature Request Reporter: Paul Gier Assigned To: Paul Gier Currently the includes are generated using extra plugin configuration. Maybe the list of includes can be generated by looking at which dependencies are required in the runtime scope. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-348) Figure out a way to warn the user if the deploy repository variables are not set.

by Paul Gier (JIRA)

Figure out a way to warn the user if the deploy repository variables are not set. --------------------------------------------------------------------------------- Key: JBBUILD-348 URL: http://jira.jboss.com/jira/browse/JBBUILD-348 Project: JBoss Build System Issue Type: Feature Request Reporter: Paul Gier Assigned To: Paul Gier Fix For: jboss-deploy-maven-plugin-1.2.GA There are two deployment variables. One for the local checkout of the jboss repository, and one for the maven repository. It would be nice if the build scripts could give some warning if either of these are not set when calling "mvn deploy" and then point the user to some explanation about how to set these either in settings.xml or from the command line. -- 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: (JBPORTAL-1248) Regression: Fix Consumer tests on 4.0.5 using JBoss WS 1.0.4

by Chris Laprun (JIRA)

Regression: Fix Consumer tests on 4.0.5 using JBoss WS 1.0.4 ------------------------------------------------------------ Key: JBPORTAL-1248 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1248 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.Beta1 Seems like there's a problem with the way Sessions are handled/passed by the WS stack. The problem does not occur on 4.0.5 (which uses 1.0.3.SP1). -- 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
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-849) PojoCache jmx test case failure

by Ben Wang (JIRA)

PojoCache jmx test case failure ------------------------------- Key: JBCACHE-849 URL: http://jira.jboss.com/jira/browse/JBCACHE-849 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Brian Stansberry Fix For: 2.0.0.GA Current pojo.jmx test is failing so I have commented them out. But we need to fix them before 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, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-3856) Update JBossRemoting to version 2.2.0

by Dimitris Andreadis (JIRA)

Update JBossRemoting to version 2.2.0 ------------------------------------- Key: JBAS-3856 URL: http://jira.jboss.com/jira/browse/JBAS-3856 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Remoting Reporter: Dimitris Andreadis Assigned To: Tom Elrod Fix For: JBossAS-5.0.0.Beta2 JBAS-3273 brought JBossAS Beta1 to remoting 2.2.0.Alpha2. This task is to track the upgrade to a stable 2.2.0 release. -- 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
1
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