April 2009 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Temporary queue not conform to JMS spec

by gaohoward

np View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223029#4223029 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223029

16 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Temporary queue not conform to JMS spec

by timfox

Good catch. Can you log a JIRA and we'll deal with it after beta? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223028#4223028 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223028

16 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: JAXB Deployer

by alesj

Not yet, see my last jboss-dev email on why not. ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223026#4223026 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223026

16 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Temporary queue not conform to JMS spec

by gaohoward

JMS 1.1 spec Section 4.4.3 2nd paragraph: anonymous wrote : Temporary destinations (TemporaryQueue or TemporaryTopic objects) are | destinations that are system-generated uniquely for their connection. Only | their own connection is allowed to create MessageConsumers for them. | I think this means the following test should fail as it tries to create a consumer on the temp queue from a different connection than the one that owns the temp queue. But it passes. | public void testTemporaryQueueScope() | { | try | { | // we stop both sender and receiver connections | senderConnection.stop(); | receiverConnection.stop(); | // we create a temporary queue to receive messages | tempQueue = receiverSession.createTemporaryQueue(); | // we recreate the sender because it has been | // already created with a Destination as parameter | senderSession.createConsumer(tempQueue); | } | catch (JMSException e) | { | fail(e); | } | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223025#4223025 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223025

16 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: JAXB Deployer

by anil.saldhana＠jboss.com

"alesj" wrote : "anil.saldhana(a)jboss.com" wrote : http://anonsvn.jboss.org/repos/jbossas/branches/Branch_5_x/security/src/m... | | Maybe the JAXBElementDeployer should go into deployers? | I see no need, as I've fixed JAXBDeployer to handle enclosed differently. Is AS5x/6 updated with your changes? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223023#4223023 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223023

16 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Context installation causes StackOverflowError

by alesj

Solution to the _real_ problem: - http://lists.jboss.org/pipermail/jboss-development/2009-April/013940.html View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223020#4223020 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223020

16 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: Annotation for MC bean

by galder.zamarreno＠jboss.com

"bstansberry(a)jboss.com" wrote : There may not be one anywhere. I don't think @Jndi actually works. (Not that the code doesn't work if the lifecycle-xxx declaration is there; just that applying the annotation doesn't currently do anything.) @Jndi does not work but @JndiBinding does, see https://jira.jboss.org/jira/browse/JBAS-6502. To make sure this is clear, annotating a bean with @JndiBinding serializes the bean and puts it in the JNDI, it doesn't provide any remote access to the bean itself or anything similar :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223000#4223000 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223000

16 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: separate take task method

by kukeltje

Yep, It was (is) in my 'process access object' View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222992#4222992 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222992

16 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - GSoC proposal: Process instance migration in JBPM

by tom.baeyens＠jboss.com

For this proposal, I think the following timeline is achievable: Milestone 1 (approx 7 days): Get overview of the jBPM codebase and learn the build system. Milestone 2 (approx 12 days): Work out the simplest possible example and discuss the proposed solution. Starting points: add a property to the deployment (probably as an attribute in the process definition). Add process instance migration code to the JpdlDeployer. Milestone 3 (approx 7 days): Add a translation map in case activity names have changed. Define how this mapping information will be part of a deployment. Milestone 4 (approx 15 days): Analyse exact constraints for migrating process instances over to a changed process definition. What kind of changes can be handled. And what kind of changes cannot be handled. Add those constraints to the process instance migration. Milestone 5 (approx 15 days): Develop a testing strategy for process instance migrations. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222989#4222989 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222989

16 years, 8 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: JBIDE-3394, hot deployment management api

by dimitris＠jboss.org

Sorry to resurrect this, I was meant to post on the topic couple of weeks ago, but forgot to. With the work in https://jira.jboss.org/jira/browse/JBAS-6330 I believe we can emulate the 4.x deployment API in 5. If this API uses mostly basic java types (javax.management, String, etc.) then the library dependency issue comes down to the remoting layer. Can we not just use the standard JMX rmi connector that comes with JDK5+? E.g. I can point jconsole to a running AS instance and access the mbeans, as long as I stick to standard java types: jconsole service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222988#4222988 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222988

16 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2009