August 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1713) Status message continue to show building package even when it errored out

by Seegler Ittyavirah (JIRA)

Status message continue to show building package even when it errored out ------------------------------------------------------------------------- Key: JBRULES-1713 URL: https://jira.jboss.org/jira/browse/JBRULES-1713 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.7 Reporter: Seegler Ittyavirah Assignee: Mark Proctor Try to build a package that will result in a build error(a wrong rule) Click on the "Build Package" button in "Verify and assemble package" window This shows a status message "Validating and building package, please wait..." in "Verify and assemble package" window Now the package build errors out and shows an error popup window with message "An error occurred executing the action." close the error popup by clicking on 'x' button However old message "Validating and building package, please wait..." still remains on the "Verify and assemble package" window -- 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

17 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-877) TreeCache usage should not depend on trove.jar

by Galder Zamarreno (JIRA)

TreeCache usage should not depend on trove.jar ---------------------------------------------- Key: JBCACHE-877 URL: http://jira.jboss.com/jira/browse/JBCACHE-877 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1 Reporter: Galder Zamarreno Assigned To: Manik Surtani Priority: Minor A customer is upgrading from JBC 1.1 to 1.4.0.SP1 and even though it only uses plain TreeCache, it gets a NoClassDefFoundError for trove classes. 2006-11-23 13:19:03,781 ERROR RpcDispatcher exception=java.lang.NoClassDefFoundError: gnu/trove/TObjectHashingStrategy This is a TreeCacheAop/PojoCache dependency and therefore, should be isolated and attempted to be loaded only when PojoCache used. -- 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

17 years, 11 months

7
28
0 / 0

[JBoss JIRA] Created: (JBRULES-1703) BRMS: test scenario should show which fileds don't match

by Jaroslaw Kijanowski (JIRA)

BRMS: test scenario should show which fileds don't match -------------------------------------------------------- Key: JBRULES-1703 URL: https://jira.jboss.org/jira/browse/JBRULES-1703 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale Fix For: 5.0.0.M2 I'll attach screenshots... what I mean is that when I run this test scenario, I would expect to see a green icon next to: [Person] field [age] was [123]. and [Person] field [name] was [Pierre]. and a yellow next to [Person] field [sex] was [m] expected [f]. (like it is now). These first two fields (age and name) should be green in the 1st screenshot; have a look at the 2nd screenshot, I didn't change anything, just the 3rd field to match the expectations with the results. -- 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

17 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2112) No error message when creating folder without name

by Martin Putz (JIRA)

No error message when creating folder without name -------------------------------------------------- Key: JBPORTAL-2112 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2112 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.6 Final Reporter: Martin Putz Assignee: Sohil Shah When we create a CMS folder and let the name field empty the CMS Admin Portlet accepts this but doesn't create it. It's correct behaviour but it would be better if additionally an appropriate error message was displayed. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2111) Copy/Move function breaks the approval/publish workflow

by Martin Putz (JIRA)

Copy/Move function breaks the approval/publish workflow ------------------------------------------------------- Key: JBPORTAL-2111 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2111 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.6 Final Environment: CMS with enabled publish/approval workflow. Reporter: Martin Putz Assignee: Sohil Shah 1. Copying an unpublished file makes it published When we copy a file which never has been published into another folder the copy becomes published automatically. This happens even when it's done by a user who hasn't the permission to publish. The same happens when copying folders containing unpublished files into another folder. This is an undesired bypass of the workflow. 2. Move an unpublished file breaks the relation from the pending approval task to the CMS content -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2110) Export/Import functionality should better integrate the approval/publish workflow aspect

by Martin Putz (JIRA)

Export/Import functionality should better integrate the approval/publish workflow aspect ---------------------------------------------------------------------------------------- Key: JBPORTAL-2110 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2110 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.6 Final Reporter: Martin Putz Assignee: Sohil Shah 1. Exporting unpublished cms content results in empty files inside the zip-archive. Furthermore, the user should have the possibility to choose if he wishes to export 1) all of the content or 2) only the published elements. It is obvious that in second case there should not be any empty/ dead elements in the zip-archive. 2. Every file in an uploaded archive should start a dedicated workflow. Uploading a file starts the workflow. Uploading the same file but archived doesn't start the workflow. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMICROCONT-323) Add ExecutionEnvironmet interface to Controller

by Ales Justin (JIRA)

[ https://jira.jboss.org/jira/browse/JBMICROCONT-323?page=com.atlassian.jir... ] Ales Justin updated JBMICROCONT-323: ------------------------------------ JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=140275 > Add ExecutionEnvironmet interface to Controller > ----------------------------------------------- > > Key: JBMICROCONT-323 > URL: https://jira.jboss.org/jira/browse/JBMICROCONT-323 > Project: JBoss MicroContainer > Issue Type: Task > Components: Dependency > Affects Versions: JBossMC.2.0.0.Beta16 > Reporter: Ales Justin > Assignee: Ales Justin > Fix For: JBossMC.2.0.0.CR1 > > > With concurrency deployment issue JBMICROCONT-265, > users should be able to use their own execution environment > to trigger/start new threads when deployment should be dealt in parallel. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1710) BRMS: test scenario bug: field's value is not initialized?

by Jaroslaw Kijanowski (JIRA)

BRMS: test scenario bug: field's value is not initialized? ---------------------------------------------------------- Key: JBRULES-1710 URL: https://jira.jboss.org/jira/browse/JBRULES-1710 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale Fix For: 5.0.0.M2 Please follow these steps to reproduce: new category, new package, new technical rule: when Cheese( smelly == true ) then insert( new Person("Pierre", "m", 18) ); smelly is a boolean field in Cheese now create a test scenario: click on Given and add a Cheese fact; click on add a field, choose smelly and now: true is select by default. Leave it as is, our rule should fire, right? Run the test, you'll notice that 0 rules fired. Now change smelly from true to false, change it back to true and run the test. One rule fired. -- 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

17 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1709) BRMS: adding rule flow breaks something

by Jaroslaw Kijanowski (JIRA)

BRMS: adding rule flow breaks something --------------------------------------- Key: JBRULES-1709 URL: https://jira.jboss.org/jira/browse/JBRULES-1709 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale Fix For: 5.0.0.M2 rev #21307 I have a rule: when Cheese( smelly == true ) then insert( new Person("Pierre", "m", 18) ); and a corresponding test scenario (insert smelly Cheese and expect Person(...) ). Works fine. Now I add(upload) a rule flow to the package, for example that attached one. Now my test scenario fails: Unable to load a required class. Unable to find class 'Cheese' server log: 16:55:55,273 INFO [STDOUT] ERROR 31-07 16:55:55,271 (ServiceImplementation.java:runScenario:1610) java.lang.ClassNotFoundException: Unable to find class 'Cheese' 16:55:55,276 INFO [STDOUT] ERROR 31-07 16:55:55,273 (GWTToSeamAdapter.java:callWebRemoteMethod:81) Error invoking a service org.drools.guvnor.client.rpc.DetailedSerializableException: Unable to load a required class. at org.drools.guvnor.server.ServiceImplementation.runScenario(ServiceImplementation.java:1611) at org.drools.guvnor.server.ServiceImplementation.runScenario(ServiceImplementation.java:1600) at org.drools.guvnor.server.ServiceImplementation.runScenario(ServiceImplementation.java:1549) at sun.reflect.GeneratedMethodAccessor133.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:46) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.security.SecurityInterceptor.aroundInvoke(SecurityInterceptor.java:118) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) at org.drools.guvnor.server.ServiceImplementation_$$_javassist_4.runScenario(ServiceImplementation_$$_javassist_4.java) at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.remoting.gwt.GWTToSeamAdapter.callWebRemoteMethod(GWTToSeamAdapter.java:76) at org.jboss.seam.remoting.gwt.GWTRemoteServiceServlet.processCall(GWTRemoteServiceServlet.java:291) at org.jboss.seam.remoting.gwt.GWTRemoteServiceServlet.doPost(GWTRemoteServiceServlet.java:173) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.web.ContextFilter$1.process(ContextFilter.java:42) at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) at org.jboss.seam.web.ContextFilter.doFilter(ContextFilter.java:37) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) -- 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

17 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1714) Default package selection in "Create new Asset" window is not correct

by Seegler Ittyavirah (JIRA)

Default package selection in "Create new Asset" window is not correct --------------------------------------------------------------------- Key: JBRULES-1714 URL: https://jira.jboss.org/jira/browse/JBRULES-1714 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7 Reporter: Seegler Ittyavirah Assignee: Mark Proctor Lets have more than one packages in the package explorer view select the second package from the package explorer tree view Expand the selected package node Click on new rule icon Watch the package selection in the "Create New Rule Asset" window. It is always the first package , not the current selected package -- 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

17 years, 11 months

3
2
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 August 2008