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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Initial cut of MC integration work

by ataylor

The MC Integration is now at a point where it can be run both inside JBoss and embedded/standalone. Check out Branch_MC_Integration_New. to run inside jboss just set JBOSS_HOME and run 'ant deploy' you'll have to make sure to remove JBM 1.4 first. to run embedded/standalone run the command 'ant embedded'. This will create a new directory in output/embedded. cd into this directory and run './run.sh local'. This will run JBM inside its own vm via the class org.jboss.jms.server.microcontainer.JBMBootstrapServer. you'll see that ive added a test () method that produces and consumes some messages. At the minute theres no API for creating client connections, i'll add these once some of the other refactoring is complete. Theres also a remote config that uses the Jboss naming Server to show how you can plug in your own. To run this you'll need to copy the jar jnpserver.jar from the jboss 5 installation into the lib dir and run './run.sh remote'. In this configuration you'll be able to run any current JBM client, such as the examples. Theres still some stuff missing but I'm going to concentrate on getting the tests working so i can get this into the trunk. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105501#4105501 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105501

18 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Testing the wireformat

by timfox

I should probably clarify myself here and draw a distinction between "mock objects" and "fake objects". Mock object = typically very lighweight throwaway object whose implementation may be written for a single test. Typically it does stuff like assert correct values are passed in etc. Fake object = A fake implementation of the interface or interfaces that typically can be re-used by many different tests. E.g. we could create a "fake group management layer" which takes the place of JGroups and allows us to test distributed destinations quickly and in vm. Or a fake database which just stores data in a map in memory - enough to run tests against. Or a fake MINA which just forwards request/responses from client to server calling the correct objects at the correct times. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105485#4105485 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105485

18 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Enabling Message counters by default

by openllg

Sorry, it was not the good forum !! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105438#4105438 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105438

18 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Nested property ref

by adrian＠jboss.org

"trustin" wrote : +1. We don't vote on code/changes at JBoss. Changes are made based on merit and reason arguments rather than plebiscites. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105421#4105421 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105421

18 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Nested property ref

by adrian＠jboss.org

"alesj" wrote : Extending Trustin's user question to dev forum: | - http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105341 | | Supporting 2nd example is trivial, just a simple recursion on the property lookup in AbstractDependencyValueMetaData. | | I guess we could support the 1st one in a similar way as we did value-factory. | Perhaps we can even extend existing value-factory notion to do that? You can support both very easily. The "." cannot be part of java property name, so would be legal to include in property names for both examples without breaking existing configurations. The first one looks a bit hacky to me. You only recurse until the second to last property using getters to locate the object then use the setter for the last property. The other part is that you have to take into null return from the getters (an error) and the BeanInfo for the object retrieved from the getter has to be retrieved at each step. The first example can actually be done already with a factory configuration. | <bean name="TopLevel" .../> | | <bean name="Configuration" ...> | <constructor><factory bean="TopLevel' method="getConfiguration"/></constructor> | <property name="nested">sdfkjsdf</property> | </bean> | But that's a bit long winded compared to. ;-) | <bean name="TopLevel" ...> | <property name="configuration.nested">sdfkjsdf</property> | </bean> | P.S. You should also add the first example to the plain javabean xml. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105418#4105418 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105418

18 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Nested property ref

by trustin

+1. I'm not 100% sure how often people will face the first use case, but I already had an issue related with it. In Apache MINA, a user is not allowed to create a configuration object but only get the current configuration and set its properties (e.g. service.getConfig().setReadBufferSize(1024)) The reason we don't allow a user to create a configuration object is because its default values differ between a server-side application and a client-side application and we don't want users to spend their time to specify it's a server side configuration or a client side configuration, which is often error-prone and leads to unnecessarily crowded mailing list. :) So, I think this kind of case, that an API provider wants to restrict the creation of a certain object but the provider is fine with the modification of its properties, will happen pretty often. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105394#4105394 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105394

18 years, 4 months

1
0
0 / 0

[Design of Management Features on JBoss] - Re: Using xinclude in config files

by adrian＠jboss.org

"snacker" wrote : | I replaced the xerces*.jar, xml-api.jar and xalan.jar in jboss/lib/endorsed with the most recent version () | http://www.apache.org/dist/xerces/j/Xerces-J-bin.2.9.1.zip | | Still didn't work. | | Perhaps I need to use a more recent version of JBOSS??? | No, you need to set the system property (or ask on the Xerces mailing list if it doesn't work). http://xerces.apache.org/xerces2-j/faq-xni.html Only JBossXB enables Xinclude by default, and only then in the most recent versions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105389#4105389 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105389

18 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Metamodel and collections

by wolfc

Deeper into the empty collections we can have silly mergers: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas?view=rev&revision=67166 Somewhere the empty collection should not have been created in the first place. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105384#4105384 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105384

18 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Nested property ref

by alesj

Extending Trustin's user question to dev forum: - http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105341 Supporting 2nd example is trivial, just a simple recursion on the property lookup in AbstractDependencyValueMetaData. I guess we could support the 1st one in a similar way as we did value-factory. Perhaps we can even extend existing value-factory notion to do that? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105349#4105349 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105349

18 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JSR224

by heiko.braun＠jboss.com

JBossWS doesn't implement the JAX-WS 2.1 specs. Especially these bits have been removed just recently. They did pop up in the API but have not been implemented. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105340#4105340 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105340

18 years, 4 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 November 2007