Description of problem:

Customers using certain sun.jdk dependencies make amendments to the module.xml to include the following

- for working with javax.sql.rowset.RowSetProvider
                 <path name="com/sun/rowset"/>
                 <path name="com/sun/rowset/providers"/>

- for working with java.lang.invoke.MethodHandleProxies
                 <path name="sun/invoke"/>

In CP releases that happen to override original sun.jdk module.xml means customers configurations are broken and changes have to be reapplied to each CP.

This bug is to get the above included in upstream and next release so it's included in future CP releases.

We should not be blocking customers using these classes in my opinion and should include them out of the box.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Use EAP 6.3.1 that includes dependency to sun/invoke in a sun.jdk module.xml
2. Upgrade to 6.3.2 and test again
3.

Actual results:
Test will fail where 6.3.2 is using module.xml from .overlays

Expected results:
Test should not be affected as these classes should be included by default

Additional info: