May 2008 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: A few problems running the examples on different machine

by timfox

"ataylor" wrote : Of course if we wanted we could implement our own simple naming service using Mina. We only have to handle destinations and connection factories. This would remove the dependency! | | Would we really need that? JBM is fully functional without any need for JNDI - since connection factories and destinations can be instantiated directly on the client side. The only reason we really need JNDI is for JMS spec which mentions that JMS objects should be available in JNDI. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150241#4150241 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150241

17 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: A few problems running the examples on different machine

by timfox

"ataylor" wrote : ok, so it turns out that even tho the initial connection to jndi was happening the exported stub that was being returned still had an endpoint of localhost. This is because if the property java.rmi.server.hostname is not set it defaults to localhost, when the App Server starts up, setting this property is one of the first things it does. | | Ive changed the jbm-standalone-beans.xml to inject the host property from the configuration object so that we only need to configure it in one place. The configuration property also sets the java.rmi.server.hostname property when the host is set. Nice catch. Sounds like a nasty one to track down. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150238#4150238 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150238

17 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Proxy Tasks for Delegation

by ALRubinger

5) Set up a code coverage M2 Plugin (Where is this being done already?) S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150235#4150235 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150235

17 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Proxy Tasks for Delegation

by ALRubinger

4) Add tests to ProxyFactoryRegistryUnitTestCaseBase that check to ensure that: * ProxyFactory.start() is called upon ProxyFactoryRegistry.registerProxyFactory() * ProxyFactory.stop() is called upon ProxyFactoryRegistry.deegisterProxyFactory() S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150234#4150234 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150234

17 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - Proxy Unit Tasks for Delegation

by ALRubinger

I've committed the first round of development for EJB3 Proxy. Anyone with spare cycles (I believe Carlo volunteered himself) who wants to look at the following is more than welcome; this will help speed along JNDI Name Conflicts preventing many tests from passing. 1) There are currently two test cases extending from a common base which contains all test logic. Each class tests an implementation of the ProxyFactoryRegistry, an object designed to keep track of / store Proxy Factories. The In-Memory tests are working; these are just backed by a HashMap. The JNDI tests are not; these require a backing JNDI Store. To fix, need standalone startup of the JNP Server (in a @BeforeClass method) and injection for the naming Context within the JndiProxyFactoryRegistry (I've placed comments in the code where this is appropriate). 2) How do we get at a Managed MC Object from an unmanaged one? The JNDI ObjectFactories are instanciated by our JNP Server upon each lookup, so I've no way to make these objects MC Beans on their own. Best I can think is to either do a lookup (but I have no reference to the Kernel/ControllerContext) or introduce an aspect to inject the MC Bean as an instance when the ctor is called. Specifically, I'm talking about McProxyObjectFactory. 3)The tests fail within the JUnit launcher for Eclipse, but this is a second-class citizen so long as all is kosher from the command line. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150231#4150231 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150231

17 years, 11 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: jboss-profiler-1.0.CR4 - Help needed

by clebert.suconic＠jboss.com

This happens because when you start the data capture process, you get the METHOD_EXIT before the METHOD_ENTER in some classes. This could be safely ignored. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150219#4150219 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150219

17 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - organization of the enterprise module

by alex.guizar＠jboss.com

While working on the jBPM 3 enterprise module I found several items that seem out of place. There are two entity-based implementations of the scheduler service, one in org.jbpm.scheduler.ejbtimer and the other in org.jbpm.ejb. The descriptor points to the former; the latter is probably the remains of an earlier refactoring. The EjbSchedulerService class, introduced in earlier 3.2.x versions, invokes the entity bean, whereas the new EntitySchedulerService class invokes the timer session bean. The command service interface, home interface and session bean are placed in the org.jbpm.ejb package, whereas the timer entity artifacts are located in org.jbpm.scheduler.ejbtimer. Any reason for this odd arrangement? If not, I want to rearrange as follows. Remove the timer entity in org.jbpm.ejb. Move the timer entity in org.jbpm.scheduler.ejbtimer to org.jbpm.ejb. For backwards compatibility, have EjbSchedulerService invoke the timer session bean. Have EntitySchedulerService invoke the timer entity bean, which better matches its name. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150216#4150216 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150216

17 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: AIO only waiting for completions on add

by clebert.suconic＠jboss.com

This should be fixed now. What I had before was an intermediary commit. It was working but it was still requiring some changes. And it is complete now. please, le me know If you still see anything wrong, as it would be a bug then. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150199#4150199 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150199

17 years, 11 months

1
0
0 / 0

[Design of JBoss ESB] - Re: 4.3 CR1 is available for download

by jarkko＠jab.fi

I didnt' go through these, so let me recheck the situtation ;) anonymous wrote : Settings required to edit before running: | | File: jbossesb-properties.xml (jbossesb.sar/jbossesb-properties.xml) | - Update the section titled "transports" and specify all of the SMTP mail server settings for your environment. | | File : deployment.properties (install/deployment.properties) | - Update the app server location settings. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150183#4150183 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150183

17 years, 11 months

1
0
0 / 0

[Design of JBoss ESB] - Re: 4.3 CR1 is available for download

by jarkko＠jab.fi

Running ant deploy from jbossesb-server-4.3.CR1/samples/trailblazer gives error and does not compute: jarkko@gandalf:~/ff/esb/4.3/jbossesb-server-4.3.CR1/samples/trailblazer$ ant deploy | Buildfile: build.xml | | messaging-config: | | messaging-dependencies: | | jbossmq-dependencies: | | esb.built: | | clean: | | trailblazer.prepare: | [mkdir] Created dir: /home/jarkko/ff/esb/4.3/jbossesb-server-4.3.CR1/samples/trailblazer/esb/build | [mkdir] Created dir: /home/jarkko/ff/esb/4.3/jbossesb-server-4.3.CR1/samples/trailblazer/esb/build/dist | [mkdir] Created dir: /home/jarkko/ff/esb/4.3/jbossesb-server-4.3.CR1/samples/trailblazer/esb/build/classes | [mkdir] Created dir: /home/jarkko/ff/esb/4.3/jbossesb-server-4.3.CR1/samples/trailblazer/client/build | [mkdir] Created dir: /home/jarkko/ff/esb/4.3/jbossesb-server-4.3.CR1/samples/trailblazer/client/build/dist | [mkdir] Created dir: /home/jarkko/ff/esb/4.3/jbossesb-server-4.3.CR1/samples/trailblazer/client/build/classes | | esb.compile: | [javac] Compiling 6 source files to /home/jarkko/ff/esb/4.3/jbossesb-server-4.3.CR1/samples/trailblazer/esb/build/classes | | BUILD FAILED | /home/jarkko/ff/esb/4.3/jbossesb-server-4.3.CR1/samples/trailblazer/build.xml:181: /home/jarkko/ff/esb/4.3/jbossesb-server-4.3.CR1/samples/trailblazer/${test.util.dir} not found. | | Total time: 0 seconds | jarkko@gandalf:~/ff/esb/4.3/jbossesb-server-4.3.CR1/samples/trailblazer$ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150182#4150182 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150182

17 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2008