The following comment has been added to this issue:

     Author: Chandra Moulee
    Created: Mon, 11 Aug 2003 1:35 AM
       Body:
The Solution found was,
1. The action mapping file has to reflect the path to the jsp as below
login.input=/com/project/jsp/login.jsp
....

2. The jsp pages cannot under WEB-INF.

With the above changes, pages can be accessed.

This exposes the security issue of jsps not under WEB-INF.

Result
------
WW2 integrates well with WebSphere 5.0, with the following changes

1. /template/xhtml/*.jsp should be made available for the projects. (Funny way of 
packaging by WW2 team).

2. The taglib definition to be changed to tld reference in the above jsp pages and 
application-specific jsp pages.

3. The quality of support from WW2 team is very very ..... poor.

Regards
Chandramoulee



---------------------------------------------------------------------
View the issue:

  http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-244


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WW-244
    Summary: WW2 on WAS 5.0
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: WebWork
 Components: 
             Actions
   Fix Fors:
             2.0
   Versions:
             2.0
             2.0-beta1

   Assignee: Patrick Lightbody
   Reporter: Chandra Moulee

    Created: Wed, 6 Aug 2003 4:53 AM
    Updated: Thu, 7 Aug 2003 9:32 PM
Environment: Websphere 5.0, WW2 (Release 1.3) and Studio Developer

Description:
Studio Developer Websphere 5.0 shows the following project-build warning!!!(in Tasks 
View)

Broken Link - /ProjectWeb/WEB-INF/com/project/jsp/login.action - It is invalid to link 
to resources under the WEB-INF directory.


The actions.xml or view.properties was under WEB-INF/classes directory, after the 
project build.

When accessing the page as below,

http://localhost:9080/ProjectWeb/login.action

There is 404 thrown with NO exception in Console->View

It seems Websphere doesNot read (or package) the view.properties or actions.xml file 
to WEB-INF/classes directory.

Dump:login.jsp
--------------
<%@ taglib uri="/WEB-INF/taglib.tld" prefix="webwork" %>
<html>
  <head>
    <title>Login</title>
  </head>
  <body>
  <form action="login.action" method="post">
    <webwork:property>
      <webwork:textfield label="'Name'" name="'userName'"/>
      <webwork:password label="'Password'" name="'password'"/>
    </webwork:property>
    <input type="submit" value="Submit"/>
  </form>
  <webwork:iterator value="errors">
    <br><webwork:property/>
  </webwork:iterator>
  </body>
</html>

Dump:actions.xml
----------------
<actions>
  <action name="LoginAction" alias="login">
    <view name="input">login.jsp</view>
    <view name="success">hello.jsp</view>
  </action>
</actions>

Dump:webwork.properties
-----------------------
# WebWork configuration
# See webwork/default.properties for full list of properties that
# can be configured here
webwork.action.packages=com.project.action

# XML action configurations
webwork.configuration.xml=actions

# a possible extension change
# don't foget that you must change
# web.xml accordingly
webwork.action.extension=action

# if you override the extension, then you should
# fix these three standard alias as well to reflect
# the correct extension
redirect.action=webwork.action.standard.Redirect
referrer.action=webwork.action.standard.Referrer
cardpane.action=webwork.action.standard.CardPane

# Velocity settings
# See the Velocity project (http://jakarta.apache.org/velocity/) for
# more info on what settings are available
# Also see webwork/default.properties in WebWork if you want
# to see what defaults have been set.

# Set this to your own source directory during development.
# This allows you to edit the pages while the server is running without losing
# the changes when you re-deploy the application.
file.resource.loader.path = /

LoginAction.java
----------------
package com.project.action;

import webwork.action.*;

public class LoginAction extends ActionSupport
{
  private String userName;
  private String password; 

  public String getPassword()
  {
    return password;
  }

  public String getUserName()
  {
    return userName;
  }

  public void setPassword(String password)
  {
    this.password = password;
  }

  public void setUserName(String userName)
  {
    this.userName = userName;
  }

  public String doExecute() throws Exception
  {
    return SUCCESS;
  }

  public void doValidation()
  {
    if (userName == null || userName.length() < 1) addError("UserName", "Please enter 
username.");
    if (password == null || password.length() < 1) addError("Password", "Please enter 
password.");
  }
}

Any bright ideas to make this work?.
Regards
Chandra Moulee


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.opensymphony.com/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to