I have been trying to get Shale Remoting working using shale v 1.03
I first tried to follow the guide at:
http://shale.apache.org/features-remoting.html
I corrected the example to the following:
First adding methods to be called by client-side Ajax to the welcome bean
(WelcomeBean.java),
ok nowones knows
2006/9/6, stephan opitz [EMAIL PROTECTED]:
is it possible to apply a complete url rewriting.
i know how to change the suffix (maybe .xml, .***), but how do i have
full control of the shown url.
is it supported?
stephan
On 9/6/06, stephan opitz [EMAIL PROTECTED] wrote:
is it possible to apply a complete url rewriting.
i know how to change the suffix (maybe .xml, .***), but how do i have
full control of the shown url.
is it supported?
It is not clear to me what you mean by complete URL rewriting. So here's
On 9/11/06, mainster [EMAIL PROTECTED] wrote:
I have been trying to get Shale Remoting working using shale v 1.03
I first tried to follow the guide at:
http://shale.apache.org/features-remoting.html
I corrected the example to the following:
First adding methods to be called by client-side
On 9/5/06, David Geary [EMAIL PROTECTED] wrote:
2006/9/5, Sean Schofield [EMAIL PROTECTED]:
We might want to revisit the one dialog per JSF view assumption. I'm
playing with the new stuff in shale-petstore and I have run into some
unexpected behavior. I have a commandLink that kicks off a
On 9/11/06, Craig McClanahan [EMAIL PROTECTED] wrote:
public String checkout() {
// Cancel the current dialog (if any, whatever it is)
FacesContext context = FacesContext.getCurrentInstance();
DialogContextManager manager = (DialogContextManager)
(top-posting on purpose)
And no action states to stuff in dialog data makes things cleaner still !
As an aside, I've restored 1.4 source compatibility for the
shale-dialog2-legacy module. I believe that any module that doesn't
inherently need tiger features should stay at 1.4 source.
Can a
On 9/11/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
(top-posting on purpose)
And no action states to stuff in dialog data makes things cleaner still !
Yep. I even tried to remove inferences (in the top level APIs) that the
underlying mechanism has to be a state machine, although I imagine
