You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by smallufo <sm...@gmail.com> on 2008/02/23 21:04:49 UTC

Wicket as a front controller ?

Hi .
I wonder if wicket can act as a servlet front controller ?

I have a normal wicket webapp , but I need one "endpoint" to process Yahoo's
bbAuth's request.
Yes , I can write normal servlet to process this , but normal servlet lacks
of spring injection and cannot access to wicket's environment.
Therefore , I need a specialized wicket "endpoint" , and that endpoint must
coexist with my wicket app .
How to do that ?

Re: Wicket as a front controller ?

Posted by Maurice Marrink <ma...@gmail.com>.
After reading up a bit on yahoo bbAuth, i'm thinking the following will work.
Take the code shown here
http://developer.yahoo.com/java/howto-BBauthJava.html for the servlet
and convert it to a servlet filter.
Then in your web.xml use this new WicketBbAuthFilter for your app
together with the original WicketFilter.
The WicketFilter must be the first to be invoked to setup wicket then
your WicketBbAuthFilter.

Spring can be handled as with any normal wicket application.

Note that the servlet example also checks if someone is already logged
in and if not authenticates them with yahoo.
You could do this too (although i would get that information from the
wicket session) or you can use a separate login page to do the
authentication request for you and let the filter just handle the
response.

Maurice

P.S. this is all from reading just a little bit about bbAuth, so i
can't give you any guarantees ;)

On Sat, Feb 23, 2008 at 9:04 PM, smallufo <sm...@gmail.com> wrote:
> Hi .
>  I wonder if wicket can act as a servlet front controller ?
>
>  I have a normal wicket webapp , but I need one "endpoint" to process Yahoo's
>  bbAuth's request.
>  Yes , I can write normal servlet to process this , but normal servlet lacks
>  of spring injection and cannot access to wicket's environment.
>  Therefore , I need a specialized wicket "endpoint" , and that endpoint must
>  coexist with my wicket app .
>  How to do that ?
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Wicket as a front controller ?

Posted by smallufo <sm...@gmail.com>.
Thank you for suggestion.
But I am using Resin 3.0.x as a servlet container.
And wicket 1.3's filter seems not working on Resin 3.0.x
see this thread for details :
http://www.nabble.com/Server-cannot-find--app-url-after-migration-to-1.3-filter-to12998876.html

Therefore , I've stay on WicketServlet



2008/2/24, Maurice Marrink <ma...@gmail.com>:
>
> >  If I use pure servlet to implement this , I have to hard code the
> >  redirecting URL , and can only use HttpSession ...
>
> If you use a filter, placed after the wicket filter, i think you can
> use the wicket session and you do not need to redirect because you can
> do Session.get().login(.....) and happily continue to the page.
>
>
> Maurice
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

Re: Wicket as a front controller ?

Posted by Maurice Marrink <ma...@gmail.com>.
>  If I use pure servlet to implement this , I have to hard code the
>  redirecting URL , and can only use HttpSession ...
If you use a filter, placed after the wicket filter, i think you can
use the wicket session and you do not need to redirect because you can
do Session.get().login(.....) and happily continue to the page.

Maurice

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Wicket as a front controller ?

Posted by smallufo <sm...@gmail.com>.
2008/2/26, smallufo <sm...@gmail.com>:
>
> Thank you , it's almost done.
> But it still have problems :
> Calling setResponsePage() at the end of onBeforeRender() not working.
> How to solve it ?
>
I found the answer .
just add : setRedirect(true);
And it works.

Re: Wicket as a front controller ?

Posted by smallufo <sm...@gmail.com>.
Thank you , it's almost done.
But it still have problems :
Calling setResponsePage() at the end of onBeforeRender() not working.
How to solve it ?


2008/2/25, Kent Tong <ke...@cpttm.org.mo>:
>
> smallufo <smallufo <at> gmail.com> writes:
>
> > I just need to redirect.
> > If bbAuth token is correct , then set correct Wicket Session and
> redirect to
> > proper page.
> > If incorrect , then redirect to another page.
>
>
> To redirect, try:
>
> public class P1 extends WebPage {
>         @Override
>         protected void onBeforeRender() {
>                 super.onBeforeRender();
>                 throw new RestartResponseException(P2.class);
>         }
>
> }
>

Re: Wicket as a front controller ?

Posted by smallufo <sm...@gmail.com>.
Oops , sorry , I found what went wrong....
Because the Server page inherits another Parent Page.
So it output the header of its parent page...


2008/2/29 smallufo <sm...@gmail.com>:

>
> >
> > To redirect, try:
> >
> > public class P1 extends WebPage {
> >        @Override
> >        protected void onBeforeRender() {
> >                super.onBeforeRender();
> >                throw new RestartResponseException(P2.class);
> >        }
> >
> > }
> >
>
> Hi
> I want to handle a POST request , and output custom messages , but....
>
> In onBeroereRenderer()  , I write the following codes :
>
> HttpServletResponse res = ((WebResponse)
> getWebRequestCycle().getResponse()).getHttpServletResponse();
> PrintWriter out = res.getWriter();
> out.print(responseText);
>
> But wicket seems pre-output HTML's DOCTYPE , that makes the remote site
> can't parse...:
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>
> I've already deleted the corresponding HTML file.
>
> How to make wicket not pre-output any HTML header/doctype ?
>

Re: Location of wicket-ajax.js

Posted by Matej Knopp <ma...@gmail.com>.
I haven't seen such problem with header contributions for 1.3 yet.
Would be great if you could put together quickstart to reproduce it.

-Matej

On Sun, Mar 2, 2008 at 2:03 AM, Chris Colman
<ch...@stepaheadsoftware.com> wrote:
> > > I kinda miss the point of this entire thread? What exactly doesn't
>  > > work? Are you getting no javascript references written to your
>  > > <head></head> section?
>
>  Correct.
>
>
>  > > How did you map the WicketFilter?
>  >
>  > Whoooh! I think you might have found the problem for us.
>
>  Unfortunately we still have the problem after changing over to filter
>  instead of servlet config for wicket.
>
>
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  For additional commands, e-mail: users-help@wicket.apache.org
>
>



-- 
Resizable and reorderable grid components.
http://www.inmethod.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


RE: Location of wicket-ajax.js

Posted by Chris Colman <ch...@stepaheadsoftware.com>.
> > I kinda miss the point of this entire thread? What exactly doesn't
> > work? Are you getting no javascript references written to your
> > <head></head> section? 

Correct.

> > How did you map the WicketFilter?
> 
> Whoooh! I think you might have found the problem for us.

Unfortunately we still have the problem after changing over to filter
instead of servlet config for wicket.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


RE: Location of wicket-ajax.js

Posted by Chris Colman <ch...@stepaheadsoftware.com>.
> I kinda miss the point of this entire thread? What exactly doesn't
> work? Are you getting no javascript references written to your
> <head></head> section? How did you map the WicketFilter?

Whoooh! I think you might have found the problem for us.

We're still mapping via the WicketServlet not the filter. Maybe that's a
wicket 1.2.x legacy that we neglected to migrate when we switched to
1.3.x.

We already have an exPOJO filter auto handling persistence for us so I
guess we now have to chain that filter with the wicket filter. I wonder
how we do that...

<servlet>
	<servlet-name>MyServer</servlet-name>
	
<servlet-class>org.apache.wicket.protocol.http.WicketServlet</servlet-cl
ass>
	<init-param>
	  <param-name>applicationClassName</param-name>
	  <param-value>com.sas.av.ui.wicket.MyApp</param-value>
		</init-param>
		<load-on-startup>1</load-on-startup>
</servlet>

<servlet-mapping>
	<servlet-name>MyServer</servlet-name>
	<url-pattern>/content/*</url-pattern>
</servlet-mapping>

> 
> 
> -Matej
> 
> On Sat, Mar 1, 2008 at 7:19 AM, Chris Colman
> <ch...@stepaheadsoftware.com> wrote:
> > How do I force a page to be stateful?
> >
> >
> >
> >  > 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
> >  > > <ch...@stepaheadsoftware.com> 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
> >  > > >  > <ch...@stepaheadsoftware.com> 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
> >  > > >  > >  > <ch...@stepaheadsoftware.com> wrote:
> >  > > >  > >  > > Using 1.3.0 - maybe I should try 1.3.1
> >  > > >  > >  > >
> >  > > >  > >  > >
> >  > > >  > >  > >
> >  > > >  > >  > >
> >  > > >  > >  > >  > -----Original Message-----
> >  > > >  > >  > >  > From: Igor Vaynberg
[mailto:igor.vaynberg@gmail.com]
> >  > > >  > >  > >  > Sent: Friday, 29 February 2008 6:29 PM
> >  > > >  > >  > >  > To: users@wicket.apache.org
> >  > > >  > >  > >  > 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
> >  > > >  > >  > >  > <ch...@stepaheadsoftware.com> 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:
> >  > > >  users-unsubscribe@wicket.apache.org
> >  > > >  > >  > >  > >  For additional commands, e-mail:
> >  > > >  users-help@wicket.apache.org
> >  > > >  > >  > >  > >
> >  > > >  > >  > >  > >
> >  > > >  > >  > >  >
> >  > > >  > >  > >  >
> >  > > >  > >
> >  > > >
> >  >
---------------------------------------------------------------------
> >  > > >  > >  > >  > To unsubscribe, e-mail:
> >  > users-unsubscribe@wicket.apache.org
> >  > > >  > >  > >  > For additional commands, e-mail:
> >  > > >  users-help@wicket.apache.org
> >  > > >  > >  > >
> >  > > >  > >  > >
> >  > > >  > >  > >
> >  > > >  > >
> >  > > >
> >  >
---------------------------------------------------------------------
> >  > > >  > >  > >  To unsubscribe, e-mail:
> >  > users-unsubscribe@wicket.apache.org
> >  > > >  > >  > >  For additional commands, e-mail:
> >  > users-help@wicket.apache.org
> >  > > >  > >  > >
> >  > > >  > >  > >
> >  > > >  > >  >
> >  > > >  > >  >
> >  > > >
> >  >
---------------------------------------------------------------------
> >  > > >  > >  > To unsubscribe, e-mail:
> >  users-unsubscribe@wicket.apache.org
> >  > > >  > >  > For additional commands, e-mail:
> >  > users-help@wicket.apache.org
> >  > > >  > >
> >  > > >  > >
> >  > > >  > >
> >  > > >
> >  >
---------------------------------------------------------------------
> >  > > >  > >  To unsubscribe, e-mail:
users-unsubscribe@wicket.apache.org
> >  > > >  > >  For additional commands, e-mail:
> >  users-help@wicket.apache.org
> >  > > >  > >
> >  > > >  > >
> >  > > >  >
> >  > > >  >
> >  >
---------------------------------------------------------------------
> >  > > >  > To unsubscribe, e-mail:
users-unsubscribe@wicket.apache.org
> >  > > >  > For additional commands, e-mail:
users-help@wicket.apache.org
> >  > > >
> >  > > >
> >  > > >
> >  >
---------------------------------------------------------------------
> >  > > >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  > > >  For additional commands, e-mail:
users-help@wicket.apache.org
> >  > > >
> >  > > >
> >  > >
> >  > >
> >
---------------------------------------------------------------------
> >  > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  > > For additional commands, e-mail: users-help@wicket.apache.org
> >  >
> >  >
> >  >
---------------------------------------------------------------------
> >  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> >
---------------------------------------------------------------------
> >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> 
> 
> 
> --
> Resizable and reorderable grid components.
> http://www.inmethod.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Location of wicket-ajax.js

Posted by Matej Knopp <ma...@gmail.com>.
I kinda miss the point of this entire thread? What exactly doesn't
work? Are you getting no javascript references written to your
<head></head> section? How did you map the WicketFilter?

-Matej

On Sat, Mar 1, 2008 at 7:19 AM, Chris Colman
<ch...@stepaheadsoftware.com> wrote:
> How do I force a page to be stateful?
>
>
>
>  > 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
>  > > <ch...@stepaheadsoftware.com> 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
>  > > >  > <ch...@stepaheadsoftware.com> 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
>  > > >  > >  > <ch...@stepaheadsoftware.com> wrote:
>  > > >  > >  > > Using 1.3.0 - maybe I should try 1.3.1
>  > > >  > >  > >
>  > > >  > >  > >
>  > > >  > >  > >
>  > > >  > >  > >
>  > > >  > >  > >  > -----Original Message-----
>  > > >  > >  > >  > From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>  > > >  > >  > >  > Sent: Friday, 29 February 2008 6:29 PM
>  > > >  > >  > >  > To: users@wicket.apache.org
>  > > >  > >  > >  > 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
>  > > >  > >  > >  > <ch...@stepaheadsoftware.com> 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:
>  > > >  users-unsubscribe@wicket.apache.org
>  > > >  > >  > >  > >  For additional commands, e-mail:
>  > > >  users-help@wicket.apache.org
>  > > >  > >  > >  > >
>  > > >  > >  > >  > >
>  > > >  > >  > >  >
>  > > >  > >  > >  >
>  > > >  > >
>  > > >
>  > ---------------------------------------------------------------------
>  > > >  > >  > >  > To unsubscribe, e-mail:
>  > users-unsubscribe@wicket.apache.org
>  > > >  > >  > >  > For additional commands, e-mail:
>  > > >  users-help@wicket.apache.org
>  > > >  > >  > >
>  > > >  > >  > >
>  > > >  > >  > >
>  > > >  > >
>  > > >
>  > ---------------------------------------------------------------------
>  > > >  > >  > >  To unsubscribe, e-mail:
>  > users-unsubscribe@wicket.apache.org
>  > > >  > >  > >  For additional commands, e-mail:
>  > users-help@wicket.apache.org
>  > > >  > >  > >
>  > > >  > >  > >
>  > > >  > >  >
>  > > >  > >  >
>  > > >
>  > ---------------------------------------------------------------------
>  > > >  > >  > To unsubscribe, e-mail:
>  users-unsubscribe@wicket.apache.org
>  > > >  > >  > For additional commands, e-mail:
>  > users-help@wicket.apache.org
>  > > >  > >
>  > > >  > >
>  > > >  > >
>  > > >
>  > ---------------------------------------------------------------------
>  > > >  > >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > > >  > >  For additional commands, e-mail:
>  users-help@wicket.apache.org
>  > > >  > >
>  > > >  > >
>  > > >  >
>  > > >  >
>  > ---------------------------------------------------------------------
>  > > >  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > > >  > For additional commands, e-mail: users-help@wicket.apache.org
>  > > >
>  > > >
>  > > >
>  > ---------------------------------------------------------------------
>  > > >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > > >  For additional commands, e-mail: users-help@wicket.apache.org
>  > > >
>  > > >
>  > >
>  > >
>  ---------------------------------------------------------------------
>  > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > > For additional commands, e-mail: users-help@wicket.apache.org
>  >
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > For additional commands, e-mail: users-help@wicket.apache.org
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  For additional commands, e-mail: users-help@wicket.apache.org
>
>



-- 
Resizable and reorderable grid components.
http://www.inmethod.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Location of wicket-ajax.js

Posted by Johan Compagner <jc...@gmail.com>.
if ajax is used in a page then the page is not stateless anyway.

johan



On Fri, Feb 29, 2008 at 9:55 PM, Igor Vaynberg <ig...@gmail.com>
wrote:

> 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
>  <ch...@stepaheadsoftware.com> 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
> >  > <ch...@stepaheadsoftware.com> wrote:
> >  > > Using 1.3.0 - maybe I should try 1.3.1
> >  > >
> >  > >
> >  > >
> >  > >
> >  > >  > -----Original Message-----
> >  > >  > From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> >  > >  > Sent: Friday, 29 February 2008 6:29 PM
> >  > >  > To: users@wicket.apache.org
> >  > >  > 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
> >  > >  > <ch...@stepaheadsoftware.com> 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: users-unsubscribe@wicket.apache.org
> >  > >  > >  For additional commands, e-mail: users-help@wicket.apache.org
> >  > >  > >
> >  > >  > >
> >  > >  >
> >  > >  >
> >  ---------------------------------------------------------------------
> >  > >  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  > >  > For additional commands, e-mail: users-help@wicket.apache.org
> >  > >
> >  > >
> >  > >
> >  ---------------------------------------------------------------------
> >  > >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  > >  For additional commands, e-mail: users-help@wicket.apache.org
> >  > >
> >  > >
> >  >
> >  > ---------------------------------------------------------------------
> >  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> >  ---------------------------------------------------------------------
> >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

RE: Location of wicket-ajax.js

Posted by Chris Colman <ch...@stepaheadsoftware.com>.
How do I force a page to be stateful?

> 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
> > <ch...@stepaheadsoftware.com> 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
> > >  > <ch...@stepaheadsoftware.com> 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
> > >  > >  > <ch...@stepaheadsoftware.com> wrote:
> > >  > >  > > Using 1.3.0 - maybe I should try 1.3.1
> > >  > >  > >
> > >  > >  > >
> > >  > >  > >
> > >  > >  > >
> > >  > >  > >  > -----Original Message-----
> > >  > >  > >  > From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> > >  > >  > >  > Sent: Friday, 29 February 2008 6:29 PM
> > >  > >  > >  > To: users@wicket.apache.org
> > >  > >  > >  > 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
> > >  > >  > >  > <ch...@stepaheadsoftware.com> 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:
> > >  users-unsubscribe@wicket.apache.org
> > >  > >  > >  > >  For additional commands, e-mail:
> > >  users-help@wicket.apache.org
> > >  > >  > >  > >
> > >  > >  > >  > >
> > >  > >  > >  >
> > >  > >  > >  >
> > >  > >
> > >
> ---------------------------------------------------------------------
> > >  > >  > >  > To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> > >  > >  > >  > For additional commands, e-mail:
> > >  users-help@wicket.apache.org
> > >  > >  > >
> > >  > >  > >
> > >  > >  > >
> > >  > >
> > >
> ---------------------------------------------------------------------
> > >  > >  > >  To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> > >  > >  > >  For additional commands, e-mail:
> users-help@wicket.apache.org
> > >  > >  > >
> > >  > >  > >
> > >  > >  >
> > >  > >  >
> > >
> ---------------------------------------------------------------------
> > >  > >  > To unsubscribe, e-mail:
users-unsubscribe@wicket.apache.org
> > >  > >  > For additional commands, e-mail:
> users-help@wicket.apache.org
> > >  > >
> > >  > >
> > >  > >
> > >
> ---------------------------------------------------------------------
> > >  > >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > >  > >  For additional commands, e-mail:
users-help@wicket.apache.org
> > >  > >
> > >  > >
> > >  >
> > >  >
> ---------------------------------------------------------------------
> > >  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > >  > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > >  For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


RE: Location of wicket-ajax.js

Posted by Chris Colman <ch...@stepaheadsoftware.com>.
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
> <ch...@stepaheadsoftware.com> 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
> >  > <ch...@stepaheadsoftware.com> 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
> >  > >  > <ch...@stepaheadsoftware.com> wrote:
> >  > >  > > Using 1.3.0 - maybe I should try 1.3.1
> >  > >  > >
> >  > >  > >
> >  > >  > >
> >  > >  > >
> >  > >  > >  > -----Original Message-----
> >  > >  > >  > From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> >  > >  > >  > Sent: Friday, 29 February 2008 6:29 PM
> >  > >  > >  > To: users@wicket.apache.org
> >  > >  > >  > 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
> >  > >  > >  > <ch...@stepaheadsoftware.com> 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:
> >  users-unsubscribe@wicket.apache.org
> >  > >  > >  > >  For additional commands, e-mail:
> >  users-help@wicket.apache.org
> >  > >  > >  > >
> >  > >  > >  > >
> >  > >  > >  >
> >  > >  > >  >
> >  > >
> >
---------------------------------------------------------------------
> >  > >  > >  > To unsubscribe, e-mail:
users-unsubscribe@wicket.apache.org
> >  > >  > >  > For additional commands, e-mail:
> >  users-help@wicket.apache.org
> >  > >  > >
> >  > >  > >
> >  > >  > >
> >  > >
> >
---------------------------------------------------------------------
> >  > >  > >  To unsubscribe, e-mail:
users-unsubscribe@wicket.apache.org
> >  > >  > >  For additional commands, e-mail:
users-help@wicket.apache.org
> >  > >  > >
> >  > >  > >
> >  > >  >
> >  > >  >
> >
---------------------------------------------------------------------
> >  > >  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  > >  > For additional commands, e-mail:
users-help@wicket.apache.org
> >  > >
> >  > >
> >  > >
> >
---------------------------------------------------------------------
> >  > >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  > >  For additional commands, e-mail: users-help@wicket.apache.org
> >  > >
> >  > >
> >  >
> >  >
---------------------------------------------------------------------
> >  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> >
---------------------------------------------------------------------
> >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Location of wicket-ajax.js

Posted by Igor Vaynberg <ig...@gmail.com>.
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
<ch...@stepaheadsoftware.com> 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
>  > <ch...@stepaheadsoftware.com> 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
>  > >  > <ch...@stepaheadsoftware.com> wrote:
>  > >  > > Using 1.3.0 - maybe I should try 1.3.1
>  > >  > >
>  > >  > >
>  > >  > >
>  > >  > >
>  > >  > >  > -----Original Message-----
>  > >  > >  > From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>  > >  > >  > Sent: Friday, 29 February 2008 6:29 PM
>  > >  > >  > To: users@wicket.apache.org
>  > >  > >  > 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
>  > >  > >  > <ch...@stepaheadsoftware.com> 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:
>  users-unsubscribe@wicket.apache.org
>  > >  > >  > >  For additional commands, e-mail:
>  users-help@wicket.apache.org
>  > >  > >  > >
>  > >  > >  > >
>  > >  > >  >
>  > >  > >  >
>  > >
>  ---------------------------------------------------------------------
>  > >  > >  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > >  > >  > For additional commands, e-mail:
>  users-help@wicket.apache.org
>  > >  > >
>  > >  > >
>  > >  > >
>  > >
>  ---------------------------------------------------------------------
>  > >  > >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > >  > >  For additional commands, e-mail: users-help@wicket.apache.org
>  > >  > >
>  > >  > >
>  > >  >
>  > >  >
>  ---------------------------------------------------------------------
>  > >  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > >  > For additional commands, e-mail: users-help@wicket.apache.org
>  > >
>  > >
>  > >
>  ---------------------------------------------------------------------
>  > >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > >  For additional commands, e-mail: users-help@wicket.apache.org
>  > >
>  > >
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > For additional commands, e-mail: users-help@wicket.apache.org
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


RE: Location of wicket-ajax.js

Posted by Chris Colman <ch...@stepaheadsoftware.com>.
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
> <ch...@stepaheadsoftware.com> 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
> >  > <ch...@stepaheadsoftware.com> wrote:
> >  > > Using 1.3.0 - maybe I should try 1.3.1
> >  > >
> >  > >
> >  > >
> >  > >
> >  > >  > -----Original Message-----
> >  > >  > From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> >  > >  > Sent: Friday, 29 February 2008 6:29 PM
> >  > >  > To: users@wicket.apache.org
> >  > >  > 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
> >  > >  > <ch...@stepaheadsoftware.com> 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:
users-unsubscribe@wicket.apache.org
> >  > >  > >  For additional commands, e-mail:
users-help@wicket.apache.org
> >  > >  > >
> >  > >  > >
> >  > >  >
> >  > >  >
> >
---------------------------------------------------------------------
> >  > >  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  > >  > For additional commands, e-mail:
users-help@wicket.apache.org
> >  > >
> >  > >
> >  > >
> >
---------------------------------------------------------------------
> >  > >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  > >  For additional commands, e-mail: users-help@wicket.apache.org
> >  > >
> >  > >
> >  >
> >  >
---------------------------------------------------------------------
> >  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> >
---------------------------------------------------------------------
> >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Location of wicket-ajax.js

Posted by Igor Vaynberg <ig...@gmail.com>.
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
<ch...@stepaheadsoftware.com> 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
>  > <ch...@stepaheadsoftware.com> wrote:
>  > > Using 1.3.0 - maybe I should try 1.3.1
>  > >
>  > >
>  > >
>  > >
>  > >  > -----Original Message-----
>  > >  > From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>  > >  > Sent: Friday, 29 February 2008 6:29 PM
>  > >  > To: users@wicket.apache.org
>  > >  > 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
>  > >  > <ch...@stepaheadsoftware.com> 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: users-unsubscribe@wicket.apache.org
>  > >  > >  For additional commands, e-mail: users-help@wicket.apache.org
>  > >  > >
>  > >  > >
>  > >  >
>  > >  >
>  ---------------------------------------------------------------------
>  > >  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > >  > For additional commands, e-mail: users-help@wicket.apache.org
>  > >
>  > >
>  > >
>  ---------------------------------------------------------------------
>  > >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > >  For additional commands, e-mail: users-help@wicket.apache.org
>  > >
>  > >
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > For additional commands, e-mail: users-help@wicket.apache.org
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


RE: Location of wicket-ajax.js

Posted by Chris Colman <ch...@stepaheadsoftware.com>.
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
> <ch...@stepaheadsoftware.com> wrote:
> > Using 1.3.0 - maybe I should try 1.3.1
> >
> >
> >
> >
> >  > -----Original Message-----
> >  > From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> >  > Sent: Friday, 29 February 2008 6:29 PM
> >  > To: users@wicket.apache.org
> >  > 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
> >  > <ch...@stepaheadsoftware.com> 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: users-unsubscribe@wicket.apache.org
> >  > >  For additional commands, e-mail: users-help@wicket.apache.org
> >  > >
> >  > >
> >  >
> >  >
---------------------------------------------------------------------
> >  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> >
---------------------------------------------------------------------
> >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Location of wicket-ajax.js

Posted by Igor Vaynberg <ig...@gmail.com>.
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
<ch...@stepaheadsoftware.com> wrote:
> Using 1.3.0 - maybe I should try 1.3.1
>
>
>
>
>  > -----Original Message-----
>  > From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>  > Sent: Friday, 29 February 2008 6:29 PM
>  > To: users@wicket.apache.org
>  > 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
>  > <ch...@stepaheadsoftware.com> 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: users-unsubscribe@wicket.apache.org
>  > >  For additional commands, e-mail: users-help@wicket.apache.org
>  > >
>  > >
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > For additional commands, e-mail: users-help@wicket.apache.org
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


RE: Location of wicket-ajax.js

Posted by Chris Colman <ch...@stepaheadsoftware.com>.
Using 1.3.0 - maybe I should try 1.3.1


> -----Original Message-----
> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> Sent: Friday, 29 February 2008 6:29 PM
> To: users@wicket.apache.org
> 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
> <ch...@stepaheadsoftware.com> 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: users-unsubscribe@wicket.apache.org
> >  For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Location of wicket-ajax.js

Posted by Igor Vaynberg <ig...@gmail.com>.
this should happen automatically, please file a bug report

-igor


On Thu, Feb 28, 2008 at 11:26 PM, Chris Colman
<ch...@stepaheadsoftware.com> 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: users-unsubscribe@wicket.apache.org
>  For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


RE: Location of wicket-ajax.js

Posted by Chris Colman <ch...@stepaheadsoftware.com>.
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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Location of wicket-ajax.js

Posted by Igor Vaynberg <ig...@gmail.com>.
it will find them in the jar
-igor


On Thu, Feb 28, 2008 at 10:00 PM, Chris Colman
<ch...@stepaheadsoftware.com> wrote:
> Do we have to explicitly unpack the .js files from the wicket-1.3.x.jar
>  and move them into that directory or should it find them while resident
>  in the wicket jar ?
>
>
>
>  > no, resources is a path that is owned by wicket resources. so what
>  > that url tells wicket is to look for wicket-ajax.js under
>  > classes/org/apache/wicket/ajax
>  >
>  > -igor
>  >
>  >
>  > On Thu, Feb 28, 2008 at 9:47 PM, Chris Colman
>  > <ch...@stepaheadsoftware.com> wrote:
>  > > When using AJAX with wicket where are the instructions on where and
>  how
>  > >  to make the .js available to the browser?
>  > >
>  > >  Eg., resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-
>  > ajax.js
>  > >
>  > >  Do we have to create a directory under project/web called
>  > >  resources/org.apache.wicket.ajax.WicketAjaxReference ? into which
>  we
>  > >  copy the .js?
>  > >
>  > >
>  > >
>  ---------------------------------------------------------------------
>  > >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > >  For additional commands, e-mail: users-help@wicket.apache.org
>  > >
>  > >
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  > For additional commands, e-mail: users-help@wicket.apache.org
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


RE: Location of wicket-ajax.js

Posted by Chris Colman <ch...@stepaheadsoftware.com>.
Do we have to explicitly unpack the .js files from the wicket-1.3.x.jar
and move them into that directory or should it find them while resident
in the wicket jar ?

> no, resources is a path that is owned by wicket resources. so what
> that url tells wicket is to look for wicket-ajax.js under
> classes/org/apache/wicket/ajax
> 
> -igor
> 
> 
> On Thu, Feb 28, 2008 at 9:47 PM, Chris Colman
> <ch...@stepaheadsoftware.com> wrote:
> > When using AJAX with wicket where are the instructions on where and
how
> >  to make the .js available to the browser?
> >
> >  Eg., resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-
> ajax.js
> >
> >  Do we have to create a directory under project/web called
> >  resources/org.apache.wicket.ajax.WicketAjaxReference ? into which
we
> >  copy the .js?
> >
> >
> >
---------------------------------------------------------------------
> >  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >  For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Location of wicket-ajax.js

Posted by Igor Vaynberg <ig...@gmail.com>.
no, resources is a path that is owned by wicket resources. so what
that url tells wicket is to look for wicket-ajax.js under
classes/org/apache/wicket/ajax

-igor


On Thu, Feb 28, 2008 at 9:47 PM, Chris Colman
<ch...@stepaheadsoftware.com> wrote:
> When using AJAX with wicket where are the instructions on where and how
>  to make the .js available to the browser?
>
>  Eg., resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js
>
>  Do we have to create a directory under project/web called
>  resources/org.apache.wicket.ajax.WicketAjaxReference ? into which we
>  copy the .js?
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Location of wicket-ajax.js

Posted by Chris Colman <ch...@stepaheadsoftware.com>.
When using AJAX with wicket where are the instructions on where and how
to make the .js available to the browser?

Eg., resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js

Do we have to create a directory under project/web called
resources/org.apache.wicket.ajax.WicketAjaxReference ? into which we
copy the .js?


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Wicket as a front controller ?

Posted by smallufo <sm...@gmail.com>.
>
>
>
> To redirect, try:
>
> public class P1 extends WebPage {
>        @Override
>        protected void onBeforeRender() {
>                super.onBeforeRender();
>                throw new RestartResponseException(P2.class);
>        }
>
> }
>

Hi
I want to handle a POST request , and output custom messages , but....

In onBeroereRenderer()  , I write the following codes :

HttpServletResponse res = ((WebResponse)
getWebRequestCycle().getResponse()).getHttpServletResponse();
PrintWriter out = res.getWriter();
out.print(responseText);

But wicket seems pre-output HTML's DOCTYPE , that makes the remote site
can't parse...:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

I've already deleted the corresponding HTML file.

How to make wicket not pre-output any HTML header/doctype ?

Re: Wicket as a front controller ?

Posted by Kent Tong <ke...@cpttm.org.mo>.
smallufo <smallufo <at> gmail.com> writes:

> I just need to redirect.
> If bbAuth token is correct , then set correct Wicket Session and redirect to
> proper page.
> If incorrect , then redirect to another page.

To redirect, try:

public class P1 extends WebPage {
	@Override
	protected void onBeforeRender() {
		super.onBeforeRender();
		throw new RestartResponseException(P2.class);
	}

}
--
Kent Tong
Wicket book with free chapters at http://www.agileskills2.org/EWDW



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Wicket as a front controller ?

Posted by smallufo <sm...@gmail.com>.
I just need to redirect.
If bbAuth token is correct , then set correct Wicket Session and redirect to
proper page.
If incorrect , then redirect to another page.

If I use pure servlet to implement this , I have to hard code the
redirecting URL , and can only use HttpSession ...


2008/2/24, Kent Tong <ke...@cpttm.org.mo>:
>
>
>
> smallufo wrote:
> >
> > Thank you , but I want a (bookmarkable) page without HTML
> > Is it possible ?
> >
>
>
> What do you want to output?
>
>
> -----
> --
> Kent Tong
> Wicket tutorials freely available at http://www.agileskills2.org/EWDW
> Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA
> --
>
> View this message in context:
> http://www.nabble.com/Wicket-as-a-front-controller---tp15656646p15664148.html
>
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

Re: Wicket as a front controller ?

Posted by Kent Tong <ke...@cpttm.org.mo>.

smallufo wrote:
> 
> Thank you , but I want a (bookmarkable) page without HTML
> Is it possible ?
> 

What do you want to output?

-----
--
Kent Tong
Wicket tutorials freely available at http://www.agileskills2.org/EWDW
Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA
-- 
View this message in context: http://www.nabble.com/Wicket-as-a-front-controller---tp15656646p15664148.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Wicket as a front controller ?

Posted by smallufo <sm...@gmail.com>.
Thank you , but I want a (bookmarkable) page without HTML
Is it possible ?

2008/2/24, Kent Tong <ke...@cpttm.org.mo>:
>
>
>
> smallufo wrote:
> >
> > I have a normal wicket webapp , but I need one "endpoint" to process
> > Yahoo's
> > bbAuth's request.
> > Yes , I can write normal servlet to process this , but normal servlet
> > lacks
> > of spring injection and cannot access to wicket's environment.
> >
>
>
> Have you tried using a bookmarkabke page as the endpoint? Something like
> http://foo.com/MyApp/app/?wicket:bookmarkablePage=:com.foo.MyApp.MyPage
>
>
>

Re: Wicket as a front controller ?

Posted by Kent Tong <ke...@cpttm.org.mo>.

smallufo wrote:
> 
> I have a normal wicket webapp , but I need one "endpoint" to process
> Yahoo's
> bbAuth's request.
> Yes , I can write normal servlet to process this , but normal servlet
> lacks
> of spring injection and cannot access to wicket's environment.
> 

Have you tried using a bookmarkabke page as the endpoint? Something like
http://foo.com/MyApp/app/?wicket:bookmarkablePage=:com.foo.MyApp.MyPage


-----
--
Kent Tong
Wicket tutorials freely available at http://www.agileskills2.org/EWDW
Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA
-- 
View this message in context: http://www.nabble.com/Wicket-as-a-front-controller---tp15656646p15660420.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org