I finally figured out how to resolve this problem once and for all. In my last posting, I mentioned that deleting the JBoss server directory and replacing it with a fresh copy worked for me. I reproduced the problem on anther PC and was able to understand exactly how to resolve this issue.

Eclipse generally uses a JRE and when I added J2SDK1.4.2_03 to the list of "Installed JREs", it automatically adds "\jre" to the directory name. For example, if you set the "JRE Home Directory" to C:\j2sdk1.4.2_03, the path Eclipse will use is C:\j2sdk1.4.2_03\jre\lib. If this is the case, tools.jar is not added to the system libraries to use.

To add tools.jar, perform the following steps:

- In Eclipse, select "Preferences" from the "Window" menu.
- Expand "Java" from the tree and select "Installed JREs".
- Select the JRE you are using and click the "Edit" button.
- In the "Edit JRE" dialogue (yeah, I'm Canadian, we spell it like this), uncheck "Use default system libraries".
- Click on the "Add External JARs..." button and open tools.jar from your SDK directory. This will add the tools.jar file to the system libraries to use.

Once you redeploy your ear and view the jsp page, JBoss will now be able to compile the jsp because it has access to tools.jar.

I hope this posting is able to help the people having this issue because it sure caused me a lot of headaches.

--
Steven Ercolani

PROFESSIONAL SUMMARY


Mr. Sanju Thomas is a software proefssional having two years of extensive experience in
developing and implementing business components in sun and related technologies. He was part
of many major projects done in java and j2ee technologies. He has got deep knowlege in object oriented analysis and design. He posses the capability to understand the business needs quickly. Mr. Sanju Thomas is a very good team player and communicator.





TECHNICAL SKILLS

Operating System : WindowsX, Linux.
Languages : Java, C++.
Scripting languages : Java Script, VB Script.
Packages : Office XP.
Software Engineering : UML.
Application Server : JBoss 4.0.
Web Server : Apcahe Tomcat 5.0.
Directory Server : Open LDAP.
RDBMS : IBM DB2-UDB.
Deployment Tool : Jakarta ANT.
Testing Tools : JUnit.
Build Tools : Apache ANT 1.6.
IDEs : Eclipse 3.0, IntelliJ IDEA 4.5.


SUN AND RELATED TECHNOLOGIES :

EJB 2.0, JAAS, JDBC, JNDI, Servlets, JSP, RMI, JMS, JavaHelp 2.0, Log4J, JDOM.

Entry level knowledge in Struts.



PROFESSIONAL EXPERIENCE

Organization : Optiwise Solutions Private Limited.

JBoss™ integration in Optiwise™
Period :Aug 2003 to Aug 2004


Overview of the project:

Optiwise™ is an Information System Tool and Methodology for Product Architecture Management. It is used for the design, communication, documentation, optimization and management of the product concept, product platforms, and product architecture. Optiwise™ can be utilized as a corporate-level strategic product management tool, with communication support for distributed R&D. With Optiwise™ the architecture of a product family is managed through dependencies between definition items such as market requirements, product features, modules, components and interfaces.

JBoss integration in Optiwise™ is done in one project life cycle, long over one year. The project was intended to release a new version of Optiwise™ in JBoss application server. So that, the cost of the Optiwise™ can be reduced through avoiding the license fee of BEA Weblogic.

Mr. Sanju Thomas worked in the high level desigh and coding of this project. He was responsible for the design, development and deployment of EJBs. He worked in implementing JAAS based security for Optiwise system


Generic adapter integration in Optiwise

Organization : Optiwise Solutions Private Limited.
Period :jan 2003 to aug 2003

Overview of the project:

SQL Adapter integration to Optiwise™ was a module in whole Optiwise™ system. It was an attempt to design an interface between six legacy systems (Oracle, MS-SQL, MS-Access, Fire-Bird, Visual Fox-pro, and IBM-DB2) and Optiwise™. This adapter will provide GUI interface to the Optiwise user to read and write data from/to the underlaying repository. Through the implementation of this adapter, the tool Optiwise become more suitable to fit into hectrogenious environment.

Mr. Sanju Thomas was responsible to the high level design and coding of this poject. In this project he worked extensivly with JDBC and java and he actively involved in testing and documentation of the work.



Help system for Optiwise Graphics Engine.

Organization : Optiwise Solutions Private Limited.
Period : sep 2002 to dec 2002

Optiwise Graphics Engine provides access to the enterprise data in a location transparent manner.
It is a tool to populate real time data into the Optiwise client GUI console. Its a comprehensive help system that support context sesitive help. The help system is implemented using Java Help 2.0 API. Its designed in such a way that, it can be plugged into any other system with out any major changes in the implementaion.

Mr. Sanju Thomas was involved in the coding and content development. He actively participated in the testing and documentation process of the project.



EDUCATION and TRAINING

Master of Computer Applications, Pondicherry Unversity, UT of Pondicherry, India.
Year : 2002
GPA :7.60/10

Bachelor of Commerce, Kerala University, Kerala, India.
Year : 1999
GPA : 6.2/10

CERTIFICATION

IBM Certified Specialist in DB2 UDB 7.1
Year: 2002

While using the XML facility of JbossIDE 1.4 in Eclipse 3.0 (xdoclet 1.2.1), opening up any of the merged files lists the following error in the XML file:

The markup in the document following the root element must be well-formed.

<error-page>
 <error-code>400</error-code>
 <location>/error/error400.jsp</location>
</error-page>

<error-page>
 <error-code>403</error-code>
 <location>/error/error403.jsp</location>
</error-page>

<error-page>
 <error-code>404</error-code>
 <location>/error/error404.jsp</location>
</error-page>

By default, Eclipse and most plugins use the default JRE as configured in preferences. Also by default, this is the public system JRE and not the JDK jre. Try navigating to window->preferences->java->installed JREs. Most likely you will have on entry and (on Windows) it will be c:\Program Files\ etc etc. Click search, navigate to your jdk (on windows default) c:\j2sdk1.4.2_05 and then that will be available to eclipse. click the checkbox to set it as default and you should be all set.

I'm not 100% sure this will work for JbossIDE and I don't know why myEclipse works. I usually avoid the hassle of running the app server within eclipse and just use handy batch files to start and stop. I find it less buggy, more flexible, and slightly better performing than dealing with the IDE. Also, remote debugging works spectacularly IMHO.

Sorry that we haven't replied -- Do you think you could file a bug report on sourceforge for this? I haven't looked over the offending code yet, but it looks to be a valid bug.

Thanks =)

Have you set "As JRE Library Use" in Window->Preferences->Java->BuildPath to "JRE_LIB variable" ?

My fix for this is to ensure tools.jar is in the bootstrap classpath in the server configuration. It is not included as a JRE library by default.