What is peculiar with Websphere Studio 6 on jsp:usebean?

I moved a clean project from Websphere Studio version 5.1 to version 6.0 using export/import ear.  On version 6.0, it flagged the line <jsp:useBean id="abean" class="com.packages.Abean"/> with an error 'package com.packages' does not exists.  This is not flagged as an error in Websphere studio 5 and works fine.  Do you have any idea what's peculiar with Websphere studio 6 (new name is Rational 6)?
royrubioAsked:
Who is Participating?
 
CEHJConnect With a Mentor Commented:
That would indicate that Abean is no longer in the classpath
0
 
royrubioAuthor Commented:
The solution on the IBM site covers the server config migration, not related to the compilation issue that I have.  I did it anyway, but the jsp:usebean was still being flagged: 'package com.packages does not exists'.  I tried to put AbeanX which does not exists and I got a second error saying that the class class AbeanX does not exists.  So this proves that the com.packages.Abean is visible.
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
royrubioAuthor Commented:
The link given covers JMS, not related to my problem.  

Anyway, I figured out a work-around to my problem, not an elegant solution though.  I created a web project in RAD6 then imported (from file system) all the java sources, JSPs, js files, images, struts and tiles configs, and defined the datasource for the database.  Nothing was flagged as error and the application run without errors.

I'm splitting the points to the 2 people for their time and effort.  At least they stirred my mind into thinking more.  Thanks guys.
0
 
royrubioAuthor Commented:
Thanks krakatoa and CEHJ.  Though none of your solutions solved the problem, they helped me think of other alternatives to solve the problem.  Your assistance is appreciated.
0
 
krakatoaCommented:
k.
0
All Courses

From novice to tech pro — start learning today.