August 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2241) Restore user's settings and portlets to default

by Brian Dill (JIRA)

Restore user's settings and portlets to default ----------------------------------------------- Key: JBPORTAL-2241 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2241 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.6.6 Final Reporter: Brian Dill Allow portal users to restore their portal to the original settings/portlets. Excerpt from discussion with Thomas Heute. "They could store the location of the reference as a portal object property of the copied page. And copy what exists for 'Copy this page to my dashboard' link. If the referenced page didn't change, they could then delete the current page, and copy the one referenced as portal object property." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-6012) Seam integration with AnnotationEnvironment / ResourceVisitor

by Ales Justin (JIRA)

Seam integration with AnnotationEnvironment / ResourceVisitor ------------------------------------------------------------- Key: JBAS-6012 URL: https://jira.jboss.org/jira/browse/JBAS-6012 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: MicroContainer bus Affects Versions: JBossAS-5.0.0.CR2 Reporter: Ales Justin Assignee: Ales Justin Priority: Minor Fix For: JBossAS-5.0.0.GA Integrate Seam's annotation / resource lookup with existing JBossAS / MC annotation / resource handling. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-6843) Metadata not created for deployments listed through Classpath attribute of Manifest.MF files

by jaikiran pai (JIRA)

Metadata not created for deployments listed through Classpath attribute of Manifest.MF files -------------------------------------------------------------------------------------------- Key: JBAS-6843 URL: https://jira.jboss.org/jira/browse/JBAS-6843 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-5.1.0.CR1, JBossAS-5.1.0.Beta1 Reporter: jaikiran pai Assignee: Ales Justin If a (EJB) *deployment* jar contains a MANIFEST.MF which points to another *deployment* (not a plain jar) through the ClassPath attribute, then the deployment framework does not generate metadata for the deployment listed in MANIFEST.MF Ex: A.jar is an EJB3 deployment which contains a MANIFEST.MF pointing to B.jar (another EJB3 deployment). While processing A.jar (and its entries in MANIFEST.MF), the deployment framework does not generate metadata for B.jar As per EJB3.0 core spec, section 20.3: The ejb-jar ﬁle must contain, either by inclusion or by reference, the class ﬁles of each enterprise bean as follows: - The enterprise bean class. - The enterprise bean business interfaces, web service endpoint interfaces, and home and component interfaces. - Interceptor classes. - The primary key class if the bean is an entity bean. We say that a jar ﬁle contains a second ﬁle "by reference" if the second ﬁle is named in the Class-Path attribute in the Manifest ﬁle of the referencing jar ﬁle or is contained (either by inclusion or by reference) in another jar ﬁle that is named in the Class-Path attribute in the Manifest ﬁle of the referencing jar ﬁle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (JBLOGGING-13) Only copy log level config over when receiving a JMX notification of type "jboss.logging.log4j.reconfigure"

by David Lloyd (JIRA)

Only copy log level config over when receiving a JMX notification of type "jboss.logging.log4j.reconfigure" ----------------------------------------------------------------------------------------------------------- Key: JBLOGGING-13 URL: https://jira.jboss.org/jira/browse/JBLOGGING-13 Project: JBoss Logging Issue Type: Task Security Level: Public (Everyone can see) Components: jboss-logbridge Affects Versions: 1.0.0.CR2-jboss-logbridge Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.0.0.CR3-jboss-logbridge -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1434) 5.0.0CR1: EJB refs across EARs don't work

by Juergen Zimmermann (JIRA)

5.0.0CR1: EJB refs across EARs don't work ----------------------------------------- Key: EJBTHREE-1434 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1434 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 5.0.0.CR1 Environment: JBoss 5.0.0.CR1, JDK 6u10beta Reporter: Juergen Zimmermann I'm having 2 different EARs and stateless session beans of the 2nd EAR are referencing stateless session beans of the 1st ear. It worked fine with 4.2.2 I'll attach a stripped down testcase: * src.zip: source of projects for Eclipse w/ JBoss Tools * hska.ear.zip: exploded EAR 1 (and zipped for transferring) * testHska.ear.zip: exploded EAR 1 (and zipped for transferring) src.zip: * hska is the 1st EAR project * hskaEJB contains the ejb module for hska * testHska is the EAR project for the 2nd EAR * testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB * testHskaClient is an application client module for testHska using JUnit -- 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

13 years, 11 months

3
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1429) SFSB replication soak testing

by Brian Stansberry (JIRA)

SFSB replication soak testing ----------------------------- Key: EJBTHREE-1429 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1429 Project: EJB 3.0 Issue Type: Task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 5.0.0.CR2 Long running tests of SFSB replication under heavy load. Should include: 1) Letting a significant percentage of sessions passivate and later activate. 2) Letting a significant percentage of sessions expire due to time out. 3) Invalidating remaining sessions after a while (i.e. don't use any sessions for the life of test; all get used and replaced after a while). 4) Perhaps, a low (say 1/1000) probability of failover. -- 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

13 years, 11 months

5
12
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1562) add ejb3 spefic params to wiki

by Radoslav Husar (JIRA)

add ejb3 spefic params to wiki ------------------------------ Key: EJBTHREE-1562 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1562 Project: EJB 3.0 Issue Type: Sub-task Reporter: Radoslav Husar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1887) implement to ExplicitFailoverInterceptor double checking to avoid stale failover requests

by Radoslav Husar (JIRA)

implement to ExplicitFailoverInterceptor double checking to avoid stale failover requests ----------------------------------------------------------------------------------------- Key: EJBTHREE-1887 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1887 Project: EJB 3.0 Issue Type: Sub-task Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1847) Error when creating a variable name equals the class name of the fact

by Nicolas Heron (JIRA)

Error when creating a variable name equals the class name of the fact ---------------------------------------------------------------------- Key: JBRULES-1847 URL: https://jira.jboss.org/jira/browse/JBRULES-1847 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.0.0.M2 Environment: Linux - Jboss 4.2.2 GA Reporter: Nicolas Heron Assignee: Mark Proctor Hello, in the BRMS, if you add a fact wih a variable name equals the class name of the fact, it does not work The good solution would be to avoid being able to create a fact variable name = class name when Calcul : Calcul() then end -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-842) Extract/index rule fact info on save

by Michael Neale (JIRA)

Extract/index rule fact info on save ------------------------------------ Key: JBRULES-842 URL: http://jira.jboss.com/jira/browse/JBRULES-842 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

13 years, 11 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2009