Force refresh resource bundles

2007-05-11 Thread Brody Wong

In my project, I need to perform forced refresh for resource bundles without
shutting down the application. Is it possible in Shale? I have only found
the class LoadBundle related to this. 

If I can find a way to list all bundles for an application, I can follow the
practice in this link:

http://technology.amis.nl/blog/?p=1360

The author is using JHeadStart from Oracle.

Many thanks.
-- 
View this message in context: 
http://www.nabble.com/Force-refresh-resource-bundles-tf3725703.html#a10426598
Sent from the Shale - User mailing list archive at Nabble.com.



Re: Shale and Sandbox inputSuggestAjax

2007-05-11 Thread Torsten Krah
Question about the chain configuration.

How can i support more than one inputSuggestAjax inputs - the
PropertyListenerCommand does have static mappings.

Changing the method signature will result in an error. Is there a clean
way to support more than one instance with different method signatures?

Torsten

Am Dienstag, den 08.05.2007, 14:46 + schrieb Gary VanMatre:
 From: Erik Govaers [EMAIL PROTECTED] 
 
  Hello, 
  
  I’m trying my hand at a very simple example based on the 
  example at http://www.irian.at/myfaces-sandbox/inputSuggestAjax.jsf. I get 
  an 
  input field, but when I start typing I get no suggestions since my backing 
  bean 
  ‘suggestedItems’ method is never called. I’m using server-side saving, but 
  switching to client-side makes no difference. I’ve looked at a lot of the 
  inputSuggestAjax related issues in the mailing lists, but found no solution 
  yet. 
  My guess is that is has either something to do with the fact that I'm using 
  MyFaces 1.1.3 or with the fact that the Shale/Clay ValidatorInputRenderer 
  is 
  overwriting the InputSuggestAjax Renderer (something I noticed just now). 
  If the 
  latter is true, what can I do to prevent this? 
 
 
 This is an open JIRA ticket [1].  We need to find a configurable option for 
 specifying components in the javax.faces.Input family that should be 
 excluded from the commons validator renderer decorator.
 
 This looks like a cool component. You might try a workaround.  This is a 
 *complete hack* but I think it should solve this problem.  The trick would be 
 to change the component family and rendererType.
  
 
 [1] https://issues.apache.org/struts/browse/SHALE-442
  
 Consider:
 
 
 // subclass the component overriding the family and renderer type.
 package com.acme.InputSuggestAjax
 public class InputSuggestAjax extends 
 org.apache.myfaces.custom.suggestajax.inputsuggestajax.InputSuggestAjax {
public InputSuggestAjax() {
   setRendererType(com.acme.InputSuggestAjax)
}   
public String getFamily() {
return com.acme.Input;
}
 
 
 }
 
 // register the subclassed component in the /WEB-INF/faces-config.xml
 
   component
 component-typecom.acme.InputSuggestAjax/component-type
 component-classcom.acme.InputSuggestAjax/component-class
   /component
  render-kit
 renderer
   component-familycom.acme.Input/component-family
   renderer-typecom.acme.InputSuggestAjax/renderer-type
   
 renderer-classorg.apache.myfaces.custom.suggestajax.inputsuggestajax.InputSuggestAjaxRenderer/renderer-class
 /renderer
   /render-kit
 
 
 Depending on if you are using JSP, Clay or Facelets you will need some 
 additional setup. 
 
 
 Gary


smime.p7s
Description: S/MIME cryptographic signature


Re: SV: SV: Shale and Sandbox inputSuggestAjax

2007-05-11 Thread Torsten Krah
Thx - nice work.

Tried it, works so far - method gets called and i get an ajax response.
But i see no popup in the browser, must have done something wrong ;).

Torsten


Am Dienstag, den 08.05.2007, 19:57 +0200 schrieb Hermod Opstvedt:
 Hi
 
 Wiki entry in place.
 
 Hermod
 
 
 -Opprinnelig melding-
 Fra: Erik Govaers [mailto:[EMAIL PROTECTED] 
 Sendt: 8. mai 2007 17:33
 Til: user@shale.apache.org
 Emne: Re: SV: Shale and Sandbox inputSuggestAjax
 
 Hi,
 
 It would be brilliant if you could get us a fix in a couple of days. I'm in 
 an advanced phase of a project and I'm reluctant to let go of either Shale or 
 Tomahawk-Sandbox. And yes, I would welcome a Wiki too.
 
 Thank you,
 
 Erik
 
 
 - Oorspronkelijk bericht -
 Van: Hermod Opstvedt [mailto:[EMAIL PROTECTED]
 Verzonden: dinsdag, mei 8, 2007 05:14 PM
 Aan: user@shale.apache.org
 Onderwerp: SV: Shale and Sandbox inputSuggestAjax
 
 Hi
 
 I have a working setup for Clay on this and if there is an interest I can 
 write a small tutorial on the Wiki.
 
 I am going to start a fix for the Shale-validator which is the cause of this 
 later to day and hopefully it will be done in a day or two.
 
 Hermod
 
 
 -Opprinnelig melding-
 Fra: Gary VanMatre [mailto:[EMAIL PROTECTED] 
 Sendt: 8. mai 2007 16:47
 Til: user@shale.apache.org
 Emne: Re: Shale and Sandbox inputSuggestAjax
 
 From: Erik Govaers [EMAIL PROTECTED] 
 
  Hello, 
  
  I’m trying my hand at a very simple example based on the 
  example at http://www.irian.at/myfaces-sandbox/inputSuggestAjax.jsf. I get 
  an 
  input field, but when I start typing I get no suggestions since my backing 
  bean 
  ‘suggestedItems’ method is never called. I’m using server-side 
  saving, but 
  switching to client-side makes no difference. I’ve looked at a lot of 
  the 
  inputSuggestAjax related issues in the mailing lists, but found no 
  solution yet. 
  My guess is that is has either something to do with the fact that I'm 
  using 
  MyFaces 1.1.3 or with the fact that the Shale/Clay ValidatorInputRenderer 
  is 
  overwriting the InputSuggestAjax Renderer (something I noticed just now). 
  If the 
  latter is true, what can I do to prevent this? 
 
 
 This is an open JIRA ticket [1].  We need to find a configurable option for 
 specifying components in the javax.faces.Input family that should be 
 excluded from the commons validator renderer decorator.
 
 This looks like a cool component. You might try a workaround.  This is a 
 *complete hack* but I think it should solve this problem.  The trick would 
 be to change the component family and rendererType.
  
  
 [1] https://issues.apache.org/struts/browse/SHALE-442
  
 Consider:
 
 
 // subclass the component overriding the family and renderer type.
 package com.acme.InputSuggestAjax
 public class InputSuggestAjax extends 
 org.apache.myfaces.custom.suggestajax.inputsuggestajax.InputSuggestAjax {
public InputSuggestAjax() {
   setRendererType(com.acme.InputSuggestAjax)
}   
public String getFamily() {
return com.acme.Input;
}
 
 
 }
 
 // register the subclassed component in the /WEB-INF/faces-config.xml
 
   component
 component-typecom.acme.InputSuggestAjax/component-type
 component-classcom.acme.InputSuggestAjax/component-class
   /component
  render-kit
 renderer
   component-familycom.acme.Input/component-family
   renderer-typecom.acme.InputSuggestAjax/renderer-type
   
  renderer-classorg.apache.myfaces.custom.suggestajax.inputsuggestajax.InputSuggestAjaxRenderer/renderer-class
 /renderer
   /render-kit
 
 
 Depending on if you are using JSP, Clay or Facelets you will need some 
 additional setup. 
 
 
 Gary
 
 
 
 
 
 


smime.p7s
Description: S/MIME cryptographic signature


Re: SV: SV: Shale and Sandbox inputSuggestAjax

2007-05-11 Thread Torsten Krah
Hm i got a serious problem:

Using firebug to analyse the response for the 3rd example (using
converter + label) under:

http://www.irian.at/myfaces-sandbox/inputSuggestAjax.jsf

On load the address is show in the field, and the answer on clocking the
arrow is:

[[detroit,nonamestreet,KL,11],[san
diego,maxstreet,SJ,12],[philadelphia,philstreet,NW,13],[new
york,newstreet,IL,14],[san francisco,sanstreet,NY,15],]

Used it with clay, and now i get:

Instead of the detroit ... , the 11 number is shown in the input
field.

The answer of the ajax request is:


[[detroit,nonamestreet,KL,11],[san 
diego,maxstreet,SJ,12],[philadelphia,philstreet,NW,13
],[new york,newstreet,IL,14],[san francisco,sanstreet,NY,15],]


The same.

But no popup for the suggests. No ajax or js error on the debug
console - whats wrong here?

Torsten

Am Freitag, den 11.05.2007, 09:45 +0200 schrieb Torsten Krah:
 Thx - nice work.
 
 Tried it, works so far - method gets called and i get an ajax response.
 But i see no popup in the browser, must have done something wrong ;).
 
 Torsten
 
 
 Am Dienstag, den 08.05.2007, 19:57 +0200 schrieb Hermod Opstvedt:
  Hi
  
  Wiki entry in place.
  
  Hermod
  
  
  -Opprinnelig melding-
  Fra: Erik Govaers [mailto:[EMAIL PROTECTED] 
  Sendt: 8. mai 2007 17:33
  Til: user@shale.apache.org
  Emne: Re: SV: Shale and Sandbox inputSuggestAjax
  
  Hi,
  
  It would be brilliant if you could get us a fix in a couple of days. I'm in 
  an advanced phase of a project and I'm reluctant to let go of either Shale 
  or Tomahawk-Sandbox. And yes, I would welcome a Wiki too.
  
  Thank you,
  
  Erik
  
  
  - Oorspronkelijk bericht -
  Van: Hermod Opstvedt [mailto:[EMAIL PROTECTED]
  Verzonden: dinsdag, mei 8, 2007 05:14 PM
  Aan: user@shale.apache.org
  Onderwerp: SV: Shale and Sandbox inputSuggestAjax
  
  Hi
  
  I have a working setup for Clay on this and if there is an interest I can 
  write a small tutorial on the Wiki.
  
  I am going to start a fix for the Shale-validator which is the cause of 
  this later to day and hopefully it will be done in a day or two.
  
  Hermod
  
  
  -Opprinnelig melding-
  Fra: Gary VanMatre [mailto:[EMAIL PROTECTED] 
  Sendt: 8. mai 2007 16:47
  Til: user@shale.apache.org
  Emne: Re: Shale and Sandbox inputSuggestAjax
  
  From: Erik Govaers [EMAIL PROTECTED] 
  
   Hello, 
   
   I’m trying my hand at a very simple example based on the 
   example at http://www.irian.at/myfaces-sandbox/inputSuggestAjax.jsf. I 
   get an 
   input field, but when I start typing I get no suggestions since my 
   backing bean 
   ‘suggestedItems’ method is never called. I’m using server-side 
   saving, but 
   switching to client-side makes no difference. I’ve looked at a lot of 
   the 
   inputSuggestAjax related issues in the mailing lists, but found no 
   solution yet. 
   My guess is that is has either something to do with the fact that I'm 
   using 
   MyFaces 1.1.3 or with the fact that the Shale/Clay 
   ValidatorInputRenderer is 
   overwriting the InputSuggestAjax Renderer (something I noticed just 
   now). If the 
   latter is true, what can I do to prevent this? 
  
  
  This is an open JIRA ticket [1].  We need to find a configurable option 
  for specifying components in the javax.faces.Input family that should be 
  excluded from the commons validator renderer decorator.
  
  This looks like a cool component. You might try a workaround.  This is a 
  *complete hack* but I think it should solve this problem.  The trick would 
  be to change the component family and rendererType.
   
   
  [1] https://issues.apache.org/struts/browse/SHALE-442
   
  Consider:
  
  
  // subclass the component overriding the family and renderer type.
  package com.acme.InputSuggestAjax
  public class InputSuggestAjax extends 
  org.apache.myfaces.custom.suggestajax.inputsuggestajax.InputSuggestAjax {
 public InputSuggestAjax() {
setRendererType(com.acme.InputSuggestAjax)
 }   
 public String getFamily() {
 return com.acme.Input;
 }
  
  
  }
  
  // register the subclassed component in the /WEB-INF/faces-config.xml
  
component
  component-typecom.acme.InputSuggestAjax/component-type
  component-classcom.acme.InputSuggestAjax/component-class
/component
   render-kit
  renderer
component-familycom.acme.Input/component-family
renderer-typecom.acme.InputSuggestAjax/renderer-type

   renderer-classorg.apache.myfaces.custom.suggestajax.inputsuggestajax.InputSuggestAjaxRenderer/renderer-class
  /renderer
/render-kit
  
  
  Depending on if you are using JSP, Clay or Facelets you will need some 
  additional setup. 
  
  
  Gary
  
  
  
  
  
  


smime.p7s
Description: S/MIME cryptographic signature


Re: Tiles integration - TilesContainer not initialized

2007-05-11 Thread Antonio Petrelli

2007/5/11, Lionel Port [EMAIL PROTECTED]:


tiles-def.xml looks like this:

?xml version=1.0 encoding=ISO-8859-1?
!DOCTYPE tiles-definitions PUBLIC -//Apache Software Foundation//DTD
Tiles Configuration 2.0//EN
http://tiles.apache.org/dtds/tiles-config_2_0.dtd;




The problem is that you use the new DTD for your Tiles definitions file,
while Shale-Tiles uses a version of Tiles where the structure is very
different.
I hope that with Shale 1.0.5 this problem will be resolved (i.e. it will
depend on Tiles 2.0.3).

Antonio