from:"Tim Clotworthy"

RE: Struts1.1 Oracle 9iAS

2003-11-05 Thread Tim Clotworthy

Sorry for not getting back sooner (got caught up in other things). As far as
the version, we are using 9.0.3. Here are the two most sticky problems we
have yet to resolve:

Problem1: The way that the Oracle9iAS jsp compiler translates the
logic:equal tag is a little strange. The following example shows two logic
equal blocks : one is ROLE_TEDT = true, another is ROLE_DFSP = true,
these two blocks should be mutually exclusive.  But in Oracle9iAS, these two
blocks are both evaluated as true, which is incorrect. 

logic:equal name = displayMode value = EDIT

   logic:equal name = ROLE_TEDT value = true
  td nowrap=yes align=left class=content-tab
a class=tab href=bean:write name=AddGroundSaleUrl/Add
Ground Sale /anbsp;nbsp;
 /td
td nowrap=yes align=left class=content-tab
a class=tab href=bean:write name=AddAircraftSaleUrl/Add Aircraft
Sale /anbsp;nbsp;
   /td
  td nowrap=yes align=left class=content-tab
 a class=tab href=bean:write name=AddNavyShipSaleUrl/Add
Navy Ship Sale/anbsp;nbsp;
  /td
/logic:equal

logic:equal name = ROLE_DFSP value = true
  td nowrap=yes align=left class=content-tab
a class=tab href=bean:write name=AddNonUsGovSaleUrl/Add Ships and
Non US Government Sale/anbsp;nbsp;
  /td
 td nowrap=yes align=left class=content-tab
a class=tab href=bean:write name=AddUsGovSaleUrl/Add US
Government Sale /anbsp;nbsp;
/td
/logic:equal

/logic:equal

Problem2: The tiles: tag does not work. The following code, using my
tiles: tag, results in a 500 Internal Server Error from
org.apache.struts.taglib.InsertTag.processName(InsertTag.java: 527).

titletiles:get name='title'//title

   tiles:get name=GlobalNavigation flush='true' /

   tiles:get name=SubNavigation flush='true' /

   tiles:get name=TitleImage flush='true' /

   tiles:get name=Body flush='true' /




If I change the tiles: tag to struts1.0 template: tag, everything works
fine.

  titletemplate:get name='title'//title

template:get name=GlobalNavigation flush='true' /

template:get name=SubNavigation flush='true' /

template:get name=TitleImage flush='true' /

template:get name=Body flush='true' /



 -Original Message-
 From: Karr, David [mailto:[EMAIL PROTECTED] 
 Sent: Monday, November 03, 2003 11:32 AM
 To: Struts Users Mailing List
 Subject: RE: Struts1.1  Oracle 9iAS
 
 
  -Original Message-
  From: Tim Clotworthy [mailto:[EMAIL PROTECTED]
  
  I am saddled with having to re-implement a struts-based 
 architecture 
  designed to run on a Tomcat web container, to an Oracle 
 9iAS Release2 
  (Tomcat is out, end-of-discussion). Unfortunately, 9iAS support 
  Struts1.0 framework, but does not seem to support the various 
  Struts1.1 capabilities
  that our system already leverages, which include:
  
  1) the RequestProcessor (specifically using ProcessRoles extension)
  2) Tiles
  3) LookupDispatchAction class
  4) some other things..
  
  If anyone else may be in a similarly unfortunate position,
  and can share any
  insights on how they either:
  
  1) figured out how to get 9iAS Release2 to work with Struts1.1,
  
  Or else:
  
  2) can share any insights on how they got around similar
  problems, it would
  be greatly appreciated. Thanks.
 
 First of all, what release of 9iAS are you using (9.0.2, 9.0.3, etc.)?
 
 When you say it doesn't support those features, what 
 exactly do you mean?  Are you getting particular error messages?
 
 -
 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]

9iAS and logic:equal tag

2003-11-05 Thread Tim Clotworthy

Hello,
We are switching to 9iAS (9.0.3) from Tomcat, and we encounter the following
two issues. Any feedback for how to resolve these is greatly appreciated:

Problem1: The way that the Oracle9iAS jsp compiler translates the
logic:equal tag is a little strange. The following example shows two logic
equal blocks : one is ROLE_TEDT = true, another is ROLE_DFSP = true,
these two blocks should be mutually exclusive.  But in Oracle9iAS, these two
blocks are both evaluated as true, which is incorrect. 

logic:equal name = displayMode value = EDIT

   logic:equal name = ROLE_TEDT value = true
  td nowrap=yes align=left class=content-tab
a class=tab href=bean:write name=AddGroundSaleUrl/Add
Ground Sale /anbsp;nbsp;
 /td
td nowrap=yes align=left class=content-tab
a class=tab href=bean:write name=AddAircraftSaleUrl/Add Aircraft
Sale /anbsp;nbsp;
   /td
  td nowrap=yes align=left class=content-tab
 a class=tab href=bean:write name=AddNavyShipSaleUrl/Add
Navy Ship Sale/anbsp;nbsp;
  /td
/logic:equal

logic:equal name = ROLE_DFSP value = true
  td nowrap=yes align=left class=content-tab
a class=tab href=bean:write name=AddNonUsGovSaleUrl/Add Ships and
Non US Government Sale/anbsp;nbsp;
  /td
 td nowrap=yes align=left class=content-tab
a class=tab href=bean:write name=AddUsGovSaleUrl/Add US
Government Sale /anbsp;nbsp;
/td
/logic:equal

/logic:equal

Problem2: The tiles: tag does not work. The following code, using my
tiles: tag, results in a 500 Internal Server Error from
org.apache.struts.taglib.InsertTag.processName(InsertTag.java: 527).

titletiles:get name='title'//title

   tiles:get name=GlobalNavigation flush='true' /

   tiles:get name=SubNavigation flush='true' /

   tiles:get name=TitleImage flush='true' /

   tiles:get name=Body flush='true' /




If I change the tiles: tag to struts1.0 template: tag, everything works
fine.

  titletemplate:get name='title'//title

template:get name=GlobalNavigation flush='true' /

template:get name=SubNavigation flush='true' /

template:get name=TitleImage flush='true' /

template:get name=Body flush='true' /





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

Struts1.1 Oracle 9iAS

2003-11-03 Thread Tim Clotworthy

Hi,
I am saddled with having to re-implement a struts-based architecture
designed to run on a Tomcat web container, to an Oracle 9iAS Release2
(Tomcat is out, end-of-discussion). Unfortunately, 9iAS support Struts1.0
framework, but does not seem to support the various Struts1.1 capabilities
that our system already leverages, which include:

1) the RequestProcessor (specifically using ProcessRoles extension)
2) Tiles
3) LookupDispatchAction class
4) some other things..

If anyone else may be in a similarly unfortunate position, and can share any
insights on how they either:

1) figured out how to get 9iAS Release2 to work with Struts1.1,

Or else:

2) can share any insights on how they got around similar problems, it would
be greatly appreciated. Thanks.

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

According to TLD, tag bean:message must be empty, but is not'

2003-07-23 Thread Tim Clotworthy

Can someone tell me what would cause the following error (when jsp is
compiled), when trying to use the bean:message tag:

According to TLD, tag bean:message must be empty, but is not'

thanks

RE: According to TLD, tag bean:message must be empty, but is not'

2003-07-23 Thread Tim Clotworthy

It seems ok now. Thanks for all help.

 -Original Message-
 From: Lloyd Wilson [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 3:20 PM
 To: Struts Users Mailing List
 Subject: RE: According to TLD, tag bean:message must be empty, but is
not'
 
 Post your use of the bean:message tag. Could be a syntax problem.
 
 -Original Message-
 From: Tim Clotworthy [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 3:14 PM
 To: Struts Users Mailing List
 Subject: According to TLD, tag bean:message must be empty, but is not'
 
 
 Can someone tell me what would cause the following error (when jsp is
 compiled), when trying to use the bean:message tag:
 
 According to TLD, tag bean:message must be empty, but is not'
 
 thanks
 
 -
 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]

LookupDispatchAction problem

2003-07-23 Thread Tim Clotworthy

I am getting the following exception:

SupportOrgDispatchAction] does not contain handler parameter named
method

For this actionmapping:

action path=/SupportOrgDispatchAction
 
type=com.hotapp.fes.presentation.support.action.FESSupportOrgDispatchAc
tion
   name=SupportOrgForm parameter=method
forward name=NextPage path=/fes/jsp/FESSupportOrgTable.jsp/
/action

against these tags in my jsp:

html:submit property=method value=Query 
bean:message key=button.selectOrgs
/html:submit

This is my first crack at subclassing the LookupDispatchAction. Any
ideas as to what I am doing wrong are greatly appreciated. Thanks.

RE: LookupDispatchAction problem

2003-07-23 Thread Tim Clotworthy

Thanks to all earnest responses. I still have a problem, but it has
evolved a little. I have simplified the syntax (using husted tip 003),
so that my jsp has:

html:submit
bean:message key=button.selectOrgs/
/html:submit

(as he suggested, using the default name of submit that corresponds to
the html:submit tag, and in my struts-config, I now have:

action path=/SupportOrgDispatchAction
type=com.hotapp.fes.presentation.support.action.FESSupportOrgDispatchAc
tion name=SupportOrgForm parameter=submit
forward name=NextPage path=/fes/jsp/FESSupportOrgTable.jsp/
/action

and in my action I have:

protected Map getKeyMethodMap() {

Map map = new HashMap();
map.put(button.selectOrgs, selectOrgs); 
return map;
}


But alas, I am still getting an error (below). I wonder if my resource
bundled is not being read properly, because the button on the form
appears with the tag syntax bean:message key (obviously red flag
something is wrong), rather than the value from the properties file. How
can I check that the property button.selectOrgs is being found in the
resource bundle, or, for that matter, that the resource bundle is being
found at all?


Thanks so much to all.

javax.servlet.ServletException: Request[/SupportOrgDispatchAction] does
not contain handler parameter named submit
at
org.apache.struts.actions.LookupDispatchAction.execute(LookupDispatchAct
ion.java:199)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestPr
ocessor.java:480)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:
274)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1420)
at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:520)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:193)...blah...blah


 -Original Message-
 From: Suzette Daniel [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 4:19 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem
 
 With LookupDispatch you don't have to use a hidden tag. I think the
 problem
 might be in your action itself. Look at Ted's
 tip(http://husted.com/struts/tips/003.html) and below is a working
sample.
 
 JSP:
   html:submit property=method
 titleKey=verify.order.add.another.button.title
   bean:message key=button.add /
   /html:submit
 
 Struts-config:
   ..
 action path=/doOrderVerification name=monitorInfoForm
 input=/pages/verifyorder.jsp parameter=method
 type=com.waca.nec.consumer.actions.StoreProductDispatchAction
 scope=session
   forward name=dontsaveproduct
path=/pages/choosemonitor.jsp/
   forward name=add path=/pages/choosemonitor.jsp/
   forward name=checkout path=/pages/contactinfo.jsp/
 /action
   
 
 ACTION:
 public class StoreProductDispatchAction extends LookupDispatchAction
{
 
   protected Map getKeyMethodMap() {
   Map map = new HashMap();
   map.put(button.add, AppConstants.ACTION_KEY_ADD);
   map.put(button.checkout,
 AppConstants.ACTION_KEY_CHECK_OUT);
   map.put(button.continue.shopping,
 AppConstants.ACTION_KEY_DONT_SAVE);
   return map;
   }
 
   public ActionForward add(ActionMapping mapping, ActionForm form,
 HttpServletRequest request, HttpServletResponse response) throws
 IOException, ServletException {
   //DO STUFF
   return mapping.findForward(AppConstants.ACTION_KEY_ADD);
   }
 
   public ActionForward checkout(ActionMapping mapping, ActionForm
 form, HttpServletRequest request, HttpServletResponse response) throws
 IOException, ServletException {
   //DO STUFF
   return
 mapping.findForward(AppConstants.ACTION_KEY_CHECK_OUT);
   }
 
   public ActionForward dontsaveproduct(ActionMapping mapping,
 ActionForm form, HttpServletRequest request, HttpServletResponse
response)
 throws IOException, ServletException {
   //DO STUFF
   return
 mapping.findForward(AppConstants.ACTION_KEY_DONT_SAVE);
   }
 
 Suzette
 
 
 -Original Message-
 From: Rick Reumann [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 4:01 PM
 To: Struts Users Mailing List
 Subject: Re: LookupDispatchAction problem
 
 
 On Wed, Jul 23,'03 (03:44 PM GMT-0400), Tim wrote:
 
  I am getting the following exception:
 
  SupportOrgDispatchAction] does not contain handler parameter named
  method
 
  For this actionmapping:
 
  action path=/SupportOrgDispatchAction
 
 
type=com.hotapp.fes.presentation.support.action.FESSupportOrgDispatc
  hAc tion
 name=SupportOrgForm

RE: LookupDispatchAction problem

2003-07-23 Thread Tim Clotworthy

Thanks, but I switch it to method, and same error occurs. 

Again, I wonder if my problem is related to my resource bundle, not
being able to find it, etc. How can I simply diagnose that the tag
bean:message key=button.add / is being processed properly by the
ActionServlet (value being found, etc.). thanks. Sorry for this going
on-and-on. Who knew...



 -Original Message-
 From: Suzette Daniel [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 4:43 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem
 
 I received the same error, so I switched to using my own property
method
 and if fixed that error.
 
 JSP:
   html:submit property=method
  titleKey=verify.order.add.another.button.title
   bean:message key=button.add /
   /html:submit
 
  Struts-config:
  ..
  action path=/doOrderVerification name=monitorInfoForm
  input=/pages/verifyorder.jsp parameter=method
  type=com.waca.nec.consumer.actions.StoreProductDispatchAction
  scope=session
 
 Suzette
 
 -Original Message-
 From: Tim Clotworthy [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 4:40 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem
 
 
 Thanks to all earnest responses. I still have a problem, but it has
 evolved
 a little. I have simplified the syntax (using husted tip 003), so that
my
 jsp has:
 
 html:submit
 bean:message key=button.selectOrgs/
 /html:submit
 
 (as he suggested, using the default name of submit that corresponds to
the
 html:submit tag, and in my struts-config, I now have:
 
 action path=/SupportOrgDispatchAction

type=com.hotapp.fes.presentation.support.action.FESSupportOrgDispatchAc
 tion name=SupportOrgForm parameter=submit
 forward name=NextPage path=/fes/jsp/FESSupportOrgTable.jsp/
 /action
 
 and in my action I have:
 
 protected Map getKeyMethodMap() {
 
 Map map = new HashMap();
 map.put(button.selectOrgs, selectOrgs);
 return map;
 }
 
 
 But alas, I am still getting an error (below). I wonder if my resource
 bundled is not being read properly, because the button on the form
appears
 with the tag syntax bean:message key (obviously red flag something
is
 wrong), rather than the value from the properties file. How can I
check
 that
 the property button.selectOrgs is being found in the resource bundle,
or,
 for that matter, that the resource bundle is being found at all?
 
 
 Thanks so much to all.
 
 javax.servlet.ServletException: Request[/SupportOrgDispatchAction]
does
 not
 contain handler parameter named submit
   at

org.apache.struts.actions.LookupDispatchAction.execute(LookupDispatchAct
 ion.java:199)
   at

org.apache.struts.action.RequestProcessor.processActionPerform(RequestPr
 ocessor.java:480)
   at

org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:
 274)
   at

org.apache.struts.action.ActionServlet.process(ActionServlet.java:1420)
   at
 org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:520)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
   at

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
 tionFilterChain.java:247)
   at

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
 erChain.java:193)...blah...blah
 
 
  -Original Message-
  From: Suzette Daniel [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, July 23, 2003 4:19 PM
  To: 'Struts Users Mailing List'
  Subject: RE: LookupDispatchAction problem
 
  With LookupDispatch you don't have to use a hidden tag. I think the
  problem might be in your action itself. Look at Ted's
  tip(http://husted.com/struts/tips/003.html) and below is a working
 sample.
 
  JSP:
  html:submit property=method
  titleKey=verify.order.add.another.button.title
  bean:message key=button.add /
  /html:submit
 
  Struts-config:
  ..
  action path=/doOrderVerification name=monitorInfoForm
  input=/pages/verifyorder.jsp parameter=method
  type=com.waca.nec.consumer.actions.StoreProductDispatchAction
  scope=session
forward name=dontsaveproduct
 path=/pages/choosemonitor.jsp/
forward name=add path=/pages/choosemonitor.jsp/
forward name=checkout path=/pages/contactinfo.jsp/
  /action
  
 
  ACTION:
  public class StoreProductDispatchAction extends LookupDispatchAction
 {
  
  protected Map getKeyMethodMap() {
  Map map = new HashMap();
  map.put(button.add, AppConstants.ACTION_KEY_ADD);
  map.put(button.checkout,
 AppConstants.ACTION_KEY_CHECK_OUT);
  map.put(button.continue.shopping,
  AppConstants.ACTION_KEY_DONT_SAVE);
  return map;
  }
 
  public ActionForward add(ActionMapping mapping, ActionForm form,
  HttpServletRequest request, HttpServletResponse response) throws
  IOException, ServletException

RE: LookupDispatchAction problem

2003-07-23 Thread Tim Clotworthy

Thanks for all help. It is fixed now. God bless you, one and all.

 -Original Message-
 From: Suzette Daniel [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 5:01 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem

 No prob, here you go:

 logic:notPresent name=org.apache.struts.action.MESSAGE
 scope=application
 ERROR:  Application resources not loaded -- check servlet
container
 logs for error messages.
 /logic:notPresent

 Suzette

 -Original Message-
 From: Tim Clotworthy [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 5:00 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem

 Thanks, but I switch it to method, and same error occurs.

 Again, I wonder if my problem is related to my resource bundle, not
being
 able to find it, etc. How can I simply diagnose that the tag
bean:message
 key=button.add / is being processed properly by the ActionServlet
 (value
 being found, etc.). thanks. Sorry for this going on-and-on. Who
knew...

  -Original Message-
  From: Suzette Daniel [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, July 23, 2003 4:43 PM
  To: 'Struts Users Mailing List'
  Subject: RE: LookupDispatchAction problem

  I received the same error, so I switched to using my own property
 method
  and if fixed that error.

  JSP:
  html:submit property=method
  titleKey=verify.order.add.another.button.title
  bean:message key=button.add /
  /html:submit

   Struts-config:
 ..
   action path=/doOrderVerification name=monitorInfoForm
   input=/pages/verifyorder.jsp parameter=method
   type=com.waca.nec.consumer.actions.StoreProductDispatchAction
   scope=session

  Suzette

  -Original Message-
  From: Tim Clotworthy [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, July 23, 2003 4:40 PM
  To: 'Struts Users Mailing List'
  Subject: RE: LookupDispatchAction problem

  Thanks to all earnest responses. I still have a problem, but it has
  evolved a little. I have simplified the syntax (using husted tip
003),
  so that
 my
  jsp has:

  html:submit
  bean:message key=button.selectOrgs/
  /html:submit

  (as he suggested, using the default name of submit that corresponds
to
 the
  html:submit tag, and in my struts-config, I now have:

  action path=/SupportOrgDispatchAction

type=com.hotapp.fes.presentation.support.action.FESSupportOrgDispatchAc
  tion name=SupportOrgForm parameter=submit
  forward name=NextPage path=/fes/jsp/FESSupportOrgTable.jsp/
  /action

  and in my action I have:

  protected Map getKeyMethodMap() {

  Map map = new HashMap();
  map.put(button.selectOrgs, selectOrgs);
  return map;
  }

  But alas, I am still getting an error (below). I wonder if my
resource
  bundled is not being read properly, because the button on the form
 appears
  with the tag syntax bean:message key (obviously red flag
something
 is
  wrong), rather than the value from the properties file. How can I
 check
  that
  the property button.selectOrgs is being found in the resource
bundle,
 or,
  for that matter, that the resource bundle is being found at all?

  Thanks so much to all.

  javax.servlet.ServletException: Request[/SupportOrgDispatchAction]
 does
  not
  contain handler parameter named submit
  at

org.apache.struts.actions.LookupDispatchAction.execute(LookupDispatchAct
  ion.java:199)
  at

org.apache.struts.action.RequestProcessor.processActionPerform(RequestPr
  ocessor.java:480)
  at

org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:
  274)
  at

org.apache.struts.action.ActionServlet.process(ActionServlet.java:1420)
  at

org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:520)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
  at

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
  tionFilterChain.java:247)
  at

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
  erChain.java:193)...blah...blah

   -Original Message-
   From: Suzette Daniel [mailto:[EMAIL PROTECTED]
   Sent: Wednesday, July 23, 2003 4:19 PM
   To: 'Struts Users Mailing List'
   Subject: RE: LookupDispatchAction problem

   With LookupDispatch you don't have to use a hidden tag. I think
the
   problem might be in your action itself. Look at Ted's
   tip(http://husted.com/struts/tips/003.html) and below is a working
  sample.

   JSP:
 html:submit property=method
   titleKey=verify.order.add.another.button.title
 bean:message key=button.add /
 /html:submit

   Struts-config:
 ..
   action path=/doOrderVerification name=monitorInfoForm
   input=/pages/verifyorder.jsp parameter=method
   type=com.waca.nec.consumer.actions.StoreProductDispatchAction
   scope=session
 forward name=dontsaveproduct
  path

RE: LookupDispatchAction problem

2003-07-23 Thread Tim Clotworthy

This is really a simple aside, but is there a way to have the text
(label) of the button appear different that the value of the submit, and
if so, how does one do it? Thanks.

 -Original Message-
 From: Tim Clotworthy [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 5:07 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem

 Thanks for all help. It is fixed now. God bless you, one and all.

  -Original Message-
  From: Suzette Daniel [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, July 23, 2003 5:01 PM
  To: 'Struts Users Mailing List'
  Subject: RE: LookupDispatchAction problem

  No prob, here you go:

  logic:notPresent name=org.apache.struts.action.MESSAGE
  scope=application
  ERROR:  Application resources not loaded -- check servlet
 container
  logs for error messages.
  /logic:notPresent

  Suzette

  -Original Message-
  From: Tim Clotworthy [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, July 23, 2003 5:00 PM
  To: 'Struts Users Mailing List'
  Subject: RE: LookupDispatchAction problem

  Thanks, but I switch it to method, and same error occurs.

  Again, I wonder if my problem is related to my resource bundle, not
 being
  able to find it, etc. How can I simply diagnose that the tag
 bean:message
  key=button.add / is being processed properly by the ActionServlet
  (value
  being found, etc.). thanks. Sorry for this going on-and-on. Who
 knew...

   -Original Message-
   From: Suzette Daniel [mailto:[EMAIL PROTECTED]
   Sent: Wednesday, July 23, 2003 4:43 PM
   To: 'Struts Users Mailing List'
   Subject: RE: LookupDispatchAction problem

   I received the same error, so I switched to using my own property
  method
   and if fixed that error.

   JSP:
 html:submit property=method
   titleKey=verify.order.add.another.button.title
 bean:message key=button.add /
 /html:submit

Struts-config:
..
action path=/doOrderVerification name=monitorInfoForm
input=/pages/verifyorder.jsp parameter=method
type=com.waca.nec.consumer.actions.StoreProductDispatchAction
scope=session

   Suzette

   -Original Message-
   From: Tim Clotworthy [mailto:[EMAIL PROTECTED]
   Sent: Wednesday, July 23, 2003 4:40 PM
   To: 'Struts Users Mailing List'
   Subject: RE: LookupDispatchAction problem

   Thanks to all earnest responses. I still have a problem, but it
has
   evolved a little. I have simplified the syntax (using husted tip
 003),
   so that
  my
   jsp has:

   html:submit
   bean:message key=button.selectOrgs/
   /html:submit

   (as he suggested, using the default name of submit that
corresponds
 to
  the
   html:submit tag, and in my struts-config, I now have:

   action path=/SupportOrgDispatchAction

type=com.hotapp.fes.presentation.support.action.FESSupportOrgDispatchAc
   tion name=SupportOrgForm parameter=submit
   forward name=NextPage path=/fes/jsp/FESSupportOrgTable.jsp/
   /action

   and in my action I have:

   protected Map getKeyMethodMap() {

   Map map = new HashMap();
   map.put(button.selectOrgs, selectOrgs);
   return map;
   }

   But alas, I am still getting an error (below). I wonder if my
 resource
   bundled is not being read properly, because the button on the form
  appears
   with the tag syntax bean:message key (obviously red flag
 something
  is
   wrong), rather than the value from the properties file. How can I
  check
   that
   the property button.selectOrgs is being found in the resource
 bundle,
  or,
   for that matter, that the resource bundle is being found at all?

   Thanks so much to all.

   javax.servlet.ServletException: Request[/SupportOrgDispatchAction]
  does
   not
   contain handler parameter named submit
 at

org.apache.struts.actions.LookupDispatchAction.execute(LookupDispatchAct
   ion.java:199)
 at

org.apache.struts.action.RequestProcessor.processActionPerform(RequestPr
   ocessor.java:480)
 at

org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:
   274)
 at

org.apache.struts.action.ActionServlet.process(ActionServlet.java:1420)
 at

 org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:520)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
   tionFilterChain.java:247)
 at

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
   erChain.java:193)...blah...blah

-Original Message-
From: Suzette Daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 4:19 PM
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem

With LookupDispatch you don't have to use a hidden tag. I think
 the
problem might be in your action itself. Look

RE: LookupDispatchAction problem

2003-07-23 Thread Tim Clotworthy

Thanks. 

 -Original Message-
 From: Suzette Daniel [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 6:07 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem

 You could try using an image button:

 html:image property=method pageKey=image.submit /

 In props file:
 image.submit=/images/submit.gif

 Suzette H. Daniel
 Java Developer/Web dept
 770 416.9222 ex: 5041

 -Original Message-
 From: Michael Ruppin [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 5:53 PM
 To: Struts Users Mailing List; [EMAIL PROTECTED]
 Subject: RE: LookupDispatchAction problem

 Great question.  You don't, which is why I did my own
 dispatch Action which works off the existence of a
 parameters in the request, not their value.  In other
 words, I made a different form property for each type
 of submission, and I check which are non-null.
 Otherwise, you can't have two buttons with the same
 label on a page, and translation of your messages
 could cause methods to be unreachable.

 There are other alternatives, if JavaScript is an
 option for you.  For me, it is not.  Another
 possibility is to have many HTML forms, one for each submission, and
put
 the
 method=foo into a hidden.
 This is not always possible, if you need nesting.

 m

 --- Tim Clotworthy [EMAIL PROTECTED] wrote:
  This is really a simple aside, but is there a way to
  have the text
  (label) of the button appear different that the
  value of the submit, and
  if so, how does one do it? Thanks.

   -Original Message-
   From: Tim Clotworthy
  [mailto:[EMAIL PROTECTED]
   Sent: Wednesday, July 23, 2003 5:07 PM
   To: 'Struts Users Mailing List'
   Subject: RE: LookupDispatchAction problem

   Thanks for all help. It is fixed now. God bless
  you, one and all.

-Original Message-
From: Suzette Daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 5:01 PM
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem

No prob, here you go:

logic:notPresent
  name=org.apache.struts.action.MESSAGE
scope=application
ERROR:  Application resources not loaded --
  check servlet
   container
logs for error messages.
/logic:notPresent

Suzette

-Original Message-
From: Tim Clotworthy
  [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 5:00 PM
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem

Thanks, but I switch it to method, and same
  error occurs.

Again, I wonder if my problem is related to my
  resource bundle, not
   being
able to find it, etc. How can I simply diagnose
  that the tag
   bean:message
key=button.add / is being processed properly
  by the ActionServlet
(value
being found, etc.). thanks. Sorry for this going
  on-and-on. Who
   knew...

 -Original Message-
 From: Suzette Daniel [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 4:43 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem

 I received the same error, so I switched to
  using my own property
method
 and if fixed that error.

 JSP:
   html:submit property=method

  titleKey=verify.order.add.another.button.title
   bean:message key=button.add /
   /html:submit

  Struts-config:
  ..
  action path=/doOrderVerification
  name=monitorInfoForm
  input=/pages/verifyorder.jsp
  parameter=method

 type=com.waca.nec.consumer.actions.StoreProductDispatchAction
  scope=session

 Suzette

 -Original Message-
 From: Tim Clotworthy
  [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 4:40 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem

 Thanks to all earnest responses. I still have
  a problem, but it
  has
 evolved a little. I have simplified the syntax
  (using husted tip
   003),
 so that
my
 jsp has:

 html:submit
 bean:message key=button.selectOrgs/
 /html:submit

 (as he suggested, using the default name of
  submit that
  corresponds
   to
the
 html:submit tag, and in my struts-config, I
  now have:

 action path=/SupportOrgDispatchAction

type=com.hotapp.fes.presentation.support.action.FESSupportOrgDispatchAc
 tion name=SupportOrgForm
  parameter=submit
 forward name=NextPage
  path=/fes/jsp/FESSupportOrgTable.jsp/
 /action

 and in my action I have:

 protected Map getKeyMethodMap() {

 Map map = new HashMap();
 map.put(button.selectOrgs, selectOrgs);
 return map;
 }

 But alas, I am still getting an error (below).
  I wonder if my
   resource
 bundled is not being read properly, because
  the button on the form
appears

RE: LookupDispatchAction problem

2003-07-23 Thread Tim Clotworthy

Ok. Thanks.

 -Original Message-
 From: Michael Ruppin [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 5:53 PM
 To: Struts Users Mailing List; [EMAIL PROTECTED]
 Subject: RE: LookupDispatchAction problem

 Great question.  You don't, which is why I did my own
 dispatch Action which works off the existence of a
 parameters in the request, not their value.  In other
 words, I made a different form property for each type
 of submission, and I check which are non-null.
 Otherwise, you can't have two buttons with the same
 label on a page, and translation of your messages
 could cause methods to be unreachable.

 There are other alternatives, if JavaScript is an
 option for you.  For me, it is not.  Another
 possibility is to have many HTML forms, one for each
 submission, and put the method=foo into a hidden.
 This is not always possible, if you need nesting.

 m

 --- Tim Clotworthy [EMAIL PROTECTED] wrote:
  This is really a simple aside, but is there a way to
  have the text
  (label) of the button appear different that the
  value of the submit, and
  if so, how does one do it? Thanks.

   -Original Message-
   From: Tim Clotworthy
  [mailto:[EMAIL PROTECTED]
   Sent: Wednesday, July 23, 2003 5:07 PM
   To: 'Struts Users Mailing List'
   Subject: RE: LookupDispatchAction problem

   Thanks for all help. It is fixed now. God bless
  you, one and all.

-Original Message-
From: Suzette Daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 5:01 PM
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem

No prob, here you go:

logic:notPresent
  name=org.apache.struts.action.MESSAGE
scope=application
ERROR:  Application resources not loaded --
  check servlet
   container
logs for error messages.
/logic:notPresent

Suzette

-Original Message-
From: Tim Clotworthy
  [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 5:00 PM
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem

Thanks, but I switch it to method, and same
  error occurs.

Again, I wonder if my problem is related to my
  resource bundle, not
   being
able to find it, etc. How can I simply diagnose
  that the tag
   bean:message
key=button.add / is being processed properly
  by the ActionServlet
(value
being found, etc.). thanks. Sorry for this going
  on-and-on. Who
   knew...

 -Original Message-
 From: Suzette Daniel [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 4:43 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem

 I received the same error, so I switched to
  using my own property
method
 and if fixed that error.

 JSP:
   html:submit property=method

  titleKey=verify.order.add.another.button.title
   bean:message key=button.add /
   /html:submit

  Struts-config:
  ..
  action path=/doOrderVerification
  name=monitorInfoForm
  input=/pages/verifyorder.jsp
  parameter=method

 type=com.waca.nec.consumer.actions.StoreProductDispatchAction
  scope=session

 Suzette

 -Original Message-
 From: Tim Clotworthy
  [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 4:40 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem

 Thanks to all earnest responses. I still have
  a problem, but it
  has
 evolved a little. I have simplified the syntax
  (using husted tip
   003),
 so that
my
 jsp has:

 html:submit
 bean:message key=button.selectOrgs/
 /html:submit

 (as he suggested, using the default name of
  submit that
  corresponds
   to
the
 html:submit tag, and in my struts-config, I
  now have:

 action path=/SupportOrgDispatchAction

type=com.hotapp.fes.presentation.support.action.FESSupportOrgDispatchAc
 tion name=SupportOrgForm
  parameter=submit
 forward name=NextPage
  path=/fes/jsp/FESSupportOrgTable.jsp/
 /action

 and in my action I have:

 protected Map getKeyMethodMap() {

 Map map = new HashMap();
 map.put(button.selectOrgs, selectOrgs);
 return map;
 }

 But alas, I am still getting an error (below).
  I wonder if my
   resource
 bundled is not being read properly, because
  the button on the form
appears
 with the tag syntax bean:message key
  (obviously red flag
   something
is
 wrong), rather than the value from the
  properties file. How can I
check
 that
 the property button.selectOrgs is being found
  in the resource
   bundle,
or,
 for that matter, that the resource bundle is
  being found at all?

 Thanks so much to all.

 javax.servlet.ServletException

RE: LookupDispatchAction problem

2003-07-23 Thread Tim Clotworthy

thanks

 -Original Message-
 From: Jason Lea [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 6:14 PM
 To: Struts Users Mailing List
 Subject: Re: LookupDispatchAction problem

 Tim Clotworthy wrote:
  This is really a simple aside, but is there a way to have the text
  (label) of the button appear different that the value of the submit,
and
  if so, how does one do it? Thanks.

 Yes and no.

 The HTML 4.0.1 standard allows you to specify a button tag which
does
 this but IE doesn't support it properly.  Mozilla supports it
correctly
 though.  I have only checked with IE6 and Mozilla 1.3/1.4.

 The button tag can even include different styles and images on the
button
 eg

 button name=method value=myValue type=submitthis is a
 bbutton/b, click me/button

 Problems I found with IE's support of the button tag:
 1. The default type should be 'submit' from the standard, but IE
treats
 it as 'button' so it doesn't cause the form to submit.  Fixed by
adding
 the type=submit to the tag

 2. (the problem that stops me using it) If you have more than 1 button
 tag in your form all the button values will be included when the form
 submits - which makes it useless.

 Eg if i have the following buttons:

 button name=method value=update type=submitupdate me/button
 button name=method value=delete type=submitdelete me/button

 I click the 'update me' button, IE will submit the following values
 method=updatemethod=delete, when it should only send method=update.

 check out the spec here:
 http://www.w3.org/TR/html401/interact/forms.html#edef-BUTTON

 --Jason Lea

 -Original Message-
 From: Tim Clotworthy [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 5:07 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem

 Thanks for all help. It is fixed now. God bless you, one and all.

 -Original Message-
 From: Suzette Daniel [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 5:01 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem

 No prob, here you go:

 logic:notPresent name=org.apache.struts.action.MESSAGE
 scope=application
 ERROR:  Application resources not loaded -- check servlet

 container

 logs for error messages.
 /logic:notPresent

 Suzette

 -Original Message-
 From: Tim Clotworthy [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 5:00 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem

 Thanks, but I switch it to method, and same error occurs.

 Again, I wonder if my problem is related to my resource bundle, not

 being

 able to find it, etc. How can I simply diagnose that the tag

 bean:message

 key=button.add / is being processed properly by the
ActionServlet
 (value
 being found, etc.). thanks. Sorry for this going on-and-on. Who

 knew...

 -Original Message-
 From: Suzette Daniel [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 4:43 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem

 I received the same error, so I switched to using my own property

 method

 and if fixed that error.

 JSP:
   html:submit property=method
 titleKey=verify.order.add.another.button.title
   bean:message key=button.add /
   /html:submit

 Struts-config:
  ..
 action path=/doOrderVerification name=monitorInfoForm
 input=/pages/verifyorder.jsp parameter=method
 type=com.waca.nec.consumer.actions.StoreProductDispatchAction
 scope=session

 Suzette

 -Original Message-
 From: Tim Clotworthy [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 23, 2003 4:40 PM
 To: 'Struts Users Mailing List'
 Subject: RE: LookupDispatchAction problem

 Thanks to all earnest responses. I still have a problem, but it

  has

 evolved a little. I have simplified the syntax (using husted tip

 003),

 so that

 my

 jsp has:

 html:submit
 bean:message key=button.selectOrgs/
 /html:submit

 (as he suggested, using the default name of submit that

  corresponds

 to

 the

 html:submit tag, and in my struts-config, I now have:

 action path=/SupportOrgDispatchAction

type=com.hotapp.fes.presentation.support.action.FESSupportOrgDispatchAc

 tion name=SupportOrgForm parameter=submit
 forward name=NextPage path=/fes/jsp/FESSupportOrgTable.jsp/
 /action

 and in my action I have:

 protected Map getKeyMethodMap() {

 Map map = new HashMap();
 map.put(button.selectOrgs, selectOrgs);
 return map;
 }

 But alas, I am still getting an error (below). I wonder if my

 resource

 bundled is not being read properly, because the button on the form

 appears

 with the tag syntax bean:message key (obviously red flag

 something

 is

 wrong), rather than the value from the properties file. How can I

 check

 that
 the property button.selectOrgs is being found in the resource

 bundle,

 or,

 for that matter, that the resource bundle is being found at all

RE: Struts1.1 Oracle 9iAS

9iAS and logic:equal tag

Struts1.1 Oracle 9iAS

According to TLD, tag bean:message must be empty, but is not'

RE: According to TLD, tag bean:message must be empty, but is not'

LookupDispatchAction problem

RE: LookupDispatchAction problem

RE: LookupDispatchAction problem

RE: LookupDispatchAction problem

RE: LookupDispatchAction problem

RE: LookupDispatchAction problem

RE: LookupDispatchAction problem

RE: LookupDispatchAction problem

13 matches

Site Navigation

Mail list logo

Footer information