Sunil Vasudevan

Is having username/password not considered safe enough?

Well, I did have such a requirement in one of my previous client(A Bank) due to sensitive data and they had put a restriction on the computers that can access the system. This was handled using client side certificates. It is a painful process as each system that would interface with the secure system would need to request for a client certificate. Here we had a server connecting to another server and we had limited number of servers.

In your case, the solution below might provide some pointers:
Have a user register a computer using a registration screen that would save a flash object on the user system. When the user logs in, read the flash object and the data stored in it to identify if this is a registered computer and registered to a specific user. This is similar to storing a cookie, but cookies can be deleted easily.

My bad.. You mentioned you need to create a login module.

During user registration, have the user provide a password too.

Since you have a login module, doesn't it require a password?

If yes, that should act as a security layer. Am I missing something?

Jerry Goldsmith wrote:
<input type="checkbox" name="arrCheckBox[]" value="<%=i%>">

Jerry Goldsmith wrote:
<% String [] arrCheckBox=request.getParameterValues("CheckBox"); out.print(arrCheckBox[0]); %>

In your JSP, you are having a different name for your checkbox and in getParameterValue() you are using a different name.

Server does not know about user closing the browser. So the session won't end. The session will still be active on the server till the session times out.

If you are using Spring, you can use spring-mock.jar. It has Mock HttpRequest, HttpResponse and HttpSession objects.

Else, if you want to go with a plain vanilla approach, create a mock HttpSession yourself.

Here is a sample code I had used before using spring-mock:

public class MockHttpSession implements HttpSession { private Map attributeMap = new HashMap(); private String sessionId; public MockHttpSession() { sessionId = "junittest-" + System.currentTimeMillis(); } public Object getAttribute(String arg0) { return attributeMap.get(arg0); } public Enumeration getAttributeNames() { return null; } public long getCreationTime() { return 0; } public String getId() { return sessionId; } public long getLastAccessedTime() { return 0; } public int getMaxInactiveInterval() { return 0; } public ServletContext getServletContext() { return null; } public HttpSessionContext getSessionContext() { return null; } public Object getValue(String arg0) { return null; } public String[] getValueNames() { return null; } public void invalidate() { //Do nothing } public boolean isNew() { return false; } public void putValue(String arg0, Object arg1) { //Do nothing } public void removeAttribute(String arg0) { attributeMap.remove(arg0); } public void removeValue(String arg0) { //Do nothing } public void setAttribute(String arg0, Object arg1) { attributeMap.put(arg0, arg1); } public void setMaxInactiveInterval(int arg0) { //Do nothing } }

Hope this helps.

Functional specifications - Provides the functional requirements of the project. It defines what the application is supposed to do.

Unit Test Plan(UTP) - Defines how you would carry out your unit testing. It usually contains unit test cases.

I am not sure how widely is Unit test plans used in the current age. It used to be popular with Rational Unified Process (RUP) Methodology. But with Agile and Test Driven Development, you directly jump in creating JUnit or TestNG unit test cases instead of documenting the unit test plan in a word document.

You may find some organizations who require you document the unit test cases for the sake of tracebility matrix to map the requirements mentioned in funtional specs to the unit test cases you intend to test. Also by reviewing the UTP (Which is usually written by the devloper who is supposed to implement a specific functionality), a tech lead or project lead figures out if the developer has understood the requirement, before he starts implementing the code. So a lot depends on the process adopted by the company you are working in.

Hope this helps.

Ryan is correct. It needs to be in a cluster for session to migrate.

JDK: Sun 1.5.0_16
Also tried on jrockit81sp5_142_08

Just for curiosity, I was trying out the following code snippet:

public class IteratorRemoveTest { public static void main(String[] args) throws Exception { List testList = new ArrayList(); testList.add("One"); testList.add("Two"); testList.add("Three"); testList.add("Four"); testList.add("Five"); System.out.println("Before: " + testList); for (Iterator iterator = testList.iterator(); iterator.hasNext();) { String object = (String) iterator.next(); System.out.println("Object got: " + object); if (object.equals("Three")) { testList.remove(object); } } System.out.println("After: " + testList); } }

I expect java.util.ConcurrentModificationException to be thrown and this code works as expected.

But when I try the same code with the second-last element ("Four" in this case), I do not get this exception. I get java.util.ConcurrentModificationException for "Five". I was expecting the behaviour to be consistent and since the list had been structurally modified, as per the specs, I should have got java.util.ConcurrentModificationException when I remove "Four" as well.

Am I missing anything?

I did not get what you meant by 1 form button.

You need two buttons - Add and Update. But they should be within one single form element. On the click on the button, your server should be able to understand if the request is for Add or Update.

Can you attach your form bean and action class?

You need to check how you have used your form tags. Your elements are wrapped in one form tag and you have update button in another form tag. Hope that gives you a pointer on what you need to do.

Hi Jeanne, I thought RAD 7 supports Java 1.5 and J2EE 1.4. Am I missing something?

Arjun, the redbooks from IBM provide all information you are looking in RAD 7.

URL for redbook of RAD7: http://www.redbooks.ibm.com/redbooks/SG247501/wwhelp/wwhimpl/java/html/wwhelp.htm

URL for compatible softwares (Google provided link...): http://publib.boulder.ibm.com/infocenter/iadthelp/v7r0/index.jsp?topic=/com.ibm.rad.nav.doc/topics/rswsuprad700.html
[ July 29, 2008: Message edited by: Sunil Vasudevan ]

Hi Arun,

This is a consistent behavior? Did you try including a debug point on the action method invoked by the submit button?

Run the following SQL on your Oracle database:
desc PRD_SGMN;

If it returns "ERROR: object PRD_SGMN does not exist", then you do not have this user defined type created in Oracle database. It is then a database issue rather than a java code issue.

Let me know what you find...

Support for WebSphere application servers (WAS) are also different.

WSAD used to support WAS 5.x

RAD6 supports WAS 6.0. You have support for JDK 1.4 but not for 1.5.

RAD7 supports both WAS 6.0 and 6.1. You can use JDK 1.5 here.

Having worked with WSAD and RAD 6 for around 2 years and having moved to RAD7 4 months back, I still would have preferred to stick with RAD 6. RAD 7 is not that unstable yet (Even with the latest patch 7.0.0.6). But we had a project that required features from JDK 1.5 and needed to be deployed on WAS 6.1.
[ April 29, 2008: Message edited by: Sunil Vasudevan ]