Hi Tony,

3) There are 2 unused imports in the EJB project.. I right click on EJB project, Properties > Java Compiler > Errors/Warnings > Unnecessary code > Unused import (set to warning). But when it auto build, the errors are still showing in my problem tab.

hahagal,

That setting is normally set to Warning by default. Did you try changing the setting to Ignore?

Could you provide a screenshot showing the code editor and the problems view, with the error about unused import selected (so that the full message shows in the bottom bar)? This visual may help.

Does this only happen with EJB projects? Can you try adding an unused import to another type of project to see if it occurs there also?

Hi,

When I was deploying the EAR to Wepshere 6.1, I noticed in the deployment.log, there are 269 warnings. How can I clear the warnings?

ADMA5016I: Installation of Belsize started.
ADMA5058I: Application and module versions are validated with versions of deployment targets.
ADMA5018I: The EJBDeploy command is running on enterprise archive (EAR) file C:\Users\admin\AppData\Local\Temp\app8673571093349706201.ear.
Starting workbench.
EJB Deploy configuration directory: c:\IBM\WebSphere\AppServer\deploytool\itp\configuration/
framework search path: c:\IBM\WebSphere\AppServer\deploytool\itp\plugins
Debug options:
Creating the project.
Deploying jar BelsizeEJB
Generating deployment code
ejbModule/com/belsize/sb/SB_WithholdingTaxBean.java(22): The serializable class SB_WithholdingTaxBean does not declare a static final serialVersionUID field of type long
ejbModule/com/belsize/sb/SB_UtilityBean.java(79): The serializable class SB_UtilityBean does not declare a static final serialVersionUID field of type long
ejbModule/com/belsize/sb/SB_UtilityBean.java(1241): The method FileInputStream(String) from the type SB_UtilityBean is never used locally
ejbModule/com/belsize/sb/SB_UtilityBean.java(2100): The method getBeanTaskInfo() from the type SB_UtilityBean is never used locally
ejbModule/com/belsize/sb/SB_UserdefineBean.java(34): The serializable class SB_UserdefineBean does not declare a static final serialVersionUID field of type long
ejbModule/com/belsize/sb/SB_UserdefineBean.java(40): The field SB_UserdefineBean.ACCESSRIGHT_CATEGORY_USEREPORT is never read locally
ejbModule/com/belsize/sb/SB_User_permissionBean.java(48): The serializable class SB_User_permissionBean does not declare a static final serialVersionUID field of type long
ejbModule/com/belsize/sb/SB_TradegroupBean.java(22): The serializable class SB_TradegroupBean does not declare a static final serialVersionUID field of type long
ejbModule/com/belsize/sb/SB_TradegroupBean.java(25): The field SB_TradegroupBean.INTERCO_ACCTCNTR is never read locally
ejbModule/com/belsize/sb/SB_TradegroupBean.java(27): The field SB_TradegroupBean.INTERCO_CTPY is never read locally
ejbModule/com/belsize/sb/SB_TradegroupBean.java(29): The field SB_TradegroupBean.MMRO_ORIGINAL is never read locally
ejbModule/com/belsize/sb/SB_TradegroupBean.java(31): The field SB_TradegroupBean.MMRO_CASHDEAL is never read locally
ejbModule/com/belsize/sb/SB_TradegroupBean.java(33): The field SB_TradegroupBean.MMRO_ROLLTO is never read locally
ejbModule/com/belsize/sb/SB_TradegroupBean.java(35): The field SB_TradegroupBean.FXRO_ORIGINAL is never read locally
.
.
.
.
Invoking RMIC.
Writing output file
Shutting down workbench.
EJBDeploy complete.
0 Errors, 269 Warnings, 0 Informational Messages
ADMA5007I: The EJBDeploy command completed on C:\IBM\WebSphere\AppServer\profiles\AppSrv01\wstemp\wstemp\app_13580846da0\dpl\dpl_Belsize.ear
WSWS0041I: Web services deploy task completed successfully.
ADMA5005I: The application Belsize is configured in the WebSphere Application Server repository.
ADMA5053I: The library references for the installed optional package are created.
ADMA5005I: The application Belsize is configured in the WebSphere Application Server repository.
ADMA5001I: The application binaries are saved in C:\IBM\WebSphere\AppServer\profiles\AppSrv01\wstemp\Script13580841f62\workspace\cells\admin-PCNode01Cell\applications\Belsize.ear\Belsize.ear
ADMA5005I: The application Belsize is configured in the WebSphere Application Server repository.
SECJ0400I: Successfuly updated the application Belsize with the appContextIDForSecurity information.
ADMA5011I: The cleanup of the temp directory for application Belsize is complete.
ADMA5013I: Application Belsize installed successfully.

Hi,

Here is the screenshot for 3) which you requested.
As for 2), Do you suggest that I uncheck the client side javascript validator?

hahagal,

These issues appear to be programming issues, not related to MyEclipse. However, I can say that the screenshot you posted is showing errors that are different from your earlier description. The error in the import is because it can't be resolved, not because it isn't used. If it truly isn't used, I suggest you delete it, otherwise you will have to add something to your project to resolve the import (perhaps by adding an external jar file or a WebSphere library).

The warnings are just warnings. There is no need to clear them. However, to clear warnings, you usually have to deal with each warning. Many of them appear to be about a missing serialization ID in classes. This is a common warning and can be corrected, if needed, by adding a static field in the class. The eclipse Java editor can add this for you through a quick fix. There may also be Java compiler switches to ignore some warnings, and standard eclipse preferences for that also.

As I say, these are programming issues, rather than MyEclipse issues, unless you believe that MyEclipse is somehow causing these warnings and errors to appear. For programming issues, you will get better support from a general Java or WebSphere programming forum.

Hi Tony,

My EJB doesn't have the warnings.. how come it still shows up when deploying to the server? Other than quick fix, any other solutions? We need to clear this..

hahagal,

I'm not sure why you need to clear those warnings but there are various standard eclipse Java settings that may help. Go to Window->Preferences->Java->Compiler->Errors/Warnings. The "Potential programming problems" section deals with the missing serialVersionUID warning, there may be others of use to you, also.

Hi Tony,

That has been set to Ignore.. Seems like its not working?
Can I check with you this should be kept as binary or ACSII text when committing project to CVS?

hahagal,

I can't replicate your problem with your serialVersionUID warnings; if I select ignore for that setting, I don't get the warnings in the Java editor or in the problems view. If you build your project externally, then you might still get warnings in your output; I think there may be Java compiler switches you can use to avoid those warnings but don't have that information to hand. I also don't know about the CVS formats.

You may get better support for these general programming or eclipse issues elsewhere as we specifically handle MyEclipse issues. The eclipse forums can be found at http://www.eclipse.org/forums/. There are many general programming forums.

Hi Tony,

Is .ejbdeploy and ejbDeploy the same? In RAD, we only have ejbDeploy folder. And when it build, the files will be in the ejbDeploy folder.. Seems like everything is going to .ejbdeploy folder. Is it so that in MEB, it only uses .ejbdeploy folder?

Hi Tony,

Is there any ways to speed up the JSF view validator task? We have a lot of JSPs and it take almost an hour to validate them..

hahagal,

Yes, the .ejbdeploy folder is used in MyEclipse Blue. I'm not sure about its relationship with RAD's ejbDeploy folder. Is this a problem for you? If so, please explain the problem.

Validation is configurable for all file types. Right click on any file or folder in the project and select MyEclipse. There are a couple of options on the sub-menu: Exclude from Validation and Manage Validation. So you can exclude individual folders and files from validation or you can stop certain validators from running. Validation can be managed on a project specific basis or a workspace basis.

I hope this helps.

support-tony wrote:

hahagal, I can't replicate your problem with your serialVersionUID warnings; if I select ignore for that setting, I don't get the warnings in the Java editor or in the problems view. If you build your project externally, then you might still get warnings in your output; I think there may be Java compiler switches you can use to avoid those warnings but don't have that information to hand. I also don't know about the CVS formats. You may get better support for these general programming or eclipse issues elsewhere as we specifically handle MyEclipse issues. The eclipse forums can be found at http://www.eclipse.org/forums/. There are many general programming forums.

Appreciate if you can provide the steps on how you build your project?

hahagal,

I'm not sure what you're looking for. I tried to replicate your problem and couldn't. MyEclipse generally builds projects automatically, in response to changes to source code or build path settings. This can be turned off (in the Project menu) with the build then having to be done manually (from the same menu).

Hi Tony,

I see. In that case I will fix the warnings myself.
Thanks for the assistance!