December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-1770) Enabling the testsuite to be used by users

by Pavel Tsekov (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1770?page=comments#action_12349319 ] Pavel Tsekov commented on JBAS-1770: ------------------------------------ What are the immediate requirements for this task ? Is it correct to consider altering the build/packaging process to include the testsuite and its dependencies into the distribution as the primary objective ? Which of the enhancements above are required and which should be added to the wish list ? Do we have to include some kind of documentation about the details on running the different tests ? Those questions might seem stupid to you but, please, bear with me since I am a newcomer and it is not obvious for me. > Enabling the testsuite to be used by users > ------------------------------------------ > > Key: JBAS-1770 > URL: http://jira.jboss.com/jira/browse/JBAS-1770 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Adrian Brock > Assigned To: Pavel Tsekov > > The testsuite should be available for users to use. > e.g. by including it in JBOSS_DIST/client or JBOSS_DIST/test??? > Other enhancements might include: > * Using JSR88 for deployment > * Using JSR160 for the MBeanServerConnection > * Exposing functionality available on the admin console > To help users provide better bug reports we should also > provide skeleton tests that the user can "extend". -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-372) Basic Publish Approval Workflow

by Sohil Shah (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-372?page=all ] Sohil Shah resolved JBPORTAL-372. --------------------------------- Resolution: Done > Basic Publish Approval Workflow > ------------------------------- > > Key: JBPORTAL-372 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-372 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal CMS > Affects Versions: 2.6 Final > Reporter: James Williams > Assigned To: Sohil Shah > Priority: Minor > Fix For: 2.6.Alpha1 > > > Optional feature which mandates that content changes must flow through a simple approval process that involves a Publisher and one or more Managers. Once the publisher makes a content change an email approval request should be sent to the manager list. The content change will not be made available to readers until all Managers approve the 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-931) jBPM Integration for CMS

by Sohil Shah (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-931?page=all ] Sohil Shah resolved JBPORTAL-931. --------------------------------- Resolution: Done > jBPM Integration for CMS > ------------------------ > > Key: JBPORTAL-931 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-931 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal CMS > Affects Versions: 2.6 Final > Reporter: Roy Russo > Assigned To: Sohil Shah > Fix For: 2.6.Alpha1 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-672) Server side valve

by Ovidiu Feodorov (JIRA)

Server side valve ----------------- Key: JBMESSAGING-672 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-672 Project: JBoss Messaging Issue Type: Sub-task Components: JMS Clustering Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical Fix For: 1.2.0.Beta1 -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3955) Upgrade commons-httpclient to v3.0.1

by Dimitris Andreadis (JIRA)

Upgrade commons-httpclient to v3.0.1 ------------------------------------ Key: JBAS-3955 URL: http://jira.jboss.com/jira/browse/JBAS-3955 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 Utilize the same version needed by JBoss Portal. -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-812) pluggable persistence

by Gavin King (JIRA)

pluggable persistence --------------------- Key: JBPM-812 URL: http://jira.jboss.com/jira/browse/JBPM-812 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Gavin King Assigned To: Tom Baeyens Currently jBPM likes to own and manage its own persistence context. This sucks, especially for Seam. I want to be able to pass it an existing Hibernate Session, or JPA EM, and have it use that. -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-810) Actions that validate transitions

by Gavin King (JIRA)

Actions that validate transitions --------------------------------- Key: JBPM-810 URL: http://jira.jboss.com/jira/browse/JBPM-810 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Gavin King Assigned To: Tom Baeyens It is useful to be able to have an action in the stack of actions for a transition "cancel" the transition: <transition name="delete"> <action expression="#{user.checkDeletePermission}"/> <action expression="#{document.delete}"/> </transition> The first action can cancel execution of the transition (and shortcircuit the rest of the action stack) by something like: * returning false? * throwing a predefined exception class CancelTransitionException? Or perhaps we could have a specific concept of a Validator: <transition name="delete"> <validator expression="#{user.admin}"/> <action expression="#{document.delete}"/> </transition> jBPM could have a Validator interface, and the Seam integration would just let you use an EL, and check the boolean return value. -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBPM-653) make the process parent classloader configurable

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-653?page=all ] Tom Baeyens updated JBPM-653: ----------------------------- Fix Version/s: jBPM 3.2 beta 1 (was: jBPM 3.2 alpha 3) > make the process parent classloader configurable > ------------------------------------------------ > > Key: JBPM-653 > URL: http://jira.jboss.com/jira/browse/JBPM-653 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM 3.2 beta 1 > > > now, always the jBPM classloader is taken as a parent for the process classloaders. this should be made configurable. at least one other possibility should be to configure the context classloader. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-395) Parallel FD

by Bela Ban (JIRA)

Parallel FD ----------- Key: JGRP-395 URL: http://jira.jboss.com/jira/browse/JGRP-395 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 With FD, when we have N nodes in a cluster and the switch crashes, every node will take roughly (N-1) * TIMEOUT ms to become a singleton cluster. This is because in regular FD, we only ping the next-in-line, e.g. - Cluster is A, B, C, D - The plug is pulled - Example B: - B decides that, after TIMEOUT ms, C is dead and excludes C from the pingable members - B then starts emitting a SUSPECT(C) until it gets a new view which excludes C - B switches to pinging D - After TIMEOUT ms, it switches to A - When all of C, D and A have been excluded, B decides to become a singleton cluster (and coordinator in it) SOLUTION: - Nodes don't actively ping other nodes. Instead, each nodes periodically multicasts a HEARTBEAT to the cluster - The HEARTBEAT is suppressed when a node sends data, because data counts as a heartbeat as well - Every node maintains a table of nodes and the last time we received either a message or a HEARTBEAT from that node - The counter is updated with the current time whenever that is the case - Periodically, we check whether any node has not sent us data/heartbeat for more the timeout ms. If so, we suspect it -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3962) XMBean persistence and JRMPProxyFactory failing together

by Ralf Zimmermann (JIRA)

XMBean persistence and JRMPProxyFactory failing together -------------------------------------------------------- Key: JBAS-3962 URL: http://jira.jboss.com/jira/browse/JBAS-3962 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Environment: Windows XP Reporter: Ralf Zimmermann Assigned To: Scott M Stark I modified the XMBean persitence example to add support fpr remote access via JNDI by adding the folowing to META-INF/jboss-service.xml  <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory" name="jboss.jmx:type=adaptor,name=MyService,protocol=jrmp,service=proxyFactory">  <depends optional-attribute-name="InvokerName">jboss:service=invoker,type=jrmp</depends>  <depends optional-attribute-name="TargetName">jboss.jmx:service=PersistentServiceExample</depends>  <attribute name="JndiName">PersistentServiceExample</attribute>  <attribute name="InvokeTargetMethod">true</attribute>  <attribute name="ExportedInterfaces">org.jboss.jmx.examples.persistence.PersistentServiceExampleMBean</attribute> <attribute name="ClientInterceptors"> <interceptors> <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor> <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> <interceptor>org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor</interceptor> <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor> </interceptors> </attribute> </mbean> If i try to access methods on the proxy object from within a web application I get the followin exception: java.lang.IllegalArgumentException: Unable to find operation getSomeString() at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:231) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:175) 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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:169) at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:118) at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:209) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:195) at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70) at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100) at $Proxy54.getSomeString(Unknown Source) at org.apache.jsp.index_jsp._jspService(index_jsp.java:48) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006