July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1674) BRMS: Error when renaming a category

by Jaroslaw Kijanowski (JIRA)

BRMS: Error when renaming a category ------------------------------------ Key: JBRULES-1674 URL: http://jira.jboss.com/jira/browse/JBRULES-1674 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assigned To: Mark Proctor Administration->Categories->New Category->newCat->Select newCat->click on Rename selected and get: An error occurred executing the action. org.drools.repository.RulesRepositoryException: javax.jcr.ItemExistsException: /drools:repository/drools:tag_area at org.drools.repository.RulesRepository.renameCategory(RulesRepository.java:939) at org.drools.guvnor.server.ServiceImplementation.renameCategory(ServiceImplementation.java:1395) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 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:21) 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.renameCategory(ServiceImplementation_$$_javassist_4.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 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:74) at org.jboss.seam.remoting.gwt.GWTRemoteServiceServlet.processCall(GWTRemoteServiceServlet.java:290) at org.jboss.seam.remoting.gwt.GWTRemoteServiceServlet.doPost(GWTRemoteServiceServlet.java:172) 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) Caused by: javax.jcr.ItemExistsException: /drools:repository/drools:tag_area at org.apache.jackrabbit.core.SessionImpl.move(SessionImpl.java:1010) at org.drools.repository.RulesRepository.renameCategory(RulesRepository.java:935) ... 52 more -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-59) Subdeployment manifest locations should not be added if they are in the parent context

by Adrian Brock (JIRA)

Subdeployment manifest locations should not be added if they are in the parent context -------------------------------------------------------------------------------------- Key: JBDEPLOY-59 URL: http://jira.jboss.com/jira/browse/JBDEPLOY-59 Project: JBoss Deployers Issue Type: Bug Components: deployer Reporter: Adrian Brock Fix For: JBDEPLOY-2.0.0.CR1 When AbstractStructureDeployer processes the manifest for a subdeployment context, it includes entries that are already included in the parent context within the classpath of . e.g. top-level.ear/utility.jar top-level.ear/sub-deployment.war If sub-deployment.war contains a manifest entry with Class-Path: utility.jar This should not be included because it is already in the classpath as part of top-level.ear (assuming top-level.ear lists it in the appliaction.xml, if it didn't it should include it in the cflasspath of subdeployment.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

16 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-494) Investigate marshalling format to simplify wireshark / ethereal plugin

by Bela Ban (JIRA)

Investigate marshalling format to simplify wireshark / ethereal plugin ----------------------------------------------------------------------- Key: JGRP-494 URL: http://jira.jboss.com/jira/browse/JGRP-494 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Currently, parsing JGroups network data via wireshark is difficult: - message lists don't have (a) total number of bytes and (b) bytes/message and - headers don't have (a) total bytes for all headers and (b) bytes / header Investigate whether we can change the marshalling format to accommodate the wireshark plugin. This has the nice side effect that the JGroups wire format becomes standardized, ie. each header has the same format. This allows us to display a header even if we don't know how to parse it. In this case, we'd simply display the name and number of bytes. Caveat: we want to avoid having to make messages bigger when marshalled. -- 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, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JGRP-653) Streaming API for large messages

by Bela Ban (JIRA)

Streaming API for large messages -------------------------------- Key: JGRP-653 URL: http://jira.jboss.com/jira/browse/JGRP-653 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.x For large messages, to load the entire payload into memory might be bad because the payload might be bigger than the max memory available. It would be useful to have an API which allows for use of input and output streams, so that large payloads can be read iteratively by a user and streamed out to the cluster via the underlying channel breaking the data in the input stream into chunks, which are fed into the input stream on the receivers side. Issues: we have to have 1 input stream per sender on the receiver side, because a stream is always defined between 2 parties (sender, receiver). Maybe something like NIO, where we register interest in a stream, are notified of new streams ('accept()') and get notified when data on any of the stream is available, would be beneficial. Demo is attached -- 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, 2 months

3
11
0 / 0

[JBoss JIRA] Created: (JGRP-771) Simplify UDP

by Vladimir Blagojevic (JIRA)

Simplify UDP ------------ Key: JGRP-771 URL: http://jira.jboss.com/jira/browse/JGRP-771 Project: JGroups Issue Type: Task Affects Versions: 2.7 Reporter: Vladimir Blagojevic Assigned To: Bela Ban Fix For: 2.7 We have some boilerplate code in UDP where we receive packets. We essentially need to read packets from socket and pass them to receive method of TP. In UDP we have the same code *repeated* to read packets from multicast and unicast socket. Unify packet reading into one class - PacketReceiver and use PacketReceiver for both unicast and multicast socket. Use features of JDK5 as well. See UDP.java revision 1.171 -- 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, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1681) BRMS: Insert logical does a regular insert

by Jaroslaw Kijanowski (JIRA)

BRMS: Insert logical does a regular insert ------------------------------------------ Key: JBRULES-1681 URL: http://jira.jboss.com/jira/browse/JBRULES-1681 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assigned To: Mark Proctor When I use the guided editor and add the action "Logically insert a new fact" and then look at the source I see: insert( new Person() ); instead of insertLogical( new Person() ); -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5782) HASingletonElector interface

by Brian Stansberry (JIRA)

HASingletonElector interface ---------------------------- Key: JBAS-5782 URL: https://jira.jboss.org/jira/browse/JBAS-5782 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.CR2 Create an interface that exposes the public ClusterNode elect(List<ClusterNode> candidates) method our current HASingletonElectionPolicy impls have. Lets those policies be used as delegates by other policies that are responsible for preparing the list of candidates. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5749) tcnative-1.dll version 1.1.14 not recognized in %JBOSS_HOME%\bin\native

by Juergen Zimmermann (JIRA)

tcnative-1.dll version 1.1.14 not recognized in %JBOSS_HOME%\bin\native ----------------------------------------------------------------------- Key: JBAS-5749 URL: http://jira.jboss.com/jira/browse/JBAS-5749 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR1 Environment: JBoss 5.0.0.CR1, JDK 6u10beta, WinXP SP2 Reporter: Juergen Zimmermann tcnative-1.dll version 1.1.14 and openssl.exe are available in %JBOSS_HOME%\bin\native However, server.log shows this log entry: 2008-07-09 17:28:38,756 INFO [org.apache.catalina.core.AprLifecycleListener] (main) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:/Programme/jboss/bin/native -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Closed: (JBAOP-509) Connect the graph to the rest of AOP code

by Flavia Rainone (JIRA)

[ https://jira.jboss.org/jira/browse/JBAOP-509?page=com.atlassian.jira.plug... ] Flavia Rainone closed JBAOP-509. -------------------------------- Resolution: Done > Connect the graph to the rest of AOP code > ----------------------------------------- > > Key: JBAOP-509 > URL: https://jira.jboss.org/jira/browse/JBAOP-509 > Project: JBoss AOP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Flavia Rainone > Assignee: Flavia Rainone > > This task consists in using the joinpoint graph during JBoss AOP execution. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAOP-502) Joinpoint Graph

by Flavia Rainone (JIRA)

[ https://jira.jboss.org/jira/browse/JBAOP-502?page=com.atlassian.jira.plug... ] Flavia Rainone closed JBAOP-502. -------------------------------- Resolution: Done Currently this feature is implemented in the JoinpointGraph branch only. > Joinpoint Graph > --------------- > > Key: JBAOP-502 > URL: https://jira.jboss.org/jira/browse/JBAOP-502 > Project: JBoss AOP > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.CR7 > Reporter: Flavia Rainone > Assignee: Flavia Rainone > > Implement the joinpoint graph algorithm for dynamic AOP -- 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, 2 months

1
0
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