RE: taglibs - nonstatic javascript value

[Varun Garg]

The only way I have done that is using straight java <%=%>.

You can definitely do that.

Also, the reason your <%= was not working was that the objects that you
were trying to reference were not declared on you page, but they are
stored in pageContext and cannot be accessed directly.

For using <%= you have define the objects in the scope they will be
used.



-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:45 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


If I decided to pass a dynamic value using javascript in struts tag
libs, it's not doable, right? regardless of using another taglib or not.

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 1:26 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I did not say it is impossible, the thing is that you are trying to use
tag inside tag and that is causing some problems, I am just suggesting a
quick solutions.

Also, when you start getting into custom javascript, you are not really
following struts at that point. 





-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:21 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Yes, thank you.
So, this means that it is impossible to do it with struts taglibs?

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 1:18 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I changes it to use  rather than  and removed the extra ".

You can use the property or not depending on your requirement.



-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:15 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


eliminating "property" doesn't do it!

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:35 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Try this, this should work.

'); document.forms[0].submit(); ">


   

-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 11:23 AM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Varun,

I've tried to put that in, but it still doesn't work:

it cuts it when it comes to those double quotes, so, my href would be =
"javascript:setHiddenLetter('". So, it doesn't like those quotes.

I've tried removing them and putting them in single quotes, I'm back to
that same problem. It reads the whole thing as one string.

Please advice!

Mona

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:06 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I would just put a bean:write instead on the D.



"'); document.forms[0].submit(); ">


   
-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 10:50 AM
To: 'Struts Users Mailing List'
Subject: taglibs - nonstatic javascript value




yes, it worked.

I have one problem, though: passing dynamic value to the function I call
in javascript.

This is what I have:




   

I would like to replace that 'D' with something like <%=choice%>, for
the user to be able to select the letter (there are letter A through Z,
and 'letter' is a hidden field).

How can I do that?

Mona 

-Original Message-
From: Lynn Guy [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 4:35 PM
To: Struts Users Mailing List
Subject: RE: first time action


put them in an html form tag
then in your link do something like
onclick=this.submit()

function doInsert() {
 document.forms[0].submit();
}


  

  
   

I think the name property for the html:form tag is no
longer valid so forms[0] refers to the first form on
my page.

In your case you can probably use the html:link tag
and put the javascript call in the onclick property.

hth



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in 

RE: taglibs - nonstatic javascript value

[Alawadhi, Mona]

If I decided to pass a dynamic value using javascript in struts tag libs,
it's not doable, right? regardless of using another taglib or not.

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 1:26 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I did not say it is impossible, the thing is that you are trying to use
tag inside tag and that is causing some problems, I am just suggesting a
quick solutions.

Also, when you start getting into custom javascript, you are not really
following struts at that point. 





-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:21 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Yes, thank you.
So, this means that it is impossible to do it with struts taglibs?

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 1:18 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I changes it to use  rather than  and removed the extra ".

You can use the property or not depending on your requirement.



-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:15 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


eliminating "property" doesn't do it!

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:35 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Try this, this should work.

'); document.forms[0].submit(); ">


   

-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 11:23 AM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Varun,

I've tried to put that in, but it still doesn't work:

it cuts it when it comes to those double quotes, so, my href would be =
"javascript:setHiddenLetter('". So, it doesn't like those quotes.

I've tried removing them and putting them in single quotes, I'm back to
that same problem. It reads the whole thing as one string.

Please advice!

Mona

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:06 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I would just put a bean:write instead on the D.



"'); document.forms[0].submit(); ">


   
-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 10:50 AM
To: 'Struts Users Mailing List'
Subject: taglibs - nonstatic javascript value




yes, it worked.

I have one problem, though: passing dynamic value to the function I call
in javascript.

This is what I have:




   

I would like to replace that 'D' with something like <%=choice%>, for
the user to be able to select the letter (there are letter A through Z,
and 'letter' is a hidden field).

How can I do that?

Mona 

-Original Message-
From: Lynn Guy [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 4:35 PM
To: Struts Users Mailing List
Subject: RE: first time action


put them in an html form tag
then in your link do something like
onclick=this.submit()

function doInsert() {
 document.forms[0].submit();
}


  

  
   

I think the name property for the html:form tag is no
longer valid so forms[0] refers to the first form on
my page.

In your case you can probably use the html:link tag
and put the javascript call in the onclick property.

hth



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on
it, is prohibited and may be unlawful. When addressed to our clients any
opinions or advice contained in this email are subject to the terms and
conditions expressed in
the governing KPMG client engagement letter. 

*


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EM

RE: taglibs - nonstatic javascript value

[Varun Garg]

I did not say it is impossible, the thing is that you are trying to use
tag inside tag and that is causing some problems, I am just suggesting a
quick solutions.

Also, when you start getting into custom javascript, you are not really
following struts at that point. 





-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:21 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Yes, thank you.
So, this means that it is impossible to do it with struts taglibs?

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 1:18 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I changes it to use  rather than  and removed the extra ".

You can use the property or not depending on your requirement.



-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:15 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


eliminating "property" doesn't do it!

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:35 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Try this, this should work.

'); document.forms[0].submit(); ">


   

-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 11:23 AM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Varun,

I've tried to put that in, but it still doesn't work:

it cuts it when it comes to those double quotes, so, my href would be =
"javascript:setHiddenLetter('". So, it doesn't like those quotes.

I've tried removing them and putting them in single quotes, I'm back to
that same problem. It reads the whole thing as one string.

Please advice!

Mona

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:06 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I would just put a bean:write instead on the D.



"'); document.forms[0].submit(); ">


   
-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 10:50 AM
To: 'Struts Users Mailing List'
Subject: taglibs - nonstatic javascript value




yes, it worked.

I have one problem, though: passing dynamic value to the function I call
in javascript.

This is what I have:




   

I would like to replace that 'D' with something like <%=choice%>, for
the user to be able to select the letter (there are letter A through Z,
and 'letter' is a hidden field).

How can I do that?

Mona 

-Original Message-
From: Lynn Guy [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 4:35 PM
To: Struts Users Mailing List
Subject: RE: first time action


put them in an html form tag
then in your link do something like
onclick=this.submit()

function doInsert() {
 document.forms[0].submit();
}


  

  
   

I think the name property for the html:form tag is no
longer valid so forms[0] refers to the first form on
my page.

In your case you can probably use the html:link tag
and put the javascript call in the onclick property.

hth



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on
it, is prohibited and may be unlawful. When addressed to our clients any
opinions or advice contained in this email are subject to the terms and
conditions expressed in
the governing KPMG client engagement letter. 

*


-
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]



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any acti

RE: taglibs - nonstatic javascript value

[Alawadhi, Mona]

Yes, thank you.
So, this means that it is impossible to do it with struts taglibs?

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 1:18 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I changes it to use  rather than  and removed the extra ".

You can use the property or not depending on your requirement.



-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:15 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


eliminating "property" doesn't do it!

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:35 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Try this, this should work.

'); document.forms[0].submit(); ">


   

-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 11:23 AM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Varun,

I've tried to put that in, but it still doesn't work:

it cuts it when it comes to those double quotes, so, my href would be =
"javascript:setHiddenLetter('". So, it doesn't like those quotes.

I've tried removing them and putting them in single quotes, I'm back to
that same problem. It reads the whole thing as one string.

Please advice!

Mona

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:06 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I would just put a bean:write instead on the D.



"'); document.forms[0].submit(); ">


   
-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 10:50 AM
To: 'Struts Users Mailing List'
Subject: taglibs - nonstatic javascript value




yes, it worked.

I have one problem, though: passing dynamic value to the function I call
in javascript.

This is what I have:




   

I would like to replace that 'D' with something like <%=choice%>, for
the user to be able to select the letter (there are letter A through Z,
and 'letter' is a hidden field).

How can I do that?

Mona 

-Original Message-
From: Lynn Guy [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 4:35 PM
To: Struts Users Mailing List
Subject: RE: first time action


put them in an html form tag
then in your link do something like
onclick=this.submit()

function doInsert() {
 document.forms[0].submit();
}


  

  
   

I think the name property for the html:form tag is no
longer valid so forms[0] refers to the first form on
my page.

In your case you can probably use the html:link tag
and put the javascript call in the onclick property.

hth



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on
it, is prohibited and may be unlawful. When addressed to our clients any
opinions or advice contained in this email are subject to the terms and
conditions expressed in
the governing KPMG client engagement letter. 

*


-
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]



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on
it, is prohibited and may be unlawful. When addressed to our clients any
opinions or advice contained in this email are subject to the terms and
conditions expressed in
the governing KPMG client engagement letter. 

*


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional 

RE: taglibs - nonstatic javascript value

[Varun Garg]

I changes it to use  rather than  and removed the extra ".

You can use the property or not depending on your requirement.



-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:15 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


eliminating "property" doesn't do it!

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:35 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Try this, this should work.

'); document.forms[0].submit(); ">


   

-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 11:23 AM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Varun,

I've tried to put that in, but it still doesn't work:

it cuts it when it comes to those double quotes, so, my href would be =
"javascript:setHiddenLetter('". So, it doesn't like those quotes.

I've tried removing them and putting them in single quotes, I'm back to
that same problem. It reads the whole thing as one string.

Please advice!

Mona

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:06 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I would just put a bean:write instead on the D.



"'); document.forms[0].submit(); ">


   
-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 10:50 AM
To: 'Struts Users Mailing List'
Subject: taglibs - nonstatic javascript value




yes, it worked.

I have one problem, though: passing dynamic value to the function I call
in javascript.

This is what I have:




   

I would like to replace that 'D' with something like <%=choice%>, for
the user to be able to select the letter (there are letter A through Z,
and 'letter' is a hidden field).

How can I do that?

Mona 

-Original Message-
From: Lynn Guy [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 4:35 PM
To: Struts Users Mailing List
Subject: RE: first time action


put them in an html form tag
then in your link do something like
onclick=this.submit()

function doInsert() {
 document.forms[0].submit();
}


  

  
   

I think the name property for the html:form tag is no
longer valid so forms[0] refers to the first form on
my page.

In your case you can probably use the html:link tag
and put the javascript call in the onclick property.

hth



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on
it, is prohibited and may be unlawful. When addressed to our clients any
opinions or advice contained in this email are subject to the terms and
conditions expressed in
the governing KPMG client engagement letter. 

*


-
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]



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on
it, is prohibited and may be unlawful. When addressed to our clients any
opinions or advice contained in this email are subject to the terms and
conditions expressed in
the governing KPMG client engagement letter. 

*


-
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]



*
Th

RE: taglibs - nonstatic javascript value

[Alawadhi, Mona]

eliminating "property" doesn't do it!

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:35 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Try this, this should work.

'); document.forms[0].submit(); ">


   

-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 11:23 AM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Varun,

I've tried to put that in, but it still doesn't work:

it cuts it when it comes to those double quotes, so, my href would be =
"javascript:setHiddenLetter('". So, it doesn't like those quotes.

I've tried removing them and putting them in single quotes, I'm back to
that same problem. It reads the whole thing as one string.

Please advice!

Mona

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:06 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I would just put a bean:write instead on the D.



"'); document.forms[0].submit(); ">


   
-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 10:50 AM
To: 'Struts Users Mailing List'
Subject: taglibs - nonstatic javascript value




yes, it worked.

I have one problem, though: passing dynamic value to the function I call
in javascript.

This is what I have:




   

I would like to replace that 'D' with something like <%=choice%>, for
the user to be able to select the letter (there are letter A through Z,
and 'letter' is a hidden field).

How can I do that?

Mona 

-Original Message-
From: Lynn Guy [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 4:35 PM
To: Struts Users Mailing List
Subject: RE: first time action


put them in an html form tag
then in your link do something like
onclick=this.submit()

function doInsert() {
 document.forms[0].submit();
}


  

  
   

I think the name property for the html:form tag is no
longer valid so forms[0] refers to the first form on
my page.

In your case you can probably use the html:link tag
and put the javascript call in the onclick property.

hth



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on
it, is prohibited and may be unlawful. When addressed to our clients any
opinions or advice contained in this email are subject to the terms and
conditions expressed in
the governing KPMG client engagement letter. 

*


-
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]



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on
it, is prohibited and may be unlawful. When addressed to our clients any
opinions or advice contained in this email are subject to the terms and
conditions expressed in
the governing KPMG client engagement letter. 

*


-
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]


*
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawf

RE: taglibs - nonstatic javascript value

[Varun Garg]

Try this, this should work.

'); document.forms[0].submit(); ">


   

-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 11:23 AM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


Varun,

I've tried to put that in, but it still doesn't work:

it cuts it when it comes to those double quotes, so, my href would be =
"javascript:setHiddenLetter('". So, it doesn't like those quotes.

I've tried removing them and putting them in single quotes, I'm back to
that same problem. It reads the whole thing as one string.

Please advice!

Mona

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:06 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I would just put a bean:write instead on the D.



"'); document.forms[0].submit(); ">


   
-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 10:50 AM
To: 'Struts Users Mailing List'
Subject: taglibs - nonstatic javascript value




yes, it worked.

I have one problem, though: passing dynamic value to the function I call
in javascript.

This is what I have:




   

I would like to replace that 'D' with something like <%=choice%>, for
the user to be able to select the letter (there are letter A through Z,
and 'letter' is a hidden field).

How can I do that?

Mona 

-Original Message-
From: Lynn Guy [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 4:35 PM
To: Struts Users Mailing List
Subject: RE: first time action


put them in an html form tag
then in your link do something like
onclick=this.submit()

function doInsert() {
 document.forms[0].submit();
}


  

  
   

I think the name property for the html:form tag is no
longer valid so forms[0] refers to the first form on
my page.

In your case you can probably use the html:link tag
and put the javascript call in the onclick property.

hth



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on
it, is prohibited and may be unlawful. When addressed to our clients any
opinions or advice contained in this email are subject to the terms and
conditions expressed in
the governing KPMG client engagement letter. 

*


-
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]



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on
it, is prohibited and may be unlawful. When addressed to our clients any
opinions or advice contained in this email are subject to the terms and
conditions expressed in
the governing KPMG client engagement letter. 

*


-
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]

RE: taglibs - nonstatic javascript value

[Alawadhi, Mona]

Varun,

I've tried to put that in, but it still doesn't work:

it cuts it when it comes to those double quotes, so, my href would be =
"javascript:setHiddenLetter('".
So, it doesn't like those quotes.

I've tried removing them and putting them in single quotes, I'm back to that
same problem. It reads the whole thing as one string.

Please advice!

Mona

-Original Message-
From: Varun Garg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:06 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


I would just put a bean:write instead on the D.



"');
document.forms[0].submit(); ">


   
-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 10:50 AM
To: 'Struts Users Mailing List'
Subject: taglibs - nonstatic javascript value




yes, it worked.

I have one problem, though: passing dynamic value to the function I call
in javascript.

This is what I have:




   

I would like to replace that 'D' with something like <%=choice%>, for
the user to be able to select the letter (there are letter A through Z,
and 'letter' is a hidden field).

How can I do that?

Mona 

-Original Message-
From: Lynn Guy [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 4:35 PM
To: Struts Users Mailing List
Subject: RE: first time action


put them in an html form tag
then in your link do something like
onclick=this.submit()

function doInsert() {
 document.forms[0].submit();
}


  

  
   

I think the name property for the html:form tag is no
longer valid so forms[0] refers to the first form on
my page.

In your case you can probably use the html:link tag
and put the javascript call in the onclick property.

hth



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on
it, is prohibited and may be unlawful. When addressed to our clients any
opinions or advice contained in this email are subject to the terms and
conditions expressed in
the governing KPMG client engagement letter. 

*


-
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]


*
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter. 
*


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: taglibs - nonstatic javascript value

[Alawadhi, Mona]

Panchasheel,

I've tried it. It doesn't work. It takes '<%=choice.toString()%>' as a whole
string, it does not replace it by the letter I want.

Actually, if you write this, and try to hover over the link, you will see:
'javascript:setHiddenletter('<%choice.toString()%>')' 
INSTEAD OF 
'javascript:setHiddenletter('D')' or
'javascript:setHiddenletter('A')' or something.

I am not sure how I can trick struts to capture the dynamic value, not
hardcode it.

Anyone can help?

Mona

-Original Message-
From: Gandle, Panchasheel [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:02 PM
To: 'Struts Users Mailing List'
Subject: RE: taglibs - nonstatic javascript value


This should work




   

Panchasheel



-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 11:50 AM
To: 'Struts Users Mailing List'
Subject: taglibs - nonstatic javascript value




yes, it worked.

I have one problem, though: passing dynamic value to the function I call in
javascript.

This is what I have:




   

I would like to replace that 'D' with something like <%=choice%>, for the
user to be able to select the letter (there are letter A through Z, and
'letter' is a hidden field).

How can I do that?

Mona 

-Original Message-
From: Lynn Guy [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 4:35 PM
To: Struts Users Mailing List
Subject: RE: first time action


put them in an html form tag
then in your link do something like
onclick=this.submit()

function doInsert() {
 document.forms[0].submit();
}


  

  
   

I think the name property for the html:form tag is no
longer valid so forms[0] refers to the first form on
my page.

In your case you can probably use the html:link tag
and put the javascript call in the onclick property.

hth



*
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter. 

*


-
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]


*
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter. 
*


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: taglibs - nonstatic javascript value

[Varun Garg]

I would just put a bean:write instead on the D.



"');
document.forms[0].submit(); ">


   
-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 10:50 AM
To: 'Struts Users Mailing List'
Subject: taglibs - nonstatic javascript value




yes, it worked.

I have one problem, though: passing dynamic value to the function I call
in javascript.

This is what I have:




   

I would like to replace that 'D' with something like <%=choice%>, for
the user to be able to select the letter (there are letter A through Z,
and 'letter' is a hidden field).

How can I do that?

Mona 

-Original Message-
From: Lynn Guy [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 4:35 PM
To: Struts Users Mailing List
Subject: RE: first time action


put them in an html form tag
then in your link do something like
onclick=this.submit()

function doInsert() {
 document.forms[0].submit();
}


  

  
   

I think the name property for the html:form tag is no
longer valid so forms[0] refers to the first form on
my page.

In your case you can probably use the html:link tag
and put the javascript call in the onclick property.

hth



*
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. 

If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on
it, is prohibited and may be unlawful. When addressed to our clients any
opinions or advice contained in this email are subject to the terms and
conditions expressed in
the governing KPMG client engagement letter. 

*


-
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]

RE: taglibs - nonstatic javascript value

[Gandle, Panchasheel]

This should work




   

Panchasheel



-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 11:50 AM
To: 'Struts Users Mailing List'
Subject: taglibs - nonstatic javascript value




yes, it worked.

I have one problem, though: passing dynamic value to the function I call in
javascript.

This is what I have:




   

I would like to replace that 'D' with something like <%=choice%>, for the
user to be able to select the letter (there are letter A through Z, and
'letter' is a hidden field).

How can I do that?

Mona 

-Original Message-
From: Lynn Guy [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 4:35 PM
To: Struts Users Mailing List
Subject: RE: first time action


put them in an html form tag
then in your link do something like
onclick=this.submit()

function doInsert() {
 document.forms[0].submit();
}


  

  
   

I think the name property for the html:form tag is no
longer valid so forms[0] refers to the first form on
my page.

In your case you can probably use the html:link tag
and put the javascript call in the onclick property.

hth



*
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter. 

*


-
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]

RE: [taglibs] Create a custom tag that uses struts HTML tags?

[James Mitchell]

Could you explain this a bit further.

I've written a few tags myself, but I'm not exactly sure what you are trying
to do.



James Mitchell
Software Engineer\Struts Evangelist
Struts-Atlanta, the "Open Minded Developer Network"
http://www.open-tools.org/struts-atlanta




> -Original Message-
> From: John Averty [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 30, 2002 5:06 PM
> To: [EMAIL PROTECTED]
> Subject: Create a custom tag that uses struts HTML tags?
>
>
> Hi,
>
> I'm a new struts user, and I couldn't find any information that helped;
>
> I'd like to create a custom tag which represents a
> super-componant such as a "properties list" tag.
>
> The idea would be to:
> 1) dynamically specify which fields to be renderered
> 2) at the same time ensure that the rendering of such list of
> properties is consistant accross different pages of the
> application, without having to rely on "low level" HTML (such as
> tables, etc) on each page.
>
> So the question is:
>
> How can I reference Struts tags from withing my tag
>  - without having to put a lot of snipet code in the jsp page
> (I'd like just the tag and a definition name)
>  - still having the struts built-in validations mechanism work.
>
> I'm assuming I might be able to get to the struts tags by some
> sort of introspecion mechanism, but I'm not clear on how to have
> the validation perform.
>
> Any help grandly apprecitated.
>
> Chheers,
>
> John.
>


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: taglibs documentation (whered it go)?

[Ted Husted]

For the nightly build, the Taglib document been moved into the User
Guide.

If possible, please install the documentation locally from the
struts-documentation.war in the distributions. 
(OK, not the distributions since Tuesday, but you know what I mean.)

-- Ted Husted, Husted dot Com, Fairport NY US
-- Developing Java Web Applications with Struts
-- Tel: +1 585 737-3463
-- Web: http://husted.com/about/services

rob wrote:
> 
> Where did the taglibs documentation go on the struts page?  Used to be
> accessed via the taglibs link under Stable Release.  The javadoc is less
> indicitive of how the tags work.
> 
> Thanks
> 
> Rob
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: taglibs documentation (whered it go)?

[Konstantina Stamopoulou]

Hello,
The tag lib documentation is now accessible trough the link "Release Notes".
I realized that yesterday!

cheers,
Konstantina


- Original Message -
From: "keithBacon" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>; "rob"
<[EMAIL PROTECTED]>
Sent: Thursday, February 21, 2002 11:51 AM
Subject: Re: taglibs documentation (whered it go)?


> so that why i couldn't find it! Please can we have it back pronto!
>
> =
> ~~
> Search the archive:-
> http://www.mail-archive.com/struts-user%40jakarta.apache.org/
> ~~
> Keith Bacon - Looking for struts work - South-East UK.
> phone UK 07960 011275
>
> __
> Do You Yahoo!?
> Yahoo! Sports - Coverage of the 2002 Olympic Games
> http://sports.yahoo.com
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: taglibs documentation (whered it go)?

[keithBacon]

so that why i couldn't find it! Please can we have it back pronto!

=
~~
Search the archive:-
http://www.mail-archive.com/struts-user%40jakarta.apache.org/
~~
Keith Bacon - Looking for struts work - South-East UK.
phone UK 07960 011275

__
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: taglibs and jsp:include

[Cedric Dumoulin]

  Hi,

  Have you check Tiles library ? Maybe it already provides what you need ...

Cedric

Martin Samm wrote:

> this is not directly Struts but seemed the best qualified forum (it is for a
> struts based app however).
> I'm using a custom tag to decide which jsp to include (based on some request
> variables) - the tag then uses a JSP writer to create the  -
> trouble is the ' tag is just written out and not 'interpretted',
> i.e. the page isn't included. How do i get the container to interpret the
> include?
> --
> Martin Samm
> [EMAIL PROTECTED]
>
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: taglibs and jsp:include

[Martin Samm]

thats great, thanks very much

On Monday 03 Dec 2001 6:29 pm, you wrote:
> > "Martin" == Martin Samm <[EMAIL PROTECTED]> writes:
>
> Martin> this is not directly Struts but seemed the best qualified forum
> (it is for a Martin> struts based app however).
> Martin> I'm using a custom tag to decide which jsp to include (based on
> some request Martin> variables) - the tag then uses a JSP writer to create
> the  - Martin> trouble is the ' tag is just
> written out and not 'interpretted', Martin> i.e. the page isn't included.
> How do i get the container to interpret the Martin> include?
>
> Generating " include mechanism, using a variation of "RequestDispatcher.include()".

-- 
Martin Samm
[EMAIL PROTECTED]

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: taglibs and jsp:include

[David M. Karr]

> "Martin" == Martin Samm <[EMAIL PROTECTED]> writes:

Martin> this is not directly Struts but seemed the best qualified forum (it is for 
a 
Martin> struts based app however). 
Martin> I'm using a custom tag to decide which jsp to include (based on some 
request 
Martin> variables) - the tag then uses a JSP writer to create the  - 
Martin> trouble is the ' tag is just written out and not 
'interpretted', 
Martin> i.e. the page isn't included. How do i get the container to interpret the 
Martin> include?

Generating "mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: 

Re: taglibs and jsp:include

[John Ng]

Try to use template.  Struts template can do exactly
what you want to.  
--- Martin Samm <[EMAIL PROTECTED]> wrote:
> this is not directly Struts but seemed the best
> qualified forum (it is for a 
> struts based app however). 
> I'm using a custom tag to decide which jsp to
> include (based on some request 
> variables) - the tag then uses a JSP writer to
> create the  - 
> trouble is the ' tag is just written
> out and not 'interpretted', 
> i.e. the page isn't included. How do i get the
> container to interpret the 
> include?
> -- 
> Martin Samm
> [EMAIL PROTECTED]
> 
> --
> To unsubscribe, e-mail:  
> 
> For additional commands, e-mail:
> 
> 


__
Do You Yahoo!?
Buy the perfect holiday gifts at Yahoo! Shopping.
http://shopping.yahoo.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: custom XSL struts taglib (was: Re: Taglibs decrease theseparation between designer and developer?)

[Jon Brisbin]

> Jakarta TagLibs also have a taglib that does XSL, have you thought about
> merging your result with theirs?

no, but that's certainly an idea...i wanted a little bit different approach
than the jakarta taglib, so i just rolled my own...

> What I think is the big disadvantage with using XSL it is very complex
> to use, especially if you want to take advantage of its more powerful
> features.  If designers are going to have problems understanding
> scriplets and velocity, they're not going to fair much better with XSL
> (probably worse, in fact).

although this might be true now, wysiwyg XSL editors are coming into being
as we speak (the ibm xsl editor is actually pretty neat :-)...the XML/XSL
approach and structure is why i prefer it over scriplets or custom
tags...the whole XML/XSL approach is very OO-centric, where scriptlets or
custom iterative tags are basically hold-overs from structured programming
days...of course, if it ain't broke, yada, yada ;-)

i also find a smaller code size for the same functions, as well as faster
performance in using limited xsl for certain things...especially for ejb
stuff that iterates over records...wow, a big difference ;-)

xml/xsl also makes my EJB infrastructure much more open, as i can request
the data any number of ways and use it in disparate systems and in multiple
instances, without having to code special taglibs for various things...just
a big template file with lots of little stuff in it seems easier to manage
for me than taglib classes, .tld files, etc...

> One good thing about having model data as XML, however, is that you can
> utilize the xpath to access the XML data if you don't need all the bells
> and whistles of XSL

actually i like all the bells and whistles ;-)...

it ain't for everyone, but XSL seems much closer to something my designers
in the past have understood easily...they're more intimidated when they see
a lot of '%' signs ;-)  i also off-load some work from myself by using xsl
instead of taglibs, as a java programmer doesn't have to do that
part...anyone that knows xml and xsl can do that...

Jon Brisbin
www.jbrisbin.net

Re: custom XSL struts taglib (was: Re: Taglibs decrease theseparation between designer and developer?)

[Calvin Yu]

Jakarta TagLibs also have a taglib that does XSL, have you thought about
merging your result with theirs?

What I think is the big disadvantage with using XSL it is very complex
to use, especially if you want to take advantage of its more powerful
features.  If designers are going to have problems understanding
scriplets and velocity, they're not going to fair much better with XSL
(probably worse, in fact).

One good thing about having model data as XML, however, is that you can
utilize the xpath to access the XML data if you don't need all the bells
and whistles of XSL (fortunately Jakarta TagLib also provides a taglib
that does this).

Calvin


On 01 Aug 2001 16:10:02 -0500, Jon Brisbin wrote:
> Thought I'd put a plug in for my own custom XSL taglib I use in my STRUTS
> apps...it helps me clean up the whole scriplet/custom tag thing by letting
> me use plain 'ol XSLT templates to output my forms with pre-filled values,
> etc...from my EJB's...i also use the struts form tags and a custom property
> copier that copies things from my ejb to my form, but this is considerably
> slower than using my session bean to extract raw xml from a sql statement,
> then transform it into a list or form...
> 
> this XSL tag caches the compiled stylesheet into the application scope,
> keyed on the filename...this to increase performance, which it does well...
> 
> you can nest xml tags and scriptlets in the body of the tag to get dynamic
> xml (you could theoretically do a full page of xml this way, with no HTML
> whatever...i just haven't migrated that far yet to have my app do that), or
> you can get your xml from an attribute...and transform *into* an attribute,
> if you wish...
> 
> i'm quite pleased with the results of incorporating my xsl into struts this
> way...this might also help some out there that would like to try it
> too...email me if you want the source code and .tld file...
> 
> Jon Brisbin
> www.jbrisbin.net
> Lamar, MO
> 
> - Original Message -
> From: "Greg Maletic" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, August 01, 2001 3:07 PM
> Subject: RE: Taglibs decrease the separation between designer and developer?
> 
> 
> > Hi, Bill--
> >
> > I completely agree that Struts Taglibs are much cleaner than the pure HTML
> > alternative, so I concur that your "select box" example is very simple and
> > nice.  I love all of the Struts form input tags, all of which are a real
> > pain to implement with pure HTML and JSP.
> >
> > But I don't think I'm exaggerating very much when I say that the Struts
> > taglibs are a new language:  they include tags to define variables,
> looping
> > constructs, and if-then-else constructs, none of which correspond to
> actual
> > HTML tags, and all of which I'll need to employ if I'm to completely rid
> my
> > JSPs of scriptlets.  I view that as pretty much a complete language.  So
> my
> > novice reaction to the Struts taglibs is that I've swapped a language that
> I
> > know (Java) for a language that I don't know (Struts taglibs), and my
> > designer has swapped a language that he knows (pure HTML) for a language
> he
> > doesn't know (Struts taglibs), at the benefit of giving the designer the
> > potential to write virtual code when I know that he--and at least 95% of
> the
> > designers I've worked with--won't write view code that I would trust no
> > matter what the language is.  (I'm not claiming they're stupid.  My
> > experience has been similar to Chris's earlier post, where I let them
> > control the look and feel and I write the view code.)
> >
> > I'm not saying that the Struts taglibs are useless by any stretch of the
> > imagination.  But the real benefit I see with taglibs is to clean up the
> > JSPs, not usher in a new age of empowered designers capable of building
> > views with no developer assistance.
> >
> > I should have prefaced my comments by saying that I'm quite new to Struts,
> > am not an expert, so my comments should be taken in that light.  I am
> > impressed with Struts and am absolutely not giving up on it.  My beef
> isn't
> > so much with Struts as it is with the whole concept of taglibs being "the
> > solution" to the MVC separation problem.  The only solution to this
> problem
> > is to keep business logic out of the view, period.  Scriptlets don't solve
> > the problem, but I don't think taglibs do either.  The only real solution
> I
> > see is developer restraint.
> >
> > --Greg
> >
> > =

custom XSL struts taglib (was: Re: Taglibs decrease the separation between designer and developer?)

[Jon Brisbin]

Thought I'd put a plug in for my own custom XSL taglib I use in my STRUTS
apps...it helps me clean up the whole scriplet/custom tag thing by letting
me use plain 'ol XSLT templates to output my forms with pre-filled values,
etc...from my EJB's...i also use the struts form tags and a custom property
copier that copies things from my ejb to my form, but this is considerably
slower than using my session bean to extract raw xml from a sql statement,
then transform it into a list or form...

this XSL tag caches the compiled stylesheet into the application scope,
keyed on the filename...this to increase performance, which it does well...

you can nest xml tags and scriptlets in the body of the tag to get dynamic
xml (you could theoretically do a full page of xml this way, with no HTML
whatever...i just haven't migrated that far yet to have my app do that), or
you can get your xml from an attribute...and transform *into* an attribute,
if you wish...

i'm quite pleased with the results of incorporating my xsl into struts this
way...this might also help some out there that would like to try it
too...email me if you want the source code and .tld file...

Jon Brisbin
www.jbrisbin.net
Lamar, MO

- Original Message -
From: "Greg Maletic" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 01, 2001 3:07 PM
Subject: RE: Taglibs decrease the separation between designer and developer?


> Hi, Bill--
>
> I completely agree that Struts Taglibs are much cleaner than the pure HTML
> alternative, so I concur that your "select box" example is very simple and
> nice.  I love all of the Struts form input tags, all of which are a real
> pain to implement with pure HTML and JSP.
>
> But I don't think I'm exaggerating very much when I say that the Struts
> taglibs are a new language:  they include tags to define variables,
looping
> constructs, and if-then-else constructs, none of which correspond to
actual
> HTML tags, and all of which I'll need to employ if I'm to completely rid
my
> JSPs of scriptlets.  I view that as pretty much a complete language.  So
my
> novice reaction to the Struts taglibs is that I've swapped a language that
I
> know (Java) for a language that I don't know (Struts taglibs), and my
> designer has swapped a language that he knows (pure HTML) for a language
he
> doesn't know (Struts taglibs), at the benefit of giving the designer the
> potential to write virtual code when I know that he--and at least 95% of
the
> designers I've worked with--won't write view code that I would trust no
> matter what the language is.  (I'm not claiming they're stupid.  My
> experience has been similar to Chris's earlier post, where I let them
> control the look and feel and I write the view code.)
>
> I'm not saying that the Struts taglibs are useless by any stretch of the
> imagination.  But the real benefit I see with taglibs is to clean up the
> JSPs, not usher in a new age of empowered designers capable of building
> views with no developer assistance.
>
> I should have prefaced my comments by saying that I'm quite new to Struts,
> am not an expert, so my comments should be taken in that light.  I am
> impressed with Struts and am absolutely not giving up on it.  My beef
isn't
> so much with Struts as it is with the whole concept of taglibs being "the
> solution" to the MVC separation problem.  The only solution to this
problem
> is to keep business logic out of the view, period.  Scriptlets don't solve
> the problem, but I don't think taglibs do either.  The only real solution
I
> see is developer restraint.
>
> --Greg
>
> ==
> Greg Maletic
> Chief Technical Officer
> Zero G Software, Inc.
> 514 Bryant Street
> San Francisco, CA 94107
>
> tel: +1.415.512.7771 x303
> fax: +1.415.723.7244
> mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> http://www.ZeroG.com <http://www.ZeroG.com>
>
> The leading provider of multi-platform software deployment solutions.
> ==
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> rg]On Behalf Of Bill Clinton
> Sent: Wednesday, August 01, 2001 12:10 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Taglibs decrease the separation between designer and
> developer?
>
>
> Greg,
> I think you are exagerating a bit when you say that "Struts
> taglibs--and other taglibs--introduce, in essence, yet another language
> that we all have to learn."  Comparing a handful of scripting tags that,
> for the most part, correspond directly to existing html tags to the
> learning of a language is a bit much.
>

Re: Taglibs decrease the separation between designer and developer?

[Ted Husted]

Bill Clinton wrote:
> The line between designer and developer is a blurry one and differs
> in most organizations.  But in my last few postions, my experience has
> been that HTML proficiency is no longer a given for web designers.
> Macromedia Dreamweaver seems to be the tool of choice for most designers
> these days, and HTML skills seems to take a back seat to skills in
> Photoshop, Flash, Dreamweaver, gif animation, etc.

And here lies the rub: 

As GUI JSP Tag extensions like 

< http://jakarta.apache.org/taglibs/doc/ultradev4-doc/intro.html >

come of age, the Struts tags, and other libraries, start to plug right
into the WYSIWYG environment. Programming a custom tag then becomes no
different for a designer than programming an ordinary HTML tag. 

If someone hasn't taken DreamWeaver UltraDev for a test-drive, you
should treat yourself. It's a real eye opener as to what can happen when
all this comes together.

I like to think of Struts as having been designed "twenty minutes into
the future". It's not only a framework for where we are, it's a
framework for where we are going ;-)

-Ted.

RE: Taglibs decrease the separation between designer and developer?

[Greg Maletic]

Hi, Bill--

I completely agree that Struts Taglibs are much cleaner than the pure HTML
alternative, so I concur that your "select box" example is very simple and
nice.  I love all of the Struts form input tags, all of which are a real
pain to implement with pure HTML and JSP.

But I don't think I'm exaggerating very much when I say that the Struts
taglibs are a new language:  they include tags to define variables, looping
constructs, and if-then-else constructs, none of which correspond to actual
HTML tags, and all of which I'll need to employ if I'm to completely rid my
JSPs of scriptlets.  I view that as pretty much a complete language.  So my
novice reaction to the Struts taglibs is that I've swapped a language that I
know (Java) for a language that I don't know (Struts taglibs), and my
designer has swapped a language that he knows (pure HTML) for a language he
doesn't know (Struts taglibs), at the benefit of giving the designer the
potential to write virtual code when I know that he--and at least 95% of the
designers I've worked with--won't write view code that I would trust no
matter what the language is.  (I'm not claiming they're stupid.  My
experience has been similar to Chris's earlier post, where I let them
control the look and feel and I write the view code.)

I'm not saying that the Struts taglibs are useless by any stretch of the
imagination.  But the real benefit I see with taglibs is to clean up the
JSPs, not usher in a new age of empowered designers capable of building
views with no developer assistance.

I should have prefaced my comments by saying that I'm quite new to Struts,
am not an expert, so my comments should be taken in that light.  I am
impressed with Struts and am absolutely not giving up on it.  My beef isn't
so much with Struts as it is with the whole concept of taglibs being "the
solution" to the MVC separation problem.  The only solution to this problem
is to keep business logic out of the view, period.  Scriptlets don't solve
the problem, but I don't think taglibs do either.  The only real solution I
see is developer restraint.

--Greg

==
Greg Maletic
Chief Technical Officer
Zero G Software, Inc.
514 Bryant Street
San Francisco, CA 94107

tel: +1.415.512.7771 x303
fax: +1.415.723.7244
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
http://www.ZeroG.com <http://www.ZeroG.com>

The leading provider of multi-platform software deployment solutions.
==
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
rg]On Behalf Of Bill Clinton
Sent: Wednesday, August 01, 2001 12:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Taglibs decrease the separation between designer and
developer?


Greg,
I think you are exagerating a bit when you say that "Struts
taglibs--and other taglibs--introduce, in essence, yet another language
that we all have to learn."  Comparing a handful of scripting tags that,
for the most part, correspond directly to existing html tags to the
learning of a language is a bit much.
That said, if your designer is unable to understand struts tags, I
would recommend that you ask him not to touch them.  I don't understand
why you would feel the need to teach a designer "the ins and outs" of
Struts tags.  Maybe you could try something like this: design the app,
using completely stripped jsp pages.  Ask your designer to do the
interface, then put the tags in his interface.  If the designer needs
control of the presentation of html contained within custom tags, use
style sheets.
Also, if you honestly do feel that things were easier without
struts, don't use it.  It is not a part of the servlet/jsp spec or
anything, and its use is completely optional.  But I would urge you to
stick with it a little more.  I think its many advantages far outweigh
the small learning curve.

One more thing, since you have experience with servlets/jsp, you
must admit that code for a select box that looks like this is a thing of
beauty::)








Bill




Greg Maletic wrote:

> Your post brings up a good point concerning what I think is a false
> assumption concerning the separation between designer and developer.
>
> Despite the potential good uses that taglibs can be put to, HTML pages
with
> JSP scriptlets are, I believe, easier to read by web designers than pages
> with Struts taglibs.  (The one caveat being the one I mentioned
before--that
> ONLY view logic--and not business logic--should reside in scriptlets.)  My
> reasoning--and experience--is that when I simply used JSPs, I told our
> designer to completely ignore the stuff inside the "<% %>"s and code
around
> them.  Things were fine.
>
> Now that we're using Struts, I have to instruct our designer on the ins
and
> o

Re: Taglibs decrease the separation between designer and develope r?

[Bill Clinton]

Kusch, John wrote:


> me, that's a pretty clear separation between "development" and "design".  If
> you argue that it's a waste of time to teach a designer the Struts taglibs,
> I think it's fair to ask whether designers should even bother learning HMTL.
> 

John,
The line between designer and developer is a blurry one and differs 
in most organizations.  But in my last few postions, my experience has 
been that HTML proficiency is no longer a given for web designers. 
Macromedia Dreamweaver seems to be the tool of choice for most designers 
these days, and HTML skills seems to take a back seat to skills in 
Photoshop, Flash, Dreamweaver, gif animation, etc.
As someone who used notepad as my first HTML editor, this is not 
something that I am thrilled with, but it seems to be fairly common. 
Sure, its a pain in the ass to me, especially all that junk html that 
gets inserted by WYSIWYG editors, but I'd rather have a good artist with 
no scripting skills making great looking designs than a great 
html/javscript guy with mediocre artistic talent.
So, I guess you are right: it is fair to argue whether designers 
should even bother learning html.

Bill

Re: Taglibs decrease the separation between designer and developer?

[Luis Olivares]

I agree (even when I know I should leave the View to a Designer).

I think any good Web Developer should know HTML (and some Javascript :)).
Designers are important, but one must be able to be self-sufficient. Of
course, that's my point of view .

In Fact, thats why I like JSPs Technology; because you can also get involved
in some 'design stuff' (plus, you don't need to compile on your own).

That's my personal opinion and I know many people may not agree :).

Regards.

Luis Olivares.
Infosphere S.A. de C.V.
tel 8365-42-88 ext. 107.

- Original Message -
From: "Assenza, Chris" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 01, 2001 12:43 PM
Subject: RE: Taglibs decrease the separation between designer and developer?


> That's a good point, but what about when your scriptlets are controlling
the
> presentation? Ie. you've got dynamic row changes, or entirely different
> tables of output being displayed depending on a flag on the request
> (assuming you can't generecize the output) - and the designer needs to
> change the HTML output by those scriptlets?
>
> Frankly, I don't mean to diminish the role of the designer (someone I find
> to be incredibly important) but I generally would not let them edit JSP's
at
> all taglibs or not, unless they had experience with JSP or ASP.  While it
> may not be ideal or efficient to do so, I find that it is much better for
> the designers to provide me with a mockup and I'll deal with the HTML.  It
> gives developers much more control and flexibility - and then all these
> issues are moot. Plus, it gives you the added bonus of avoiding the demons
> that are WYSIWYG web development tools (hehe, I'm known lovingly as the
> "HTML snob" by one of my uncles who happens to be a designer).
>
> Unfortunately, not every developer knows HTML well so it involves more
> responsibility for the developer then may actually be good, possible or
> practical, but for me personally, I wouldn't have it any other way. :)
>
> -Chris
>
>
> -Original Message-
> From: Greg Maletic [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 01, 2001 1:15 PM
> To: [EMAIL PROTECTED]
> Subject: Taglibs decrease the separation between designer and developer?
>
>
> Your post brings up a good point concerning what I think is a false
> assumption concerning the separation between designer and developer.
>
> Despite the potential good uses that taglibs can be put to, HTML pages
with
> JSP scriptlets are, I believe, easier to read by web designers than pages
> with Struts taglibs.  (The one caveat being the one I mentioned
before--that
> ONLY view logic--and not business logic--should reside in scriptlets.)  My
> reasoning--and experience--is that when I simply used JSPs, I told our
> designer to completely ignore the stuff inside the "<% %>"s and code
around
> them.  Things were fine.
>
> Now that we're using Struts, I have to instruct our designer on the ins
and
> outs of a completely new set of pseudo-HTML tags that he doesn't
understand
> at all--and NOT to use the tags he's familiar with ("", "",
> etc.)
>
> It was much easier for both him and me before we made this switch.  Struts
> taglibs--and other taglibs--introduce, in essence, yet another language
that
> we all have to learn.
>
>
> ==
> Greg Maletic
> Chief Technical Officer
> Zero G Software, Inc.
> 514 Bryant Street
> San Francisco, CA 94107
>
> tel: +1.415.512.7771 x303
> fax: +1.415.723.7244
> mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> http://www.ZeroG.com <http://www.ZeroG.com>
>
> The leading provider of multi-platform software deployment solutions.
> ==
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> rg]On Behalf Of Tim Colson
> Sent: Tuesday, July 31, 2001 7:57 AM
> To: [EMAIL PROTECTED]
> Subject: HTML in Taglibs (was: some comparision between JSP/struts &
> velocity)
>
>
>
> Niall wrote:
> > Sorry, I couldnt disagree with you more.
> > Custom tags are exactly the place to put html - they are part of the
view,
>
> Heh heh... I never said definitively that they weren't, just that in the
> particular situation we had - it seemed like a bad idea. The bits in
> question were definitively Designer territory.
>
> BTW - you are correct when saying this was/is part of the View. However,
> part of the separation I'm striving for is between Designer and Developer
> roles. And I hope you'll agree with me that a TagLib isn't something a
> D

RE: Taglibs decrease the separation between designer and developer?

[Kusch, John]

I'm sure that this e-mail group is heavier on the Java/JSP developers than
it is on designers, so I'll throw out this question: isn't anything that
creates visual presentation of information considered "design"?  While Java
(Servlets) and the Struts framework create information and functionality,
it's HTML, scripting and taglibs that facilitate visual presentation.  To
me, that's a pretty clear separation between "development" and "design".  If
you argue that it's a waste of time to teach a designer the Struts taglibs,
I think it's fair to ask whether designers should even bother learning HMTL.

Most designers involved with the web are perfectly capable of handling
programming basics, from HTML to server-side scripting.  I think it
under-sells the abilities of most web designers to imply that Struts is too
much for them.  If it's difficult to explain Struts to a designer, the
answer isn't relegating the designer to the role of a "mockup artist" ---
it's training.  I'd think that most developers have enough on their hands
that they wouldn't mind relegating the JSP end of things to a competent and
informed designer.  The designer gets more freedom to control presentation,
and the developer gets to focus on development.

--John Kusch

-Original Message-
From: Bill Clinton [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 01, 2001 2:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Taglibs decrease the separation between designer and
developer?


Greg,
I think you are exagerating a bit when you say that "Struts 
taglibs--and other taglibs--introduce, in essence, yet another language 
that we all have to learn."  Comparing a handful of scripting tags that, 
for the most part, correspond directly to existing html tags to the 
learning of a language is a bit much.
That said, if your designer is unable to understand struts tags, I 
would recommend that you ask him not to touch them.  I don't understand 
why you would feel the need to teach a designer "the ins and outs" of 
Struts tags.  Maybe you could try something like this: design the app, 
using completely stripped jsp pages.  Ask your designer to do the 
interface, then put the tags in his interface.  If the designer needs 
control of the presentation of html contained within custom tags, use 
style sheets.
Also, if you honestly do feel that things were easier without 
struts, don't use it.  It is not a part of the servlet/jsp spec or 
anything, and its use is completely optional.  But I would urge you to 
stick with it a little more.  I think its many advantages far outweigh 
the small learning curve.

Greg Maletic wrote:

> Now that we're using Struts, I have to instruct our designer on the ins
and
> outs of a completely new set of pseudo-HTML tags that he doesn't
understand
> at all--and NOT to use the tags he's familiar with ("", "",
> etc.)
> 
> It was much easier for both him and me before we made this switch.  Struts
> taglibs--and other taglibs--introduce, in essence, yet another language
that
> we all have to learn.

Re: Taglibs decrease the separation between designer and developer?

[Bill Clinton]

Greg,
I think you are exagerating a bit when you say that "Struts 
taglibs--and other taglibs--introduce, in essence, yet another language 
that we all have to learn."  Comparing a handful of scripting tags that, 
for the most part, correspond directly to existing html tags to the 
learning of a language is a bit much.
That said, if your designer is unable to understand struts tags, I 
would recommend that you ask him not to touch them.  I don't understand 
why you would feel the need to teach a designer "the ins and outs" of 
Struts tags.  Maybe you could try something like this: design the app, 
using completely stripped jsp pages.  Ask your designer to do the 
interface, then put the tags in his interface.  If the designer needs 
control of the presentation of html contained within custom tags, use 
style sheets.
Also, if you honestly do feel that things were easier without 
struts, don't use it.  It is not a part of the servlet/jsp spec or 
anything, and its use is completely optional.  But I would urge you to 
stick with it a little more.  I think its many advantages far outweigh 
the small learning curve.

One more thing, since you have experience with servlets/jsp, you 
must admit that code for a select box that looks like this is a thing of 
beauty::)








Bill




Greg Maletic wrote:

> Your post brings up a good point concerning what I think is a false
> assumption concerning the separation between designer and developer.
> 
> Despite the potential good uses that taglibs can be put to, HTML pages with
> JSP scriptlets are, I believe, easier to read by web designers than pages
> with Struts taglibs.  (The one caveat being the one I mentioned before--that
> ONLY view logic--and not business logic--should reside in scriptlets.)  My
> reasoning--and experience--is that when I simply used JSPs, I told our
> designer to completely ignore the stuff inside the "<% %>"s and code around
> them.  Things were fine.
> 
> Now that we're using Struts, I have to instruct our designer on the ins and
> outs of a completely new set of pseudo-HTML tags that he doesn't understand
> at all--and NOT to use the tags he's familiar with ("", "",
> etc.)
> 
> It was much easier for both him and me before we made this switch.  Struts
> taglibs--and other taglibs--introduce, in essence, yet another language that
> we all have to learn.
> 
> 
> ==
> Greg Maletic
> Chief Technical Officer
> Zero G Software, Inc.
> 514 Bryant Street
> San Francisco, CA 94107
> 
> tel: +1.415.512.7771 x303
> fax: +1.415.723.7244
> mailto:[EMAIL PROTECTED] 
> http://www.ZeroG.com 
> 
> The leading provider of multi-platform software deployment solutions.
> ==
> 
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> rg]On Behalf Of Tim Colson
> Sent: Tuesday, July 31, 2001 7:57 AM
> To: [EMAIL PROTECTED]
> Subject: HTML in Taglibs (was: some comparision between JSP/struts &
> velocity)
> 
> 
> 
> Niall wrote:
> 
>> Sorry, I couldnt disagree with you more.
>> Custom tags are exactly the place to put html - they are part of the view,
> 
> 
> Heh heh... I never said definitively that they weren't, just that in the
> particular situation we had - it seemed like a bad idea. The bits in
> question were definitively Designer territory.
> 
> BTW - you are correct when saying this was/is part of the View. However,
> part of the separation I'm striving for is between Designer and Developer
> roles. And I hope you'll agree with me that a TagLib isn't something a
> Designer would likely build. 
> 
>> if you look at struts html tags thats what they do.
> 
> Yes. I understand. And honestly, it makes me a trifle uneasy. ;-)
> 
> Real example - I had a Designer chap get stumped because the html:form
> attribute "name" didn't actually map directly to the "name" of the "real
> html form". When he tried to connect a javascript function to an element in
> the form - he didn't know the name of the form. When he reasoned, "oh, I'll
> just name my html:form 'bleckfoo', just like I would if it was standard
> HTML...  following:
> 
> 
>> Error Location: Edit.jsp Internal Servlet Error:
>> javax.servlet.ServletException: Must specify type attribute if name is
> 
> specified
> 
>>  at org.apache.jasper.runtime.PageContextImpl.handlePageException
>> (PageContextImpl.java:459)
>>  at jsp._0002fjsp_0002fEdit_0002ejspEdit_jsp_2._jspService
>> (_0002fjsp_0002fEdit_0002ejspEdit_jsp_2.java:344)
> 
> 
> (That was a fun one to explain - lemme tell ya.  ;-)
> 
> 
> My point - hiding complexity won't always make things simpler.
> 
> To my Designer colleague, the fact that the  associates a Form bean with the form elements, as well as doing other nifty
> things for him/her behind the scenes didn't matter. What mattered was that
> they knew how to do HTML, and they were stumped about how to make this
> "

RE: Taglibs decrease the separation between designer and developer?

[Tim Colson]

Chris -

> Assenza, Chris wrote :
> I generally would not let [Designers] edit JSP's at all taglibs or not,
> unless they had experience with JSP or ASP.
Yikes. ;-)  I agree partially - I too have a dim view that Designers can
effectively modify JSP files w/ or w/o taglibs. But I think that in an ideal
world the Designer _should_ be able to update the View directly without a
developer intermediary as suggested.

> While it
> may not be ideal or efficient to do so, I find that it is much better for
> the designers to provide me with a mockup and I'll deal with the HTML.

When the mockup changes by a word or two - the Developer can easily make the
update.

However - when the changes are dramatic - the Developer must do a massive
manual-eyeball diff between the new mockup and the JSP. Efficiency is not
the term that usually pops in my head at that point. 


Maybe I'm the minority - but my ideal world is where the View can be built
100% by a Designer.

(BTW - if your definition of "Designer" is someone who does mockups in
PhotoShop and can't learn or use simple looping/logic concepts, then ammend
the role to "Smart Designer" or "Junior Developer". ;-)

The Answer: JSP / JSP & StrutsTaglibs / Templates (Velocity, WebMacro,
Disney's Tea, etc.) / Alien Technology / 42???

 I doubt JSP will be the answer. JSP & Struts or "standard" Taglibs might
work - I'm curious to see the how the JSR-052 and Struts tags evolve,
especially to handle non-HTML output (WML anyone?)

 From what's available now - I'd put my money on a simple to use template
system like Velocity to do the trick.

Cheers,
Timothy

RE: Taglibs decrease the separation between designer and developer?

[Assenza, Chris]

That's a good point, but what about when your scriptlets are controlling the
presentation? Ie. you've got dynamic row changes, or entirely different
tables of output being displayed depending on a flag on the request
(assuming you can't generecize the output) - and the designer needs to
change the HTML output by those scriptlets?  

Frankly, I don't mean to diminish the role of the designer (someone I find
to be incredibly important) but I generally would not let them edit JSP's at
all taglibs or not, unless they had experience with JSP or ASP.  While it
may not be ideal or efficient to do so, I find that it is much better for
the designers to provide me with a mockup and I'll deal with the HTML.  It
gives developers much more control and flexibility - and then all these
issues are moot. Plus, it gives you the added bonus of avoiding the demons
that are WYSIWYG web development tools (hehe, I'm known lovingly as the
"HTML snob" by one of my uncles who happens to be a designer). 

Unfortunately, not every developer knows HTML well so it involves more
responsibility for the developer then may actually be good, possible or
practical, but for me personally, I wouldn't have it any other way. :) 

-Chris


-Original Message-
From: Greg Maletic [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 01, 2001 1:15 PM
To: [EMAIL PROTECTED]
Subject: Taglibs decrease the separation between designer and developer?


Your post brings up a good point concerning what I think is a false
assumption concerning the separation between designer and developer.

Despite the potential good uses that taglibs can be put to, HTML pages with
JSP scriptlets are, I believe, easier to read by web designers than pages
with Struts taglibs.  (The one caveat being the one I mentioned before--that
ONLY view logic--and not business logic--should reside in scriptlets.)  My
reasoning--and experience--is that when I simply used JSPs, I told our
designer to completely ignore the stuff inside the "<% %>"s and code around
them.  Things were fine.

Now that we're using Struts, I have to instruct our designer on the ins and
outs of a completely new set of pseudo-HTML tags that he doesn't understand
at all--and NOT to use the tags he's familiar with ("", "",
etc.)

It was much easier for both him and me before we made this switch.  Struts
taglibs--and other taglibs--introduce, in essence, yet another language that
we all have to learn.


==
Greg Maletic
Chief Technical Officer
Zero G Software, Inc.
514 Bryant Street
San Francisco, CA 94107

tel: +1.415.512.7771 x303
fax: +1.415.723.7244
mailto:[EMAIL PROTECTED] 
http://www.ZeroG.com 

The leading provider of multi-platform software deployment solutions.
==


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
rg]On Behalf Of Tim Colson
Sent: Tuesday, July 31, 2001 7:57 AM
To: [EMAIL PROTECTED]
Subject: HTML in Taglibs (was: some comparision between JSP/struts &
velocity)



Niall wrote:
> Sorry, I couldnt disagree with you more.
> Custom tags are exactly the place to put html - they are part of the view,

Heh heh... I never said definitively that they weren't, just that in the
particular situation we had - it seemed like a bad idea. The bits in
question were definitively Designer territory.

BTW - you are correct when saying this was/is part of the View. However,
part of the separation I'm striving for is between Designer and Developer
roles. And I hope you'll agree with me that a TagLib isn't something a
Designer would likely build. 

> if you look at struts html tags thats what they do.
Yes. I understand. And honestly, it makes me a trifle uneasy. ;-)

Real example - I had a Designer chap get stumped because the html:form
attribute "name" didn't actually map directly to the "name" of the "real
html form". When he tried to connect a javascript function to an element in
the form - he didn't know the name of the form. When he reasoned, "oh, I'll
just name my html:form 'bleckfoo', just like I would if it was standard
HTML...  Error Location: Edit.jsp Internal Servlet Error:
> javax.servlet.ServletException: Must specify type attribute if name is
specified
>   at org.apache.jasper.runtime.PageContextImpl.handlePageException
> (PageContextImpl.java:459)
>   at jsp._0002fjsp_0002fEdit_0002ejspEdit_jsp_2._jspService
> (_0002fjsp_0002fEdit_0002ejspEdit_jsp_2.java:344)

(That was a fun one to explain - lemme tell ya.  ;-)


My point - hiding complexity won't always make things simpler.

To my Designer colleague, the fact that the 

RE: Taglibs decrease the separation between designer and developer? (A designer's perspective)

[Kusch, John]

As a designer, what I love about Struts is that, once you learn the taglibs,
you don't *need* the back-end programmers to put any code in the JSP's at
all.  As long as they're working closely with you on the behavioral
requirements of the app and accurately documenting their beans (i.e., which
beans contain which properties), the designer has full control over the
presentation of information, without having to "ignore" any code at all.
Granted, it does involve learning an entirely new set of tags, but at least
they're tags that resemble HTML, as opposed to raw JSP code.

I think that if a designer is armed with an undestanding of the Struts
taglibs, and is working with a developer who has solid communications
skills, Struts creates a working environment where the developer doesn't
have to muck around in JSP's, and the designer doesn't have to "ignore"
code.

In short, if you take the time to make sure the designer understands the
taglibs, you'll be free to focus on back-end development and let the
designer focus on presentation.  Hence, increased separation --- with a
little training.

--John Kusch

-Original Message-
From: Greg Maletic [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 01, 2001 12:15 PM
To: [EMAIL PROTECTED]
Subject: Taglibs decrease the separation between designer and developer?


Your post brings up a good point concerning what I think is a false
assumption concerning the separation between designer and developer.

Despite the potential good uses that taglibs can be put to, HTML pages with
JSP scriptlets are, I believe, easier to read by web designers than pages
with Struts taglibs.  (The one caveat being the one I mentioned before--that
ONLY view logic--and not business logic--should reside in scriptlets.)  My
reasoning--and experience--is that when I simply used JSPs, I told our
designer to completely ignore the stuff inside the "<% %>"s and code around
them.  Things were fine.

Now that we're using Struts, I have to instruct our designer on the ins and
outs of a completely new set of pseudo-HTML tags that he doesn't understand
at all--and NOT to use the tags he's familiar with ("", "",
etc.)

It was much easier for both him and me before we made this switch.  Struts
taglibs--and other taglibs--introduce, in essence, yet another language that
we all have to learn.


==
Greg Maletic
Chief Technical Officer
Zero G Software, Inc.
514 Bryant Street
San Francisco, CA 94107

tel: +1.415.512.7771 x303
fax: +1.415.723.7244
mailto:[EMAIL PROTECTED] 
http://www.ZeroG.com 

The leading provider of multi-platform software deployment solutions.
==


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
rg]On Behalf Of Tim Colson
Sent: Tuesday, July 31, 2001 7:57 AM
To: [EMAIL PROTECTED]
Subject: HTML in Taglibs (was: some comparision between JSP/struts &
velocity)



Niall wrote:
> Sorry, I couldnt disagree with you more.
> Custom tags are exactly the place to put html - they are part of the view,

Heh heh... I never said definitively that they weren't, just that in the
particular situation we had - it seemed like a bad idea. The bits in
question were definitively Designer territory.

BTW - you are correct when saying this was/is part of the View. However,
part of the separation I'm striving for is between Designer and Developer
roles. And I hope you'll agree with me that a TagLib isn't something a
Designer would likely build. 

> if you look at struts html tags thats what they do.
Yes. I understand. And honestly, it makes me a trifle uneasy. ;-)

Real example - I had a Designer chap get stumped because the html:form
attribute "name" didn't actually map directly to the "name" of the "real
html form". When he tried to connect a javascript function to an element in
the form - he didn't know the name of the form. When he reasoned, "oh, I'll
just name my html:form 'bleckfoo', just like I would if it was standard
HTML...  Error Location: Edit.jsp Internal Servlet Error:
> javax.servlet.ServletException: Must specify type attribute if name is
specified
>   at org.apache.jasper.runtime.PageContextImpl.handlePageException
> (PageContextImpl.java:459)
>   at jsp._0002fjsp_0002fEdit_0002ejspEdit_jsp_2._jspService
> (_0002fjsp_0002fEdit_0002ejspEdit_jsp_2.java:344)

(That was a fun one to explain - lemme tell ya.  ;-)


My point - hiding complexity won't always make things simpler.

To my Designer colleague, the fact that the 

Re: Taglibs

[Peter Alfors]

we use the syntax:

<%@ taglib uri="my-taglibs" prefix="mtl" %>

where the web.xml file has



  my-taglibs
  /WEB-INF/tlds/mytaglibs.tld


HTH,
Pete

Matthew Fowkes wrote:

> Pete,
>
> Do you create seperate jars for the tabligs and include them in the jsp
> pages as:
>
> <%@ taglib prefix="html" uri="/jars/test-tags.jar" %>
>
> or as
>
> <%@ taglib prefix="html" uri="/WEB-INF/test-tags.tld" %>
>
> Thanks,
> Matt
>
> > -Original Message-
> > From: Peter Alfors [SMTP:[EMAIL PROTECTED]]
> > Sent: Friday, April 27, 2001 10:51 AM
> > To:   [EMAIL PROTECTED]
> > Subject:  Re: Taglibs
> >
> > We deploy everything as JAR files.  However, we are not using iPlanet.
> > We use Apache & Tomcat.
> >
> > Pete
> >
> > Matthew Fowkes wrote:
> >
> > > Is anyone deploying the taglibs as a jar file?  iPlanet Webserver
> > version
> > > 4.1 seems to be recommending this is the only way to use custom tags
> > under
> > > it.
> > >
> > > Regards,
> > > Matt << File: Card for Peter Alfors >>


begin:vcard 
n:;
x-mozilla-html:FALSE
org:http://www.irista.com/logo/irista.gif";>Bringing Vision to Your Supply Chain
adr:;;
version:2.1
end:vcard

RE: Taglibs

[Matthew Fowkes]

Pete,

Do you create seperate jars for the tabligs and include them in the jsp
pages as:

<%@ taglib prefix="html" uri="/jars/test-tags.jar" %>

or as

<%@ taglib prefix="html" uri="/WEB-INF/test-tags.tld" %>

Thanks,
Matt

> -Original Message-
> From: Peter Alfors [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, April 27, 2001 10:51 AM
> To:   [EMAIL PROTECTED]
> Subject:  Re: Taglibs
> 
> We deploy everything as JAR files.  However, we are not using iPlanet.
> We use Apache & Tomcat.
> 
> Pete
> 
> Matthew Fowkes wrote:
> 
> > Is anyone deploying the taglibs as a jar file?  iPlanet Webserver
> version
> > 4.1 seems to be recommending this is the only way to use custom tags
> under
> > it.
> >
> > Regards,
> > Matt << File: Card for Peter Alfors >> 

Re: Taglibs

[Peter Alfors]

We deploy everything as JAR files.  However, we are not using iPlanet.
We use Apache & Tomcat.

Pete

Matthew Fowkes wrote:

> Is anyone deploying the taglibs as a jar file?  iPlanet Webserver version
> 4.1 seems to be recommending this is the only way to use custom tags under
> it.
>
> Regards,
> Matt


begin:vcard 
n:;
x-mozilla-html:FALSE
org:http://www.irista.com/logo/irista.gif";>Bringing Vision to Your Supply Chain
adr:;;
version:2.1
end:vcard