So far as I know, I haven't touched the asset service on my project.
I tried moving the HtmlArea.jar around a bit:
Tomcat/shared/lib -> no errors, results as per previous email
Tomcat/common/lib -> nasty classloader errors, app won't start
I'm fairly stumped at this point, especially by the lack of any kind
of error message. If I was getting some sort of a "cannot find asset
foo/bar" I'd at least be able to work with it, but so far, no dice.
I'm going to ask a stupid question now though:
Do I have to do anything to enable Tapestry's script engine? E.g. do
I have to throw a flag in my border component and/or add a tapestry <script>
component high up on the page to give this .jwc a spot to write its
javascript into? I never really followed the scripting chapter in Howard's
book (I got about ten pages in and said the hell with it I'll write my own),
so I might be missing something utterly fundamental here :).
--- Pat
> -----Original Message-----
> From: Robert Zeigler [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 26, 2005 12:47 PM
> To: Tapestry users
> Subject: Re: HtmlArea help
>
> One thing I would try first off is setting your rows to something larger
> than 8... htmlarea is a little weird that way. Even so, that shouldn't
> be the problem with the degradation. I'm using HtmlArea many places in
> 3.0.3 with no issues, so... not sure what the deal is.
>
> But if the scripts aren't being referenced in your page, that would
> explain the lack of an htmlarea. :) The issue, then, is why aren't the
> scripts being loaded... Are you doing anything... funny with the asset
> service?? That's the only thing I can really think of.
>
> Robert
>
> Patrick Casey wrote:
> > Well, there is no component file as I'm using declarative binding
> > e.g.
> >
> > <span jwcid="@htmlarea:HtmlArea" value="ognl:object.instructions"
> rows="8"
> > cols="80"/>
> >
> > Is the only reference to the htmlarea on one of my pages.
> >
> > I'm suspicious that what's happening is that the component is
> > supposed to link in two scripts e.g. the HtmlArea.html code looks like:
> >
> > <script jwcid="definitions"/>
> > <textarea jwcid="theArea" id="ognl:components.theArea.name"/>
> > <script jwcid="theScript"/>
> >
> > While the HtmlArea.jwc code defines definitions and theScript thus:
> >
> > <component id="theScript" type="Script">
> > <static-binding name="script">HtmlArea.script</static-binding>
> > <binding name="fullpage" expression="fullPage"/>
> > <binding name="table" expression="tableOperations"/>
> > <binding name="context" expression="contextMenu"/>
> > <binding name="spelling" expression="spellChecker"/>
> > <binding name="id" expression="generateId()"/>
> > <static-binding name="included"
> > value="?service=HtmlAreaResourceLoader&sp=Shtmlarea.js"/>
> > </component>
> >
> > <component id="definitions" type="Script">
> > <static-binding
> > name="script">HtmlAreaDefinitions.script</static-binding>
> > <static-binding name="url"
> > value="?service=HtmlAreaResourceLoader&sp=S"/>
> > </component>
> >
> > The problem is I'm not seeing either of these scripts show up in my
> > page at all. I've actually seen this problem with other libraries I've
> > downloaded off of Tassel or Tacos e.g. the scripts never seem to load
> and I
> > have to manually load them e.g. put my own <any> tags in to link the
> scripts
> > from physical storage instead of the jar.
> >
> > Is there any kind of known "gotcha" that would prevent the component
> > loading its scripts from its own .jar?
> >
> > --- Pat
> >
> >
> >
> >>-----Original Message-----
> >>From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
> >>Sent: Friday, August 26, 2005 10:32 AM
> >>To: Tapestry users
> >>Subject: Re: HtmlArea help
> >>
> >>Impossible to tell what is going wrong without seeing your component
> code,
> >>~but~ I have a few ideas even without that.
> >>
> >>Your javascript may not be getting parsed on the server return. (If that
> >>is
> >>what your component is relying on). Or...Ummm...Tapestry 3.0.3 does
> >>something really weird? There are just too many possibilities.
> >>
> >>On 8/26/05, Patrick Casey <[EMAIL PROTECTED]> wrote:
> >>
> >>>
> >>>You're right, sorry, I meant Tassel and wrote Tacos :).
> >>>
> >>>As for Tapestry, I'm on 3.0.3.
> >>>
> >>>--- Pat
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>From: Robert Zeigler [mailto:[EMAIL PROTECTED]
> >>>>Sent: Friday, August 26, 2005 12:23 PM
> >>>>To: Tapestry users
> >>>>Subject: Re: HtmlArea help
> >>>>
> >>>>Just to clarify... htmlarea isn't part of the tacos library. :)
> >>>>Not sure what's going on... what version of tapestry are you using it
> >>>>with?
> >>>>
> >>>>Robert
> >>>>
> >>>>Patrick Casey wrote:
> >>>>
> >>>>>
> >>>>>I'm trying to use the tacos htmlarea component. So far as I
> >>>>
> >>>>can
> >>>>
> >>>>>tell, it's downloaded and linked to my application properly. It runs
> >>>>
> >>>>fine,
> >>>>
> >>>>>the only problem is I don't get an HTML area out, I get a normal
> >>>>
> >>>>textarea
> >>>>
> >>>>>when it renders. No server side errors, no javascript console
> >>
> >>errors,
> >>
> >>>>just a
> >>>>
> >>>>>text area comes out.
> >>>>>
> >>>>>
> >>>>>
> >>>>>.application
> >>>>>
> >>>>><library id="htmlarea"
> >>>>>specification-path="/org/rz/htmlarea/htmlarea.library"/>
> >>>>>
> >>>>>
> >>>>>
> >>>>>What goes on my .html page
> >>>>>
> >>>>><span jwcid="@htmlarea:HtmlArea" value="ognl:object.instructions"
> >>>>
> >>>>rows="8"
> >>>>
> >>>>>cols="80"/>
> >>>>>
> >>>>>
> >>>>>
> >>>>>What actually comes out:
> >>>>>
> >>>>>
> >>>>>
> >>>>><textarea name="theArea" cols="80" rows="8" id="theArea">These are
> >>
> >>the
> >>
> >>>>>Survey <b>Instructions</b>!</textarea>
> >>>>>
> >>>>>
> >>>>>
> >>>>>In other words it looks like it's "failing safely" into a text area?
> >>>>
> >>>>Fails
> >>>>
> >>>>>identically on fireFox 1.0.6 and IE.
> >>>>>
> >>>>>
> >>>>>
> >>>>>Can anyone offer any enlightenment?
> >>>>>
> >>>>>
> >>>>>
> >>>>>--- Pat
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>---------------------------------------------------------------------
> >>>>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]
> >>>
> >>>
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
