Hello, just me strange things?

I downloaded the version 9.1.1 from the previous 9.1.0 with no errors.

Only 4 egl programs between 200l in the same project gives me the error:

Multiple Makers at this line

IWN.VAL.6890.w 10/16 the expression is deprecated

IWN.VAL 3000.e An error has occured whilw complig part.a.Check the log file for additional information.

The instruction is:

 handler a type JSFHandler{onConstructionFunction = onConstruction, onPrerenderFunction = onPrerender, view = "aa.jsp", viewRootVar = viewRoot}
 

all other 196 programs are without error !!!

Any idea?

Attached one of the four programs

paoloc

Hi,

The reason for this message is that the JSF support in EGL was deprecated as of RBD 9.0 and we started to flag it in 9.1.0.    We wanted to flag it so you would be more explicitly aware that the support could go away in the future.   As of RBD 9.1.1, JSF is still supported and that release will be in support until at least Sept. 2019.    

Here is a link to a technote that we will keep up-to-date as releases are shipped.   This is also available from the RBD Knowledge Center:

http://www-01.ibm.com/support/docview.wss?uid=swg27041781

Deprecations/removals

Deprecated Syntax will be marked "deprecated" in source (yellow icon)

Hello Mark,

thanks for your answer. I had already realized that an yellow error was not serious.But I do not understand that will have consequences in the future. An outstanding problem I never liked best.

There must be a serious problem in the transition from 9.1.0 to 9.1.1 because the error occurs when I do this step.

So I abandoned the version 9.1.1 because I have no time to lose. 

As you can see from the attached only 4 programs are in error  in 9.1.1 while with the 9.1.0 there were no errors and this is really incomprehensible.

I do not have time to report it, but the problem exists

Regards paoloc

The IWN.VAL 3000.e message is really what the problem was. That is a catch-all message for when an exception has occurred during validation. The message says to look in the log file to get more details. However, as the log file is not attached, I cannot proceed.

To expand on what Jeff said, this message means there is some syntax error (red-x) in the EGL source or EGL Projects.  You need to look at the problems view and see what the errors are and correct them prior to trying to generate.

Paoloc,

Jeff and I were chatting and we are confused which error you are getting now?

The IVN.VAL.3000 that you first reported means the validation functionality itself took an exception and this would be in the .log file in your <workspace>\.metadata folder.  We would need to see that.

The generation error you reported on the screen shot in the latest comment is what I was referring to which is just a syntax error somewhere and you are getting a red-x that needs to be resolved.  What is wrong should be in the problems view.

Please let us know what issue you are having currently and if needed attach more documentation.

Mark

Hello friends.

I redid the whole installation process 9.1.1.

Attached the rquested files.

paoloc

Paoloc.

I see the problem and can email you a fixtest. Can you please email me at    jeffdouglas@us.ibm.com  ??

After thinking about this some more, I think you can simply turn off a preference and you won't get the problem.

Try this and let me know the results:

In your RBD, go to Window --- Preferences --- EGL --- Editor and you will see an option that says "Warn when moving data to a smaller field" ... turn that off and you should be fine

Hello,

Install..,uninstall,...install..,uninstall, install, etc. and now RBD don't start !

Attached log when lauch RBD

paoloc

Paoloc,

I am sorry you having so many issues with RBD. 

First, of all, I would like to make two suggestions that might help you

- When upgrading to a new version/release/fixpack, I would suggest installing a second software development instance.  So, you can keep your old one and then install a new one and upgrade it, delete it, etc without affecting the one that you have working the way you want.     For example, I have 8 different instances from RBD V7.5 to V9.1 and various combinations of 32 bit and 64 bit.

- when you install a new level, please always create a new workspace and import your projects into that new workspace.   You don't state whether you are trying to reuse workspaces between levels. 

On your problem at this point, it seems that you it is having problems with finding Eclipse or within Eclipse itself (which RBD is based on).

I looked up the root cause which was a nullpointerException.

Some possible causes were installing WAS 8.0 in the same location as RBD.   This is not allowed (see RAD doc on this: http://www-01.ibm.com/support/knowledgecenter/#!/SSRTLW_8.0.4/com.ibm.rad.install.doc/topics/t_install_was8.html

Or other WAS/RAD (which would include RBD since RBD is based on RAD)..where it was suggested to "uninstall WAS or any fixpacks) if it was installed in the same folder as RBD.

I am thinking that in the install/uninstall/etc process things have gotten out of sync in the classes.

Can you reinstall one more time and make sure the non-shared directory uses a different folder than you have been using previously.     If you are installing WAS, then make sure it is installed in a separate folder.  

And on this new install, you may also want to change the eclipse.ini to specify a new "shareClasses name)

As shipped -     Xshareclasses:name=IBMSDP_%u

maybe change to:   Xshareclasses:name=IBMSDP2_%u

I

Mark!

The solution proposed by Jeff works. I have no red errors.

Unfortunately your solution to have to install a second software development instance It is not valid if the same  project resides on different instaces. I should reflect the change made in one instance ,manually, into another.

Thanks anyway for the tip.

paoloc

Glad Jeff's solution worked.

On my suggestion, I did not mean that you would do development/maintenance on the code in both platforms as I agree that it is very hard to keep them in sync and is extra work

I just meant that when you do decide to try a new level, then use the suggested approach.   Import the projects into the new workspace and do some testing/experimentation, but keep doing your maintenance/development in the old level.  Then when you are comfortable with the new level, import the latest projects from the old workspace with all the latest changes and start doing your development/maintenance in the new level.

Anyway..glad it is working for you now. 

Mark