EAP 6.2.1 patch corrupts patched modules

Latest response

Hi,

I tried to install the EAP 6.2.1 patch via cli. According to CLI the patch was applied successfully and when I restart the JBoss it is coming up with 6.2.1 version. The problem is, that the original .jar files of the patched modules are corrupted now (can not be opened with a zip tool any more). An example is "modules\system\layers\base\org\apache\santuario\xmlsec\main\xmlsec-1.5.5.redhat-2.jar". This gives compile errors in JBDS when using the JBoss container. The environment is Windows 7 with JDK 1.7. Is there any solution to this problem?

Thanks,
Mario

MM
Log in to join the conversation

Responses

Mustafa Musaji's picture Red Hat Guru 1798 points
19 February 2014 12:34 PM

Hi Mario

The patch tool does indeed "corrupt" the original JAR, this is by design [1]

What you'll need to do is download the source for the patch [2] and make sure JBDS checks the source for these instead of the now corrupted files.

I hope this help.

Mustafa

[1] https://github.com/jbossas/jboss-eap/blob/6.2.x/patching/src/main/java/org/jboss/as/patching/runner/PatchModuleInvalidationUtils.java#L144
[2] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=28083&product=appplatform&version=6.2.0&downloadType=patches

sh Active Contributor 155 points
27 February 2014 5:00 PM

The url in [1] above seems invalid currently.

MM Red Hat Pro 605 points
28 February 2014 7:51 AM

Please refer to patching/src/main/java/org/jboss/as/patching/runner/PatchModuleInvalidationUtils.java in jboss-eap-6.2.0-src.zip instead.

Or please refer to wildfly's source code instead. The current implementation is same to EAP 6.2.0 one.

NP Community Member 20 points
22 April 2014 9:37 AM

Is there any explanation for why the jar files are invalidated? Or which jar files to use instead?

We use for example the org.jboss.as.cli.CommandContext class from the system\layers\base\org\jboss\as\cli\main module (jboss-as-cli-7.3.0.Final-redhat-14.jar).

Wolf-Dieter Fink's picture Red Hat Pro 533 points
2 May 2014 11:04 AM

The modules should not be used. It is an internal implementation detail.

The modules directory should not be used to build applications and clients should not depend on that.

If you build applications you should use the provided maven repositories.
A client should use the provided libraries from bin/client folder

John Liptak's picture Community Member 30 points
1 July 2014 9:53 PM

Unfortunately, when you add servers in eclipse, it adds dependencies to modules rather than maven. Any solution to that?

David Powles's picture Red Hat 25369 points
2 July 2014 4:36 AM

Might be better to start a new topic for this one, John.

Wolf-Dieter Fink's picture Red Hat Pro 533 points
2 July 2014 1:20 PM

Does https://issues.jboss.org/browse/JBIDE-17025 helps?

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.