I don't understand.
What dependency do I need to break out? I don't touch HTTP code, I don't care about HTTP code.
My only dependency is Remoting and I only have a piece of configuration that says "bisocket" or "http". Remoting can implement HTTP using smoke signals, for what I care.
IF we start to get into this, maybe it's time to ditch remoting and start thinking about our own transport.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022692#4022692
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022692
"weston.price(a)jboss.com" wrote :
| 2) Eliminate the problematic elements from the *-ds.xml deployment (ie MBean definitions) that get in the way of making the unmarshalling a simple process, or at least find someway to work around this.
|
| This was actually my initial approach but the MBean definitions inside the *-ds.xml got in my way.
|
Ok, but at that point you have a new an incompatible ds.xml descriptor. What I'm talking about is morphing the legacy ds.xml into ds2.xml that is a perfectly parsable, aspect oriented delight. Its whatever the lesser of two evils is, an essentially hand-coded xml parse/deserializer or xsl.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022689#4022689
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022689
Ronald,
I'm not sure how much of this was in response to my earlier note of today (see third post in http://www.jboss.com/index.html?module=bb&op=viewtopic&t=100746)
My main concern wasn't about not having a way to provide input into triage.
My problem is that Jira is currently nearly useless as a way to understand what the current short-term roadmap is.
With 32 outstanding issues and release scheduled for a week ago, I know that Jira is nowhere near the truth. But has no one made any progress on those issues, or are they just not keeping Jira up to date? I'm sure that the truth is some mix of these two things, but what's the ratio?
Folks who have deadlines in the next several months need to know what they can expect, from which they can determine what they'll need to develop on their own.
-Ed Staub
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022629#4022629
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022629
I would like to get away from using XSL at all (the original point of the task). The approach you mention could work, but if I was going to go down that route, I would be more inclinded to
1) Create a MCF XSD and deprecate the DTD
2) Eliminate the problematic elements from the *-ds.xml deployment (ie MBean definitions) that get in the way of making the unmarshalling a simple process, or at least find someway to work around this.
This was actually my initial approach but the MBean definitions inside the *-ds.xml got in my way.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022626#4022626
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022626