The RBD v.9.1 and v.9.5 wil be supported for Windows 10 ?

There will be a new fixpack to RBD V.9.1 ? or new release ?

Neither support Windows 10.   The underlying Eclipse level in 9.1 or 9.5 does not support it either.  

As we go forward, we will continue to evaluate the need for it and what the underlying SW stack supports. .

RBD 9.5 needs Java8 but Java8 is not supported for Windows XP.

Does this mean that I have to upgrade to a later Windows version in order to use RBD9.5?

I can continue with Java7?

paoloc

Paoloc,

I looked and the Java website has an FAQ about Windows XP and Java 8 which says it should work but it is not supported.  See my response above about "best effort".  The same would be true for RBD 9.5 and Windows XP with any version of Java.  Given Windows XP is out of support, then RBD no longer claims support for it.

https://www.java.com/en/download/faq/winxp.xml

Now, to answer your question on using Java 7.   The RBD product is compiled using the Java 8 compiler, but with a tolerance level of V6 which means lower levels of the JRE can be used since product such as WAS 7 or WAS 8 do not use Java 8 yet.    To change the JRE, all you need to do is change the JRE specified in the eclipse.ini used at startup.    The -vm specifies the startup directory for the javaw.exe.   If you change this to a Java 7 JRE, it should work.

-vm
C:\RBD95_GM\jdk\jre\bin\javaw.exe
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.library
plugins/org.eclipse.equino

General question on this topic:

In the companies/corporations you work with, how many are planning on moving to Windows 10 in the future?  If so, what time frame?

Thanks...this will help me gauge the interest from a requirements viewpoint. 

Mark

Mark!

For the development I want to stay on XP as long as we can

paoloc

Paoloc,

thanks.   As stated before, we are not doing any testing on Windows XP, so while it may continue to work, there are no guarantees.   Given there are many products/technologies involved here (WAS, Java, Eclipse, RBD, browsers, etc), at some point, one of them may be incompatible with Windows XP.  Therefore, I would suggest you make a plan to upgrade to a newer Windows.

Mark

3 of the 4 developers are already using windows 10 without any problems.

The 4th will be migrated soon.

Bram,

thanks.

Mark

Mark!

two grave errors with rbd95.

First error.

in a new workspace I imported a project exported with RBD 9.1.1

All egl files report error in the istruction:

handler a type JSFHandler...........

Error:
IWN.VAL.6759.e 10/16 The expression is no longer supported and has been removed    a.egl    /documenta71/EGLSource/jsfhandlers    line 10    EDT Problem

Migration was OK:

 Validating project: documenta71
    Running validator: Legacy Workspace Detector (id= LegacyWorkspaceDetector)
    Finished running validator: Legacy Workspace Detector (id= LegacyWorkspaceDetector)
    Running validator: EJB Mapping Validator (id= EjbMappingValidator)
      The project has no EJB model associated with it.  EJB mapping backend validation will not be performed.
    Finished running validator: EJB Mapping Validator (id= EjbMappingValidator)
    Running validator: WebSphere Facet Validator (id= WebSphereFacetValidator)
      The project has no WebSphere runtime associated with it.  WebSphere facet validation will not be performed.
    Finished running validator: WebSphere Facet Validator (id= WebSphereFacetValidator)
    Running validator: WebSphere Runtime Validator (id= WebSphereRuntimeValidator)
      The project has no WebSphere runtime associated with it.  WebSphere runtime validation will not be performed.
    Finished running validator: WebSphere Runtime Validator (id= WebSphereRuntimeValidator)
  Finished validating project: documenta71

Second error:

In only one a Java Program the instruction:

import org.eclipse.jdt.internal.compiler.ast.CastExpression;

Error:

The import org.eclipse cannot be resolved

Any idea?

paoloc

Paoloc,

As stated in the forum stream about RBD 9.5, JSF is no longer supported.   See this link:

https://www.ibm.com/developerworks/community/forums/html/topic?id=29b30fe9-dbe5-44a6-b916-31d5c760813e&ps=25

which contained this text from my post on Sept 25 (and another one earlier)

that is correct.  We announced the deprecation of the JSF support in RBD 9.0 due to the JWL deprecation in RAD, the resources it would take to support later JSF levels, and the strategic direction of the RUI support.  In RBD 9.1, you would have gotten a deprecation warning on the usage JSF related syntax.

 

Given the removal of the JWL support in RAD 9.5 (which EGL was dependent on), we had to remove the support in RBD 9.5. 

 

So, yes you are reading it correctly.

 

For now, you will have to continue to use RBD 9.1.1 or below until you can replace the JSF pages with RUI.

On the second error, it could be related to the removal of JSF, but not sure.   one thought would be to delete (after backing up the project) the Java Classes and folders under EGLGen/JavaSource and then regenerate the project.

Given you have JSF applications, my suggestion would be to stay at RBD 9.1.1. for now.

Mark

Mark!

replace the JSF pages with RUI ? 

This means rewriting the application !!!

It already happened with VisualRPG and VisualAge (to throw it all away), but I did not think that IBM would make me this joke again.

There is an alternative?

paoloc

Paoloc,

The need to remove the JSF support was not taken lightly.  It just was not feasible for RBD to continue supporting it and/or enhancing it.

Switching to RUI is not a complete rewrite.  You should still have a lot of business/data logic in EGL and this could be reused, whether it is at a function, library, service, or program level.

As stated before, RBD 9.1.1 which still has the JSF support will be in support until at least Sept. 2019.

Mark

Mark,

all jsp are to rewrite to RUI, all function must become services,all Javascript  they are to be reviewed.

It costs me 6 months / 1 year of work.

It is a disaster !  I think to block development with RBD (unfortunately again).

paoloc

Paoloc,

I understand and thanks for your input.

At this stage, RBD 9.1.1 has a minimum of 4 years of support left, so I would suggest you use that and at the same time, work on determining a plan on how you want to move forward.
 

Mark

I don't have any problems with 9.1.0 under windows 10.

Hi Bram,

Thanks for reply.

"Maybe" It works apparently in Windows 10 , but it no have IBM support to open PMR.

Regards,

Hsieh

Hsieh,

You are correct in that we would not accept a defect for RBD running on Windows 10.   If you opened a PMR and happened to be running on Windows 10, we would work on it as a "best effort".  But if anything about the problem seemed related to the operating system, then you would have to recreate the same problem on a supported Windows level.

Also, with that said, to my knowledge, RBD itself is not very tied to the Windows level.   I can't remember any problems that were caused or changes we had to make for a certain level of Windows. Things like WAS, Tomcat, and Java itself might be more sensitive to it.    So, again, it may work, but we would not accept a defect.

Mark