[Design of JBoss ESB] - Re: Trailblazer out-of-the-box experience
by mark.little@jboss.com
"kurt.stam(a)jboss.com" wrote : (i) This can be best accomplished by introducing a 'deployTrailblazer' task. :)
|
Sounds just about perfect. Let me guess, something like
| <target name="deployTrailblazer"
| depends="configure, deploy"/>
|
;-)
anonymous wrote :
| (ii) We should get rid of the ant wizzard all together and just have one loanbroker.properties file (we check in an -example) just like we do for the esb itself.
|
That sounds good too. We already tell people they have to edit the loanbroker.properties-template file anyway.
anonymous wrote :
| There is nothing better then simplicity. We could annotate this file with info on where this parameter is going to be used. Just so that it becomes easier to check up on yourself. (Currently the ant wizzard still has problems with slashes, spaces and it doesn't keep track of your previously given answers)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976563#3976563
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976563
19 years, 6 months
[Design of JBoss ESB] - Trailblazer out-of-the-box experience
by mark.little@jboss.com
The machine I was building the TB on had a disk failure last night, so I've been trying to set this up from scratch on Mac OS X. Not something I've had to do in a while. I'd forgotten how many steps you have to go through. Some observations:
(i) we should have a single rule for configuring and running the demo. Multiple rules are fine for the user who wants to go through each step at a time, but I think the 80/20 rule needs to apply here.
(ii) the configuration step should cache the answers from each run and echo them back if you want to re-run. That way you don't have to answer all of the same set of questions again if only one thing needs changing. Where I've used this approach before you see the default answer in [], so for example:
[input] Enter the path to the root of your local JBoss Application Server Installation (required for access to JBoss libraries):
would be
[input] Enter the path to the root of your local JBoss Application Server Installation (required for access to JBoss libraries): [/usr/local/jboss-4.0.4]
and
[input] Enter the host address of the JBoss Application Server on which your deployed JBoss ESB is running (for "localhost" simply press return):
would be
[input] Enter the host address of the JBoss Application Server on which your deployed JBoss ESB is running: [25]
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976549#3976549
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976549
19 years, 6 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Application Server Integration Tests
by rachmatowicz@jboss.com
I hope to present a detailed picture of my understanding of what you want tomorrow (Friday) which we can use to move forward.
One question though: from what I have read, the microcontainer (MC) has limitations, in particular that remote communication is not supported at present. I assume this means that, say, in a test case based on MicrocontainerTestCase, that the JMS provider, deployed destinations, and test case itself all have to reside in the same VM. (Please correct me if i'm mistaken).
So running test cases using the MC, despite this limitation, makes sense when we are outside the AS, as there is no alternative.
However, what if JMX (which supports remote communication) is available?. You mentioned in an earlier posting that tests should be written against the MC. Does this mean that you want to run these generic JMS tests against the MC, even when the AS is available? That is, in the AS test suite, to run all JMS tests (whether against the JBossMQ provider or Messaging preovider) by deploying these providers to the MC and not JMX?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976447#3976447
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976447
19 years, 6 months