The labels of the fields on the form are dependent one the user's project in
their profile.  So, for example one project needs to enter size data on the
form. 

Project A Size Data is measured in DLOCs 


Project B's Size Data is measured in SLOCs 


DLOCs and SLOCs are the labels for the text fields on the form. 
  


Mike Jasnowski wrote: 


Yes you can make it a variable.  But I'm curious, are the contents of each 
message catalog different? I assume so if you're trying to have each one per

user profile. But what is unique about each profile that requires you to 
have a separate bundle for each? 


Thanks, 
Mike 


-----Original Message----- 
From: Rassmann, Natalie D [mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ] 
Sent: Thursday, June 05, 2003 12:54 PM 
To: Struts Users Mailing List 
Subject: Re: Multiple Message Resource Files 


The bundle is not static....  I am going to change what bundle I use based 
on the users profile (depends on what project they are a member of). 


Mark Galbreath wrote: 


why would you want to?  the bundle is static - it's an absolute reference 


-----Original Message----- 
From: Natalie D Rassmann [mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>  
<mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > ]

Sent: Thursday, June 05, 2003 9:04 AM 
To: Struts Users Mailing List 
Subject: Re: Multiple Message Resource Files 


I suppose I could but can I make that a variable that I can get out of the 
session? 


Mike Jasnowski wrote: 


Can't you just use the "bundle" att on the Struts message tag? 


-----Original Message----- 
From: David Chelimsky [mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>  
<mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > ] 
Sent: Thursday, June 05, 2003 8:55 AM 
To: Struts Users Mailing List 
Subject: Re: Multiple Message Resource Files 


I know that if you're using the jstl tags you can define the bundle in 
the tags. So instead of: 


<bean:message key="some.label"/> 


you'd write: 


<fmt:message bundle="${currentBundle}" key="some.label"/> 


Then you can set the value of currentBundle in your Action based on the 
current project, or store it in the session when the user selects that 
project. In any case, I'm not sure if there's an equivalent in the 
struts bean tags. If not, I'd recommend using the JTSL tags. 


David 


Natalie D Rassmann wrote: 


>Hi, 
> 
>My requirement is to have multiple message resource files not based on 
>Locale but based on the user's project.  For example, 
>I need to create a message bundle for Project A and another one for 
>Project B. 
> 
>MessageResources_ProjectA.properties looks like this: 
> 
>label.first = First Name 
>label.last = Last Name 
> 
>MessageResources_ProjectB properties lookes like this: 
> 
>label.first = First Initial 
>label.last = Last Initial 
> 
>My question is how do I do this?  I believe it works similar to the 
>Struts Internationaliztion capablity where you can set a locale. 
>Is there some kind of variable I can set to distinguish what Project to 
>use? 
> 
>Can anyone point me in the right direction? 
> 
>Thanks in advance, 
> 
>Natalie 
> 
> 
> 
>------------------------------------------------------------------------ 
> 
>--------------------------------------------------------------------- 
>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