September 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBBUILD-261) Build pom

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-261?page=all ] Paul Gier closed JBBUILD-261. ----------------------------- Resolution: Out of Date Issue replaced by JBBUILD-411 > Build pom > --------- > > Key: JBBUILD-261 > URL: http://jira.jboss.com/jira/browse/JBBUILD-261 > Project: JBoss Build System > Issue Type: Sub-task > Components: Maven > Reporter: Ruel Loehr > Assigned To: Paul Gier > Fix For: Maven Build - App Server > > -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBRULES-1112) drools-jbrms.war does not work with JBoss4.0.5 bundled with Jetty6.1.1

by Huishan Zhou (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-1112?page=comments#action_12375488 ] Huishan Zhou commented on JBRULES-1112: --------------------------------------- Before communicating with you, I use the jsf-impl.jar and jsf-api.jar from SUN's website, and from the MyEclipse plugin. (I did many tests for different sources of those jar files). After communicating with you, I use the jsf-impl.jar and jsf-api.jar bundled with jboss-faces.jar because you said it must use jboss-faces.jar. Today I tested again. I even did the test without putting drools-jbrms.war in standalone jetty-6.1.1's webapps but put the three jsf files in the lib of jetty-6.1.1 (not in the war's lib). It throws the error when the jetty is starting. But you claim that your three jsf jar files will not only make jetty working, but also make the drools-jbrms.war working, it is a big magic to us. Did you add any other jar files to a fresh standalone jetty-6.1.1 installation? > drools-jbrms.war does not work with JBoss4.0.5 bundled with Jetty6.1.1 > ---------------------------------------------------------------------- > > Key: JBRULES-1112 > URL: http://jira.jboss.com/jira/browse/JBRULES-1112 > Project: JBoss Rules > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-brms > Affects Versions: 4.0.0.GA > Environment: Windows XP Professional 2002 service pack 2, JDK1.6.0 > Reporter: Huishan Zhou > Assigned To: Fernando Meyer > Priority: Critical > Fix For: FUTURE > > > The bugs of the following test is based on running drools-jbrms.war > on JBoss4.0.5 bundled with Jetty6.1.1. (No bugs on running this war in > JBoss4.0.5 bundled with Tomcat5.5) > drools-jbrms.war is extracted from drools-4.0.0-brms.zip > which is downloaded from > http://labs.jboss.com/drools/downloads.html on 08/21/2007. > (I also tested drools-jbrms.war extracted from > jbossrules-4.0.0.12865MR3-brms.zip > downloaded from > http://labs.jboss.com/jbossrules/downloads > on 08/20/2007. Identical error message.) > (1) during starting of JBoss, it throws the > ClassNotFoundException, javax/faces/context/FacesContext, > and in web browser console, it showed that drools-jbrms deployment > failed. > We have fixed this exception by adding two jar files, jsf-impl.jar > and jsf-api.jar, to WEB-INF/lib > (2) After fixing errors in (1) we can start JBoss. And we can go > to > http://localhost:8080/drools-jbrms/drools-jbrms/org.drools.brms.JBRMS/ > welcome.jsp > and > http://localhost:8080/drools-jbrms/drools-jbrms/org.drools.brms.JBRMS/ > JBRMS.html with the showup of the code of JBRMS.html itself, not > the user name and password form that was showed up in the JBoss4.0.5 > bundled with Tomcat5.5 > and > we can also go to > http://localhost:8080/drools-jbrms/drools-jbrms/org.drools.brms.JBRMS/ > login.jsp (What is the purpose of this page?) > If we try to go to > http://localhost:8080/drools-jbrms/drools-jbrms/org.drools.brms.JBRMS/ > JBRMS.jsp > we got error. We opened JBRMS.jsp, we found that it missed one very > basic line (but this missing didn't cause any trouble while testing in > JBoss bundled with Tomcat ?) > <%@ page language="java" import="org.jboss.seam.security.Identity" > pageEncoding="ISO-8859-1"%> > After adding this line to the code. We still got errors: > = = = = errors message = = = = > org.apache.jasper.JasperException: Unable to compile class for JSP > Generated servlet error: > Only a type can be imported. org.jboss.seam.security.Identity > resolves to a package > An error occurred at line: 11 in the jsp file: > /drools-jbrms/org.drools.brms.JBRMS/JBRMS.jsp > Generated servlet error: > Identity cannot be resolved to a type > An error occurred at line: 10 in the jsp file: > /drools-jbrms/org.drools.brms.JBRMS/JBRMS.jsp > Generated servlet error: > org.jboss.seam.security.Identity cannot be resolved to a type > = = = = = = = = = = = = = = = = = = = > We have checked that the jar file for the class > org.jboss.seam.security.Identity is in the WEB-INF/lib of > drools-jbrms.war. -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-181) ManagedObject support

by Adrian Brock (JIRA)

ManagedObject support --------------------- Key: JBMICROCONT-181 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-181 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC_2_0_0_CR1 Add support for creating ManagedObjects 1) From annotations on classes 2) By overrides from xml/other mechanisms Support different ManagedObject use cases, e.g. * flat model - simple * flattening model - multiple classes in (multiple) trees of object appear as one flat model * sets/maps/collections etc. * annotations * etc. -- 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

18 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1677) Rework portlet instances page similarly to portlet definitions

by Chris Laprun (JIRA)

Rework portlet instances page similarly to portlet definitions -------------------------------------------------------------- Key: JBPORTAL-1677 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1677 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6.1 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.8 Final, 2.6.2 Final -- 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

18 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1678) Do not show preferences link in table displays if there are no preferences

by Chris Laprun (JIRA)

Do not show preferences link in table displays if there are no preferences -------------------------------------------------------------------------- Key: JBPORTAL-1678 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1678 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Chris Laprun Assigned To: Chris Laprun -- 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

18 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-178) Expand the ManagedObject spi to operations/runtime properties

by Scott M Stark (JIRA)

Expand the ManagedObject spi to operations/runtime properties ------------------------------------------------------------- Key: JBMICROCONT-178 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-178 Project: JBoss MicroContainer Issue Type: Feature Request Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC_2_0_0_CR1 Properties that are updatable at runtime as well as operations need to be supported from the ManagedObject spi. -- 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

18 years, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (JBAS-4670) Remove support for AopMarker and InstanceOfAopMarker marker interfaces

by Brian Stansberry (JIRA)

Remove support for AopMarker and InstanceOfAopMarker marker interfaces ---------------------------------------------------------------------- Key: JBAS-4670 URL: http://jira.jboss.com/jira/browse/JBAS-4670 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta3 These two interfaces are legacy "marker" interfaces that were used to mark classes for FIELD granularity (PojoCache) bytecode enhancement. In a JDK 5 world, this should be done with an annotation, not an interface. In any case, in AS 5 we just want to use the @Replicable annotation from PojoCache. In AS 4.x these marker interfaces were in package org.jboss.web.tomcat.tc5.session, which does not exist in AS 5. We're not going to add those packages just for these classes, so since keeping them means a package change, there's no point keeping them around for "backward compatibility". If users wish to aspectize classes for FIELD based on something other than @Replicable, they can just write their own jboss-aop.xml file. -- 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

18 years, 10 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBPM-288) Fork/Join and child token deactivation

by Benjamin Madsen (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-288?page=comments#action_12375428 ] Benjamin Madsen commented on JBPM-288: -------------------------------------- Not a problem. I figured it just needed a bump for attention. Thanks for getting to it. > Fork/Join and child token deactivation > -------------------------------------- > > Key: JBPM-288 > URL: http://jira.jboss.com/jira/browse/JBPM-288 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0 > Environment: Any > Reporter: Lukasz Czekierda > Assigned To: Tom Baeyens > Priority: Critical > Fix For: jBPM jPDL 3.2.2 > > Attachments: processdefinition.xml, SimpleProcessTest.java > > > Join implementation has incorrectly/no implemented activation of finished child tokens. They remain active till the end of the whole process. Example from junit test (Wfp03SynchronizationTest.testSynchronizationFirstTokenFirst) works perfectly as long as is unmodified. After adding a few bottom lines and changing a transition in join I get my error. Token.end is called on children and the root token in the LAST state, when finishing the entire process. When in stateX or stateY, the process still reports two active child tokens. > --- > "<process-definition>" + > " <start-state name='start'>" + > " <transition to='fork' />" + > " </start-state>" + > " <fork name='fork'>" + > " <transition name='first' to='one' />" + > " <transition name='second' to='two' />" + > " </fork>" + > " <state name='one'>" + > " <transition to='join' />" + > " </state>" + > " <state name='two'>" + > " <transition to='join' />" + > " </state>" + > " <join name='join'>" + > " <transition to='stateX' />" + > " </join>" + > " <state name='stateX'>" + > " <transition to='stateY' />" + > " </state>" + > " <state name='stateY'>" + > " <transition to='end' />" + > " </state>" + > " <end-state name='end' />" + > "</process-definition>" -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3940) Use the JGroups multiplexer in the 4.2 branch

by Brian Stansberry (JIRA)

Use the JGroups multiplexer in the 4.2 branch --------------------------------------------- Key: JBAS-3940 URL: http://jira.jboss.com/jira/browse/JBAS-3940 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.0.CR1 Branch_4_2 will use JGroups 2.4.1, so we can use the multiplexer and multiplex the various channels. Only code change for this is in ClusterPartition; other services use JBoss Cache where it is just a config change. -- 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

18 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-4659) jboss-4.2.1.GA.zip distribution doesn't include mail-ra.rar

by Pete Muir (JIRA)

jboss-4.2.1.GA.zip distribution doesn't include mail-ra.rar ----------------------------------------------------------- Key: JBAS-4659 URL: http://jira.jboss.com/jira/browse/JBAS-4659 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.1.GA Reporter: Pete Muir AS 4.0.5.GA came with server/default/deploy/mail-ra.rar, this isn't bundled in 4.2.1.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

18 years, 10 months

2
3
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 September 2007