dev@glassfish.java.net

Re: Problems running trunk on Glassfish

From: Henry Story <henry.story_at_bblfish.net>
Date: Thu, 19 Oct 2006 18:15:47 +0200

Ok, I have re-installed to the latest trunk of roller

hjs_at_bblfish:0$ svn infoPath: .
URL: https://svn.apache.org/repos/asf/incubator/roller/trunk
Repository Root: https://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 465608
Node Kind: directory
Schedule: normal
Last Changed Author: snoopdave
Last Changed Rev: 465605
Last Changed Date: 2006-10-19 14:29:47 +0200 (Thu, 19 Oct 2006)
Properties Last Updated: 2006-09-28 14:53:16 +0200 (Thu, 28 Sep 2006)


This again works with Tomcat but not with Glassfish Edition 9.1
(build b19)

It looks like the tld is in a different place:

hjs_at_bblfish:0$ jar tvf roller.war | grep roller.tld
10789 Thu Oct 19 11:48:48 CEST 2006 WEB-INF/classes/META-INF/tlds/
roller.tld

You were expecting it to be in the rollerweb.jar

Henry


On 19 Oct 2006, at 10:56, Henry Story wrote:

> On 19 Oct 2006, at 06:29, Jan Luehe wrote:
>
>>
>> Hmm, this is weird.
>>
>> The taglib with this URI:
>>
>> "http://www.rollerweblogger.org/tags"
>>
>> is defined in rollerweb.jar's META-INF/tlds/roller.tld, and
>> rollerweb.jar is bundled
>> in roller.war's WEB-INF/lib, so the taglib really should be found.
>
> Ah that could be it. There is no META-INF/tlds/roller.tld in the
> rollerweb.jar that I have.
> in revision 453532 of the roller trunk svn repository.
>
>> I'm wondering why the exception message has a space in front of
>> "tags" in
>>
>> "http://www.rollerweblogger.org/ tags",
>
> No, that's a stupid bug with Apple Mail.app that I have reported a
> few years back and that looks like it will never get fixed.
> Mail.app cuts up urls, when they cross a line.
>
> Henry
>
>>
>> when the taglib's URI as defined in the TLD does not have any such
>> space:
>>
>> "http://www.rollerweblogger.org/tags"
>>
>> This mismatch in the imported and declared URIs could explain why
>> the taglib
>> is not found.
>>
>> Do you see any other exceptions in the server.log?
>>