Yes, I could work around part of the problem spelling out absolute
pathes for assets. However, the template could still not be found for
templated components, even if it was in the very same package/directory.
Marcus 

> -----Original Message-----
> From: Steve Shucker [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, April 04, 2007 7:43 PM
> To: Tapestry users
> Subject: Re: .jwc-file-free components for libraries (4.1.1)
> 
> My recent experience (with 4.1.1) is that injecting relative 
> resources isn't working.  I have a few components in a 
> library with associated *.script files.  Some have templates 
> and use the @Script tag in the template.  Others don't have 
> templates and use the @InjectScript annotation.  I tried to 
> put all the script files in the same directory and found that 
> the paths in the annotation couldn't be resolved.  I'd get an 
> error message with the correct classpath, but it said the 
> script file wasn't there.  If I put the *.script files in the 
> same directory as the class, they'd work fine.  I don't know 
> if the problem was because I was using parent paths or any 
> directory would have broken it.
> 
> -Steve
> 
> Jesse Kuhnert wrote:
> > I do remember being annoyed by this lately, if you file a 
> jira issue 
> > for it I'll fix it quickly.
> >
> > On 4/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >> We are trying to move a little library of ours to Java-5 with full 
> >> usage of annotations, without jwc-files. While a component 
> itself is 
> >> recognised this way. Asset-resolution relative to the 
> (non-existing) 
> >> specification doesn't work.
> >> Did I overlook anything? Or would that be an 
> improvement-issue in Jira?
> >>
> >> regards,
> >> Marcus
> >>
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to