On Tue, Jun 10, 2008 at 6:52 PM, Raymond Feng <[EMAIL PROTECTED]> wrote:
> Hi, > > Please see my comments inline. > > Thanks, > Raymond > > [snip] > >> Good requirement, but I don't think that the current manifest + >> tuscany-all JAR solution is a good one (for example it mixes APIs and >> internals in the same JAR, doesn't work well with IDEs, works only for one >> big distro, requires different settings in J2SE and webapps) >> >> > IMHO, the all-in-one package pretty much defeats our modularity. For > example, all module activators will be called even the extension won't be > used at all. Calling a module activator is pretty minimal initialization overhead especially if it just fails right away with something like a ClassNotFoundException and the runtime carries on, and this is what happens with the our bundle jar - you can just use it without the extension dependencies you don't need and it works fine. Note I'm not necessarily saying we should be keeping the single one big bundle jar, i'm just trying to avoid the impression that the _only_ option we have is everything in individual separate jars. > Two extension cannot have different versions of a 3rd party jar. > > Here's what I'd like to see as a user: >> >> - a short list of API JARs that I can add to my dev compile/build path >> >> - a single small launcher or bootstrap JAR that takes care of >> bootstrapping the Tuscany runtime >> >> > This is similar to JEE launchClient. If I can invoke the Launcher directly > in java, I would be happy. > So just to be clear on what is being suggested this would be like the launcher we used to have back in M2 days right? ...ant
