March 2007 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: org.jboss.test.jbossmq.test cleanup in jboss5

by scott.stark＠jboss.org

The UIL2* tests have been removed. most of thest tests should have analogs in the internal jbm testsuite, but are not really integration tests and could be dropped. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032589#4032589 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032589

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: org.jboss.test.jbossmq.test cleanup in jboss5

by rachmatowicz＠jboss.com

The org.jboss.test.jbossmessaging.test tests consist of all the JMS tests from org.jboss.test.jbossmq.test which (i) did not have any obvious dependencies on JBossMQ and (ii) have been modified in such a way that they can be executed against JBossMQ or Messaging by setting up appropriate configuration files. The idea was to eventually have one directory of JMS tests, which would exercise only pure JMS functionality, and could be executed against either JMS implementation. At present, only the Messaging implementation is using these tests, as it is the default JMS provider in JBoss 5. I have a spreadsheet which I used to categorise the JBossMQ, if it is of any interest. There were some JBossMQ tests which are still in a pending state ( not yet included in the jbossmessaging package) as they test XA recovery, and XA recovery was not available in Messaging at the time. This list of tests from JBossMQ which were not carried over is: CleanTopicRemovalUnitTestCase ClientMonitorConnectionRaceUnitTestCase DestinationFullUnitTestCase HTTPConnectionUnitTestCase LargeMessageUnitTestCase NackWithRollbackUnitTestCase SelectorParserUnitTestCase SelectorSyntaxUnitTestCase UIL2ConnectionUnitTestCase UIL2InvocationLayerStressTestCase ExpiryDestinationTestCase HTTPJBossMQUnitTestCase ScheduledDeliveryUnitTestCase UIL2JBossMQUnitTestCase ReceiversImplStressTestCase ReceiversImplArrayListStressTestCase ReceiversImplLinkedListStressTestCase These all had JBossMQ depenedencies referenced in them. However, it may be that, for some of these tests, aside from some minor dependency on JBossMQ, a similar generic JMS test might want to be developed (e.g. LargeMessageUnitTestCase) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032576#4032576 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032576

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: JACC Policy Bean not getting injected into EJBModule

by scott.stark＠jboss.org

There isn't one. What is the need you have? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032572#4032572 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032572

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: Implicit container dependencies

by wolfc

"adrian(a)jboss.org" wrote : This has been turned off in JBoss5 (at least for EJB2). | | 1) The code was not (is not) portable | | 2) Just because remote access to jndi (either another member of the cluster | or a thirdparty jms provider) is flakey, you don't want it to create a queue | | 3) It obscures the most common problem, which is that you mistyped the jndi name | I want this functionality. The feature is that if you're running EJB3 with JBoss Messaging, EJB3 will create a queue for you if needed. 1. We only do it when running JBoss Messaging, so it's not ment to be portable. 2. We don't stuff anything in JNDI, we ask JBoss Messaging for a queue. It's similar to JBCTS-541, only there j2ee-mods is asking for a queue. I don't see a problem in that. Either admin, j2ee-mods or EJB3 deployer is creating a queue. BTW. I want to get JBCTS-541 out of the way. Shall I create a new DestinationManager which hooks into ServerPeer? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032567#4032567 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032567

17 years, 3 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Remove JBoss version of StandardService class

by anil.saldhana＠jboss.com

We have to remove this JBoss version of StandardService class sitting in the tomcat module. http://jira.jboss.com/jira/browse/JBAS-4263 There are two options possible. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032558#4032558 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032558

17 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Removal policies

by genman

Talking with some fellow devs, I'd like to have the eviction policies really handle removes not just evicts. One use case is: 1. I am only allowed to fetch a user's profile once every 4 hours. 2. I must remove this profile after 4 hours. 3. This data needs to be persisted. I know it is somewhat stretching the meaning of eviction, but there are no "removal policies" available. Is this something that's been given consideration? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032540#4032540 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032540

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: JACC Policy Bean not getting injected into EJBModule

by anil.saldhana＠jboss.com

Is there an equivalent of: | Set<DeploymentContext> children = unit.getDeploymentContext().getChildren(); | Something like: | Set<DeploymentUnit> children = unit.getChildren(); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032534#4032534 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032534

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: What do we need in terms of x509 cert processing for ws

by anil.saldhana＠jboss.com

Since PKI etc have been broached on this thread, I also want to provide a link to the following lgpl oss project that users may find useful: http://www.strongkey.org View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032533#4032533 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032533

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: JACC Policy Bean not getting injected into EJBModule

by anil.saldhana＠jboss.com

It probably is. Also, we need to adapt the deploy method of AbstractWebDeployer to use the updated API for DeploymentUnit ie. unit.getParent() and unit.getSimpleName(). This will remove the usage of DeploymentContext. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032480#4032480 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032480

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: JACC Policy Bean not getting injected into EJBModule

by scott.stark＠jboss.org

Ok, I don't know then unless its another symptom of the http://jira.jboss.com/jira/browse/JBMICROCONT-159 issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032479#4032479 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032479

17 years, 3 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-dev-forums March 2007