Simon Groenewolt <[EMAIL PROTECTED]> wrote: > > > >That makes no sense. There should be only one jar with taglibcontent.xml: > >mmbase-taglib.jar. > > I am not arguing whether it makes sense or not, just that the situation > as described above currently is possible, and will lead to confusion. > (Or at least it did in my situation)
Yes, i think it is only logical that this didn't work. How excactly did it end up there? Perhaps the simply 'application' framework currenly in use in applicatins module does not really allow for stuff in WEB-INF/classes? > You can seal packages by creating/editing your own manifest file, and > you can supply the jar tag in ant with a manifest tag to indicate which > one to use. > http://java.sun.com/docs/books/tutorial/jar/basics/manifest.html#sealing > > However, if you use this option it also _might_ no longer be possible to > put the taglibcontent file in the classes directory without removing it > from the jar, I did a quick search on this one but I didn't find the > answer yet. Also I am not really sure if all ClassLoaders will > automatically enforce checks on sealing or that it is optional. Yes, I figured that too, so perhaps we should say that it is not even worth the try. Michiel -- Michiel Meeuwissen | Mediapark C101 Hilversum | +31 (0)35 6772979 | I hate Internet nl_NL eo_XX en_US | mihxil' | [] () |
