On Mon, May 12, 2008 at 9:50 PM, Jean-Sebastien Delfino < [EMAIL PROTECTED]> wrote:
> ant elder wrote: > > > On Sun, May 11, 2008 at 7:38 PM, Jean-Sebastien Delfino < > > [EMAIL PROTECTED]> wrote: > > > > ant elder wrote: > > > > > > I may not have been very clear in the first email and also left out > > > > the > > > > link > > > > - it is just a single file that doesn't drag in any additional > > > > dependencies > > > > - > > > > > > > > > > > > https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/host-webapp/src/main/resources/META-INF/sca.tld > > > > > > > > Is a whole new module really necessary? > > > > > > > > ...ant > > > > > > > > > > > > IMO a new module is necessary, the taglib is from a different spec, > > > for a > > > different usage scenario. > > > > > > -- > > > Jean-Sebastien > > > > > > > > What we'd be saying is if you're developing SCA applications - JSPs, > > Servlets, POJOs whatever - you need the tuscany-sca-api jar on your > > classpath. Why is this a "different usage scenario"? > > > > Developing a J2SE client and developing a Web app are different scenarios. > > > > Right now this is just a single file so an entire module really does > > seem to > > unnecessarily complicate things. When we implement more of the JEE spec > > and > > it turns out that there are more API files then maybe i'd agree but > > would it > > be so bad untill then to put this in the tuscany-sca-api module? > > > > ...ant > > > > > I think I gave you my opinion. I don't think it's right to mix different > specs in the same JAR. > > -- > Jean-Sebastien Guess this has hit the eternal "lots of individual jars" versus "fewer jars with combined function" wall. I'll just leave the taglib where it is for the time being. ...ant
