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

[Design the new POJO MicroContainer] - Re: Java EE unified metadata prototype

by adrian＠jboss.org

"bill.burke(a)jboss.com" wrote : Instead of having a metadata bridge between these two projects, why not just merge the metamodels? That's what I did, they both use the same model. The bridge just means we don't have to go through all the old EJB2 classes, clustering classes, etc. and change them (potentially breaking them :-) But more importantly, these classes are required for any user that wrote their own interceptor for our EJB2 container. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063213#4063213 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063213

18 years, 9 months

1
0
0 / 0

[Design of JBoss Build System] - Re: jboss-head build testsuite action plan

by ryan.campbell＠jboss.com

For the moment, let's take cruisecontrol out of the equation as I would prefer we do this as a generic hudson plugin so that we can apply it generically for any project that chooses to go this route. That said, here is how it would roughly work (erring on the side of completeness): 1. CI system polls SVN every 15 minutes looking for changes 2. If changes are found, CI system polls SVN for additional 7 minutes to make sure the commits are complete. 3. CI system performs a clean build 4. If the build fails, rollback the commit by doing a reverse merge on the workspace using the last known good revision ID. 5. Commit this changeset to the repository. 6. Send out an email flaming the committers to the build. 7. GOTO 1 This is the algorithm as I understand it. Please confirm that I have it right before I tell you why I think its a bad idea. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063210#4063210 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063210

18 years, 9 months

1
0
0 / 0

[Design of JBoss ESB] - Re: JMSHeader fields

by mark.little＠jboss.com

"beve" wrote : Hi, | | I'm working on JIRA http://jira.jboss.com/jira/browse/JBESB-651 and would like to know how JMSHeader fields should be transported with a Message object in the ESB. | | I've identified the following JMSHeader fields that might be of interest. | | | JMSMessageID -> message.getHeader().getCall().getMessageID() | | JMSCorrelationID -> message.getHeader().getCall().getRelatesTo() ); | | | | Yes, that sounds right to me. Since we have the capability in the EPR, let's use that rather than stuff the information in the message body. anonymous wrote : | JMSReplyTo should propably be mapped to message.getHeader().getCall().getReplyTo() but I'm not sure how I should set/create the JMSEpr. Can anyone help me out? | What's the problem specifically? anonymous wrote : | I have another JIRA that is related to this one which is the JMSRouter. I've added the following method to this class: | | | protected void setJMSProperties( Message jmsMessage, org.jboss.soa.esb.message.Message esbMsg ) | | throws JMSException | | { | | jmsMessage.setJMSCorrelationID( esbMsg.getHeader().getCall().getRelatesTo().toString() ); | | } | | | Now this will set the out going JMS message correlationID to the JMSMessageID that has been carried along with the Message object. This is probably ok for most user but this will also let other that have different needs subclass JMSRouter and overrride this method. | | While writing unit test for this I noticted that the test JmsRouterUnitTest is trying to connect to a server, and if one is not running it will time out: | | | [java] [junit] Running org.jboss.soa.esb.actions.routing.JmsRouterUnitTest | | [java] [junit] Testsuite: org.jboss.soa.esb.actions.routing.JmsRouterUnitTest | | [java] [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 80.874 sec | | [java] [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 80.874 sec | | | Recactoring this junit test might speed up the build :) | | Thanks, | | Daniel It should probably be an integration test anyway. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063206#4063206 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063206

18 years, 9 months

1
0
0 / 0

[Design of JBoss Build System] - Re: jboss-head build testsuite action plan

by scott.stark＠jboss.org

The first change should be rolling back changes that break the build of the server or testsuite. What is required to do this with the current CC runs? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063202#4063202 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063202

18 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Java EE unified metadata prototype

by alex.loubyansky＠jboss.com

"bill.burke(a)jboss.com" wrote : Instead of having a metadata bridge between these two projects, why not just merge the metamodels? And have both containers use the same classes? If this is an option, I do suggest a new package name so that if Carlo and company need to backmerge something, they won't conflict with JBoss 4.2. You mean EJB2 and EJB3 use the same metadata classes? That's the goal, AFAIK. At least in JBoss5. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063200#4063200 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063200

18 years, 9 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Ordering of .ear subdeployments

by SailuRavi

After having module order to strict .. the modules are loading as specified in application.xml... Earlier I didn't have jboss-app.xml at all and thought that the default is in the order given in appliacation.xml but the default is implicit... <module-order>strict</module-order> did it. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063199#4063199 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063199

18 years, 9 months

1
0
0 / 0

[Design of JBoss Build System] - jboss-head build testsuite action plan

by scott.stark＠jboss.org

After a number of email on the need to lock down the jboss-head testsuite and introduce build breakage and testsuite failure consequences, there was no action plan. I'd like to get that finalized in this thread. No whining please, just posts that move toward the goal. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063197#4063197 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063197

18 years, 9 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBAS-4276 Discussion Thread

by bstansberry＠jboss.com

Let's throw an exception and strip out any code that tries to do a lookup. If the partition isn't available, that means Brian screwed up when he wrote and tested the config file. :) In general, I want to go with a straight IOC approach -- services assume they have dependencies injected, and don't try looking them up themselves. If the necessary dependencies aren't available, throw an IllegalStateException (let's avoid any NPE). AIUI, this business of looking stuff up predates the days when the JMX Microkernel could do dependency injection via "depends optional-attribute name". I would have torn it out when I added the "ClusterPartition" attribute, but that was too big a change for a 4.0 point release. We may need to be a bit more cautious/think about it a wee bit more in the case of things like HAServiceMBeanSupport, where it's expected users will subclass the class. But for internal services like HASessionState, be ruthless. :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063156#4063156 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063156

18 years, 9 months

1
0
0 / 0

[Design of JBoss ESB] - JMSHeader fields

by beve

Hi, I'm working on JIRA http://jira.jboss.com/jira/browse/JBESB-651 and would like to know how JMSHeader fields should be transported with a Message object in the ESB. I've identified the following JMSHeader fields that might be of interest. | JMSMessageID -> message.getHeader().getCall().getMessageID() | JMSCorrelationID -> message.getHeader().getCall().getRelatesTo() ); | | JMSReplyTo should propably be mapped to message.getHeader().getCall().getReplyTo() but I'm not sure how I should set/create the JMSEpr. Can anyone help me out? | | I have another JIRA that is related to this one which is the JMSRouter. I've added the following method to this class: | | | protected void setJMSProperties( Message jmsMessage, org.jboss.soa.esb.message.Message esbMsg ) | | throws JMSException | | { | | jmsMessage.setJMSCorrelationID( esbMsg.getHeader().getCall().getRelatesTo().toString() ); | | } | | | Now this will set the out going JMS message correlationID to the JMSMessageID that has been carried along with the Message object. This is probably ok for most user but this will also let other that have different needs subclass JMSRouter and overrride this method. | | While writing unit test for this I noticted that the test JmsRouterUnitTest is trying to connect to a server, and if one is not running it will time out: | | | [java] [junit] Running org.jboss.soa.esb.actions.routing.JmsRouterUnitTest | | [java] [junit] Testsuite: org.jboss.soa.esb.actions.routing.JmsRouterUnitTest | | [java] [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 80.874 sec | | [java] [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 80.874 sec | | | Recactoring this junit test might speed up the build :) | | Thanks, | | Daniel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063150#4063150 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063150

18 years, 9 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBAS-4276 Discussion Thread

by JerryGauth

A question on the SessionStateService - Currently this service instantiates HASessionStateImpl when the service is created. If the partition hasn't been injected, the service just uses the partition name when constructing HASessionStateImpl. The constructor then uses the partition name to ultimately lookup the partition via JNDI. If the partition name is missing, the constructor uses the default JNDI name for the partition. For other services that inject the partition, we throw an exception in the start() method if the partition is null. In this service, we no longer have a partition name if the service hasn't been injected. However we can still pass a null partition name to HASessionStateImpl which will trigger an attempt to perform the default name lookup. I can leave HASessionStateImpl as is so that it will still attempt to use the default name in a JNDI lookup. Alternatively I can throw an exception in HASessionStateService.create() if the partition hasn't been injected. Any thoughts on what's preferable here? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063142#4063142 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063142

18 years, 9 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 July 2007