July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5761) Rename conf/*-service.xml to *-beans.xml to be consistent with naming conventions

by Scott M Stark (JIRA)

Rename conf/*-service.xml to *-beans.xml to be consistent with naming conventions --------------------------------------------------------------------------------- Key: JBAS-5761 URL: http://jira.jboss.com/jira/browse/JBAS-5761 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR1 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.CR2 The extension -service.xml is usually associated with JMX, but in this case the file is used with the microcontainer. I know that file naming conventions (e.g., *-service.xml) apply only in the deploy directory, and not in conf, but it can be initially confusing. -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5634) The drive name in jca sample for mssql is wrong

by Jason Oliveira (JIRA)

The drive name in jca sample for mssql is wrong ----------------------------------------------- Key: JBAS-5634 URL: http://jira.jboss.com/jira/browse/JBAS-5634 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: JBossAS-4.2.2.GA Environment: N/A Reporter: Jason Oliveira Assigned To: Samson Kittoli The drive name in jca sample for mssql is wrong. In the jca sample (tamplates for datasource configuration) the mssql-ds.xml speficies the driver-class like: com.microsoft.sqlserver.jdbc.SQLServerDriver But the driver-class for MSSQL2000 is: com.microsoft.jdbc.sqlserver.SQLServerDriver -- 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

16 years, 1 month

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

16 years, 1 month

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

16 years, 1 month

2
7
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

16 years, 1 month

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

16 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBREM-1008) Socket keep alive with client EJB and RMI over HTTP

by amar slimane (JIRA)

Socket keep alive with client EJB and RMI over HTTP --------------------------------------------------- Key: JBREM-1008 URL: http://jira.jboss.com/jira/browse/JBREM-1008 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.4.0.CR2 (Pinto) Environment: CentOS release 4.4 (Final) Reporter: amar slimane With the parameter 'invokerDestructionDelay', the same socket connection is reused for all client requests to the Server. This works fine with the socket transport but not with HTTP transport. The parameter 'invokerDestructionDelay' is taken into account and the HTTPClientInvoker is not removed but the socket is closed at each call. -- 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

16 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBASM-10) Release JBASM 0.1.1.GA

by Shelly McGowan (JIRA)

Release JBASM 0.1.1.GA ---------------------- Key: JBASM-10 URL: https://jira.jboss.org/jira/browse/JBASM-10 Project: JBoss AS Server Manager Issue Type: Release Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 0.1.1.GA Release needed to push out changes documented in JBASM-4 -- 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

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1366) state transfer optimisation (with preload, and in memory state transfer)

by Mircea Markus (JIRA)

state transfer optimisation (with preload, and in memory state transfer) ------------------------------------------------------------------------ Key: JBCACHE-1366 URL: http://jira.jboss.com/jira/browse/JBCACHE-1366 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mircea Markus Assigned To: Manik Surtani Priority: Minor Fix For: 3.0.0 Optimization can be done in in a configuration where the following are true: - prelaod - in-memory state transfer is enabled - no passivation - a) shared cache loader OR b)fetch persistent state Optimization:during in-memory state transfer frome cache ONE to cache TWO, do not transfer the regions which in cache TWO were set for preloading. a) is shared cache loader is on that these regions will be loaded from the store anyhow, so transfer of these regions is redundant b) the content of these regions will be transfered at persistent state transfer anyway, so again redundancy during in-memory state transfer -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-315) JBossXB for aspect domain does not set the parentFirst, extends, inheritBindings and inheritDefinitions attributes

by Kabir Khan (JIRA)

JBossXB for aspect domain does not set the parentFirst, extends, inheritBindings and inheritDefinitions attributes ------------------------------------------------------------------------------------------------------------------ Key: JBMICROCONT-315 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-315 Project: JBoss MicroContainer Issue Type: Bug Affects Versions: JBossMC.2.0.0.Beta16 Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossMC.2.0.0.CR1 -- 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

16 years, 1 month

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008