Project Progress

We chose the XML parser JDOM for creating and configuring XML documents.
The reason for we chose JDOM is that it is a Java based parser and it is free to download at
www.jdom.org

How to install JDOM
The most current version of JDOM is always available from the JDOM web site, http://www.jdom.org.

JDOM installation is as simple as extracting the compressed files into some suitable location and running a single script.On Microsoft Windows, the files will extract to a folder named jdom-b7.
The important thing is that you have to set the CLASSPATH AND JAVA_HOME variables.

How to set classpath

On microsoft windows,take environment varibles, set the path of your installation direcotry

eg: C:\java\jdom-b7\jdom.jar.


How to install and compile jdom class files

On MIcrosoft Windows,take command prompt
type c:\jdom-b7\build

build is a batch file which is loacted in JDOM directory.

The build script will compile and install the JDOM class files. Actually, the script will really just call the Java ANT program (included as part of the JDOM archive), and ANT will handle the compilation and installation.

Reference site : www.topxml.com

Project Progress

We installed Macromedia Dreamweaver and Adobe Photoshop 7.0 for designing the webpage.
We designed our homepage template using dreamweaver and adobe photoshop.
We are using MVC 2 architecture for our project.

Project progress

Thursday we fixed an appointment with our project Co-ordinator Mr.praveen kumar.
We have still some doubts in authentication.

How a web based repository interface can ensure authentication of users?

CVS limitations

The following are the limitations of CVS

Binary File Handling: CVS is designed to work with text-based data. Changes to text-based data are captured as diffs. CVS does not keep diffs of binary data changes, and instead keeps full copies of each revision. This will increase the size of nightly tarballs and the on-server storage of the repository. We discourage the storage of binary data on our CVS servers as result.

Case Sensitivity in File and Directory Names: CVS running under linux operating system, filenames are case-sensitive; a file with the name of 'filename' is distinctly separate from a file with the name of 'Filename'. This is in direct contrast with the case insensitivity of operating systems such as Microsoft Windows. Windows would treat both of those filenames as the same file. Users of case insensitive operating systems should be careful with their filenames. This can prevent access to data in your repository for some users.

File Permissions: CVS has no reliable mechanism for the remote control of file permissions. This comes in to play most frequently when storing executable files (such as scripts) within CVS. Permissions are defined at time of file add/commit. Manual intervention is required to change file permissions after-the-fact.

File Naming Limitations: File and directory names should not contain spaces; not all platforms handle spaces well. Commonly-reserved filenames should also be avoided.

Reference: www.sourceforge.net

progress of project

As usual we had some discussions with our giude.
Trying to build a home page for viewing the repositories.
Doing it in JSP.
Strated preparing the software requirement specification document.
Awaiting a meeting with our guide for more clarification.

29/09/2006 - 05/10/2006

We discussed project details with our guide.
Learned the concept of control version system.
After discussing with the team members we designed an interface for the repository.
Tried to install subversion server.


we checked the following websites

http://www.viewvc.org/
http://subversion.tigris.org/

We discuss within the group members every day, about the progress of the project.
We are posting this as a weekly report.