Bill Burke wrote:
Carlo de Wolf wrote:
> I think we can say that the entire scope of JBoss Embedded is too
> large to handle right now.
To put it bluntly: This is a bunch of crap. Either do it right or
don't do it at all. There's no point doing it at all if you're not
going to solve user's needs. You'll just be wasting engineering
resources.
Horse shit. That way we wouldn't be able to make any small increase
in
progress. We shouldn't be making progress onto a dead-end path, *that*
would be wasting engineering resources.
>
> The tricky bit will be assigning the proper properties to the proper
> component while trying to maintain it backwards compatible with what
> we have right now.
>
What I think you need to do is map out *exactly* how you think users
are going to use Embedded. Go through a couple of iterations of it on
this list. I know a few customers that would love to participate in
this discussion. (Cisco). After you flush it out, Implement it.
*THEN* figure out how to refactor it so it fits in the grand scheme of
things. You're doing it backwards.
The requirements for Embedded in EAP have been discussed on lists and
calls. If the community wants to add scenarios for Embedded they are
free to do so.
Carlo