Proposed JBESB Configuration File Schema (JBESB-119)

[ddegroff]

Work has begun on establishing schema for the JBESB application configuration file. What has occurred to this point is to create proposed configuration files based on both TestJBossESB and trailblazer. The schema to validate the configuration file was created also.

More details of the approach may be found in the file "aREADME" attached to JBESB-119, along with the sample configuration files and proposed schema.

Any/all comments/suggestions/concerns are welcome prior to laying code to support PropertyManager in GpListener.

Thanks, Dave DeGroff

[daniel.brum]

Dave, have you looked at the property manager Mark checked in? It might be useful in this scenario, and would allow for one common way of setting ESB config and application config values, all using the same manager.

[marklittle]

Daniel, did you check http://jira.jboss.com/jira/browse/JBESB-122 and http://jira.jboss.com/jira/browse/JBESB-119?

;-)

[tfennelly]

Hey Dave, I had a look at that there. Looking at the LoanBrokerConfig, I personally would find that format a bit difficult to follow. While it's XML, it's a very flat structure. I'd find it more difficult to read and navigate than I'd expect.

[marklittle]

Dave, could you post a "before" and "after" example here, so we can discuss?

[ddegroff]

Hey Dave, I had a look at that there. Looking at the LoanBrokerConfig, I personally would find that format a bit difficult to follow. While it's XML, it's a very flat structure. I'd find it more difficult to read and navigate than I'd expect.

Not only do I not discount Tom's remark, I tend to agree. I've a bit of an emergent situation at work, but once that crisis abates, I'm on this. First, a revision to my proposed configuration XML (concentrating on LoanBrokerConfig).

Tom: Would you prefer my communicating direct, or through this thread?

Thanks, Dave

[ddegroff]

Was posting while Mark was posting... Will do.

Dave

[ddegroff]

Proposed Revision to Configuration XML.

Before:
www.ehealthconnect.net/ehc/LoanBrokerConfigBefore.xml

After:
www.ehealthconnect.net/ehc/LoanBrokerConfigAfter.xml

[marklittle]

"ddegroff" wrote:

Hey Dave, I had a look at that there. Looking at the LoanBrokerConfig, I personally would find that format a bit difficult to follow. While it's XML, it's a very flat structure. I'd find it more difficult to read and navigate than I'd expect.

Not only do I not discount Tom's remark, I tend to agree. I've a bit of an emergent situation at work, but once that crisis abates, I'm on this. First, a revision to my proposed configuration XML (concentrating on LoanBrokerConfig).

Tom: Would you prefer my communicating direct, or through this thread?

Thanks, Dave

Let's keep the discussion here. More chance of additional feedback.

[tfennelly]

"ddegroff" wrote:
Proposed Revision to Configuration XML.

Before:
www.ehealthconnect.net/ehc/LoanBrokerConfigBefore.xml

After:
www.ehealthconnect.net/ehc/LoanBrokerConfigAfter.xml

www.ehealthconnect.net/ehc/LoanBrokerConfigBefore.xml

www.ehealthconnect.net/ehc/LoanBrokerConfigAfter.xml

[marklittle]

I think the forum has screwed with the URLs.

[tfennelly]

BTW: I don't really know what the value of a before/after comparison is since there's prob not a huge fan base for the before config anyway. Should we not simply judge it on it's own merits?

[marklittle]

The comparison is to show what we currently have and why it may be problematical and then show what the proposal is. Pros and cons of the proposal need to be weighed against the current approach, which is the baseline.

[tfennelly]

I think the forum has screwed with the URLs.

Looks as though many of those BB Code features have been disabled for some reason - most anoyingly the fact that you can't edit yer own posts.

I think they forgot to disable the "Preview" feature ;-) Ups, I probably shouldn't have said that!

[marklittle]

Stepping back a moment: what's the estimate of time and effort to change the current configuration approach used by GpListener and friends? Time is of the essence here, so something very invasive may not be the best approach until after the RC.