I tried that by adding a TextField - still no joy.

> no. webpage is the correct choice. as a workaround you can make the
> page stateful....
> 
> -igor
> 
> 
> On Fri, Feb 29, 2008 at 1:04 PM, Chris Colman
> <[EMAIL PROTECTED]> wrote:
> > The class derives, ultimately, from the WebPage class. Should I try
> >  deriving it from some other wicket base class as a workaround?
> >
> >
> >
> >  > there are no conditions, these things are pushed to wicket by
> >  > invocations on  iheadercontributor's iheaderresponse interface by
all
> >  > interested components/behaviors. i guess wicket ignores these if
the
> >  > page is stateless, which woud be a bug...
> >  >
> >  > -igor
> >  >
> >  > On Fri, Feb 29, 2008 at 12:50 PM, Chris Colman
> >  > <[EMAIL PROTECTED]> wrote:
> >  > > I've tried 1.3.1 and still no luck in getting wicket to inject
the
> >  > >  appropriate <script> lines into the header of the HTML.
> >  > >
> >  > >  I was wondering what is the *trigger* or set of conditions
that
> >  wicket
> >  > >  uses to determine that it should inject the <script> lines
that
> >  import
> >  > >  the .js files into a generated HTML file?
> >  > >
> >  > >  Maybe if I understand these I can 'force' it to add these
lines.
> >  > >
> >  > >  I should mention that we're using markup inheritance in case
that
> >  has
> >  > >  some bearing on the issue.
> >  > >
> >  > >
> >  > >
> >  > >  >
> >  > >  > that is a given. try 1.3.1 and if that doesnt work try
building
> >  trunk
> >  > >  > yourself and test with that.
> >  > >  >
> >  > >  > -igor
> >  > >  >
> >  > >  >
> >  > >  > On Fri, Feb 29, 2008 at 12:16 AM, Chris Colman
> >  > >  > <[EMAIL PROTECTED]> wrote:
> >  > >  > > Using 1.3.0 - maybe I should try 1.3.1
> >  > >  > >
> >  > >  > >
> >  > >  > >
> >  > >  > >
> >  > >  > >  > -----Original Message-----
> >  > >  > >  > From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
> >  > >  > >  > Sent: Friday, 29 February 2008 6:29 PM
> >  > >  > >  > To: [email protected]
> >  > >  > >  > Subject: Re: Location of wicket-ajax.js
> >  > >  > >  >
> >  > >  > >  > this should happen automatically, please file a bug
report
> >  > >  > >  >
> >  > >  > >  > -igor
> >  > >  > >  >
> >  > >  > >  >
> >  > >  > >  > On Thu, Feb 28, 2008 at 11:26 PM, Chris Colman
> >  > >  > >  > <[EMAIL PROTECTED]> wrote:
> >  > >  > >  > > Problem found: Was a problem with <script> import
lines
> >  not
> >  > >  being
> >  > >  > >  added,
> >  > >  > >  > >  not that the .js files were not reachable.
> >  > >  > >  > >
> >  > >  > >  > >  Apparently we need to have a stateful component
> somewhere
> >  in
> >  > >  the
> >  > >  > >  page
> >  > >  > >  > in
> >  > >  > >  > >  order for wicket to auto inject the <script> lines
into
> >  the
> >  > >  HTML
> >  > >  > >  for
> >  > >  > >  > us.
> >  > >  > >  > >
> >  > >  > >  > >  Is there a way of telling wicket to inject the
<script>
> >  lines
> >  > >  > >  without
> >  > >  > >  > >  having a stateful component on the page - currently
> >  > everything
> >  > >  on
> >  > >  > >  the
> >  > >  > >  > >  page is stateless - we just have buttons on each
item
> >  that,
> >  > >  when
> >  > >  > >  > >  pressed, need to bring up an AJAX modal dialog box
to
> >  display
> >  > >  some
> >  > >  > >  info
> >  > >  > >  > >  on the items.
> >  > >  > >  > >
> >  > >  > >  > >  Or do we need to add an invisible edit control or
> >  something
> >  > to
> >  > >  get
> >  > >  > >  the
> >  > >  > >  > >  <script> injection happening?
> >  > >  > >  > >
> >  > >  > >  > >
> >  > >  > >  > >
> >  > >  > >  > >
> >  > >  > >  > >
> >  > >  > >
> >  > >
> >
---------------------------------------------------------------------
> >  > >  > >  > >  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]
> >  > >
> >  > >
> >  >
> >  >
---------------------------------------------------------------------
> >  > 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]

Reply via email to