April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-208) Example of custom client-side/server-side interceptors

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-208?page=all ] Tim Fox updated JBMESSAGING-208: -------------------------------- Fix Version/s: Unscheduled (was: Miscellaneous) > Example of custom client-side/server-side interceptors > ------------------------------------------------------ > > Key: JBMESSAGING-208 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-208 > Project: JBoss Messaging > Issue Type: Task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Provide an example of writing and configuring a custom client-side and server-side AOP interceptor. > Add the example to docs/examples so it can be used as an integration test. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-357) Update the Messaging Core documentation

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-357?page=all ] Tim Fox updated JBMESSAGING-357: -------------------------------- Fix Version/s: Unscheduled (was: Miscellaneous) > Update the Messaging Core documentation > --------------------------------------- > > Key: JBMESSAGING-357 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-357 > Project: JBoss Messaging > Issue Type: Task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 1 week > Remaining Estimate: 1 week > -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-123) Unify the "ServiceContainer" testing framework with similar efforts in other projects

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-123?page=all ] Tim Fox updated JBMESSAGING-123: -------------------------------- Fix Version/s: Unscheduled (was: Miscellaneous) > Unify the "ServiceContainer" testing framework with similar efforts in other projects > ------------------------------------------------------------------------------------- > > Key: JBMESSAGING-123 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-123 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > > JBoss Messaging is currently using for tests a "ServiceContainer", which is able to instantiate a scaled-down version of the microkernel and essential services (transactions, inmemory database, JNDI, etc), while using for these services actual implementations available from other JBoss projects/thirdparty archives. > * Try to integrate this effort with what is being done in other projects. > * Possible use Bill's work: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=63480 > * Other reference http://jira.jboss.com/jira/browse/JBAS-1768 > * Move whatever infrastructure is required by this from src/org/jboss/messaging/tools to tests/src ..... -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-87) Light-weight JMS 1.1 / JGroups package

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-87?page=all ] Tim Fox updated JBMESSAGING-87: ------------------------------- Fix Version/s: Unscheduled (was: Miscellaneous) > Light-weight JMS 1.1 / JGroups package > -------------------------------------- > > Key: JBMESSAGING-87 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-87 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Facade > Reporter: Bela Ban > Priority: Minor > Fix For: Unscheduled > > > Motivation: people want to use JGroups, but need to program against a standard API, like JMS 1.1. > Create a distribution which includes only the relevant parts of the JMS 1.1 implementation that runs on top of JGroups (the 'Serverless JMS' part, not the client/server part). -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-271) Modifying a server/**/*Advised.java or a client/**/**Delegate.java file breaks the incremental build, because of AOPC failure

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-271?page=all ] Tim Fox updated JBMESSAGING-271: -------------------------------- Fix Version/s: Unscheduled (was: Miscellaneous) > Modifying a server/**/*Advised.java or a client/**/**Delegate.java file breaks the incremental build, because of AOPC failure > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-271 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-271 > Project: JBoss Messaging > Issue Type: Bug > Components: Build System > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > > Modifying a class that is going to be AOPCed (server/**/*Advised.java or a client/**/**Delegate.java) breaks the incremental build, as the AOPC fails to process it: > compile-classes: > [javac] Compiling 1 source file to C:\work\src\cvs\jboss-head\jms\output\classes > [aopc] java.lang.RuntimeException: defrost(): org.jboss.jms.client.delegate.ClientBrowserDelegate$close_N4742752445160157748 was pruned. > [aopc] at javassist.CtClassType.checkPruned(CtClassType.java:1093) > [aopc] at javassist.CtClassType.defrost(CtClassType.java:272) > [aopc] at org.jboss.aop.instrument.OptimizedInvocations.defrostClassIfExists(OptimizedInvocations.java:66) > [aopc] at org.jboss.aop.instrument.OptimizedInvocations.makeInvocationClass(OptimizedInvocations.java:96) > [aopc] at org.jboss.aop.instrument.OptimizedMethodInvocations.createOptimizedInvocationClass(OptimizedMethodInvocations.java:78) > [aopc] at org.jboss.aop.instrument.OptimizedMethodExecutionTransformer.transformMethod(OptimizedMethodExecutionTransformer.java:59) > [aopc] at org.jboss.aop.instrument.MethodExecutionTransformer.instrument(MethodExecutionTransformer.java:137) > [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:654) > [aopc] at org.jboss.aop.AspectManager.translate(AspectManager.java:835) > [aopc] at org.jboss.aop.AspectManager.transform(AspectManager.java:747) > [aopc] at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:345) > [aopc] at org.jboss.aop.standalone.Compiler.compile(Compiler.java:234) > [aopc] at org.jboss.aop.standalone.Compiler.main(Compiler.java:90) > [aopc] [error] failed to transform: org.jboss.jms.client.delegate.ClientBrowserDelegate.. Do verbose mode if you want full stack trace. > [aopc] java.lang.RuntimeException: failed to transform: org.jboss.jms.client.delegate.ClientBrowserDelegate > [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:728) > [aopc] at org.jboss.aop.AspectManager.translate(AspectManager.java:835) > [aopc] at org.jboss.aop.AspectManager.transform(AspectManager.java:747) > [aopc] at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:345) > [aopc] at org.jboss.aop.standalone.Compiler.compile(Compiler.java:234) > [aopc] at org.jboss.aop.standalone.Compiler.main(Compiler.java:90) > [aopc] Caused by: java.lang.RuntimeException: defrost(): org.jboss.jms.client.delegate.ClientBrowserDelegate$close_N4742752445160157748 was pruned. > [aopc] at javassist.CtClassType.checkPruned(CtClassType.java:1093) > [aopc] at javassist.CtClassType.defrost(CtClassType.java:272) > [aopc] at org.jboss.aop.instrument.OptimizedInvocations.defrostClassIfExists(OptimizedInvocations.java:66) > [aopc] at org.jboss.aop.instrument.OptimizedInvocations.makeInvocationClass(OptimizedInvocations.java:96) > [aopc] at org.jboss.aop.instrument.OptimizedMethodInvocations.createOptimizedInvocationClass(OptimizedMethodInvocations.java:78) > [aopc] at org.jboss.aop.instrument.OptimizedMethodExecutionTransformer.transformMethod(OptimizedMethodExecutionTransformer.java:59) > [aopc] at org.jboss.aop.instrument.MethodExecutionTransformer.instrument(MethodExecutionTransformer.java:137) > [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:654) > [aopc] ... 5 more > [aopc] Exception in thread "main" > BUILD FAILED > C:\work\src\cvs\jboss-head\jms\build.xml:339: Java returned: 1 > The workaround in this case is to do a ant clean and then rebuild everything from scratch, which is very inefficient. > Must be fixed properly -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-837) Write a JBoss Messaging Best Practices Guide

by Ovidiu Feodorov (JIRA)

Write a JBoss Messaging Best Practices Guide -------------------------------------------- Key: JBMESSAGING-837 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-837 Project: JBoss Messaging Issue Type: Feature Request Components: Documentation and Training Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.1 -- 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

19 years, 3 months

2
4
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-388) Write a JBossMQ to Messaging migration guide

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ] Tim Fox updated JBMESSAGING-388: -------------------------------- Fix Version/s: Unscheduled (was: Miscellaneous) > Write a JBossMQ to Messaging migration guide > -------------------------------------------- > > Key: JBMESSAGING-388 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Fix For: Unscheduled > > -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-153) JBoss Messaging should be capable of handling real big files (tens of megabytes possibly a hundred)

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-153?page=all ] Tim Fox updated JBMESSAGING-153: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > JBoss Messaging should be capable of handling real big files (tens of megabytes possibly a hundred) > --------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-153 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-153 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Messaging Core > Affects Versions: 1.0.0 alpha PR3 > Reporter: Karl de Boer > Fix For: 2.0.0 Beta 1 > > Original Estimate: 4 minutes > Remaining Estimate: 4 minutes > > As dicussed during JBW Barcelona i want to ask to investigate if it is posible to reliably sent very big messages from one jboss messaging node to another one (most likely on top of HTTPS(S). The business case is: mulitple organisations working in one workflow on digitally signed documents where Quality of Service is extremely important for instance patent applications. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-584) Eliminate jgroups.jar "processing"

by Ovidiu Feodorov (JIRA)

Eliminate jgroups.jar "processing" ---------------------------------- Key: JBMESSAGING-584 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-584 Project: JBoss Messaging Issue Type: Task Components: Build System Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Trivial Fix For: 1.2.0.CR1 During the release procedure, the current release script expands jgroups.jar and removes service deployment descriptos (gossip-service.xml multiplexer-service.xml). It has just been confirmed by the JGroups team that the presence of those deployment descriptors is not intentional, it's just an unwanted artifact of their release process. Get rid of "jgroups jar processing" as soon as we upgrade our dependency to a "clean" jgroups jar. -- 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

19 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-905) org.jboss.test.messaging.jms.clustering.FailoverValveTest.testConcurrentClose() fails on Linux

by Ovidiu Feodorov (JIRA)

org.jboss.test.messaging.jms.clustering.FailoverValveTest.testConcurrentClose() fails on Linux ---------------------------------------------------------------------------------------------- Key: JBMESSAGING-905 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-905 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Clebert Suconic Fix For: 1.2.0.GA junit.framework.AssertionFailedError at org.jboss.test.messaging.jms.clustering.FailoverValveTest.testConcurrentClose(FailoverValveTest.java:287) -- 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

19 years, 3 months

3
4
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 April 2007