K
Karl Uppiano
When my RAR MANIFEST.MF contains the following entries,
Extension-Name: my-ra
Specification-Vendor: my-vendor
Implementation-Vendor: my-vendor
Implementation-Title: my-ra
Implementation-Version: my-version
WebLogic 9.2 throws the exception:
weblogic.connector.exception.RAException: Trying to version a resource
adapter that is not versionable
at
weblogic.connector.common.RAInstanceManager.initialize(RAInstanceManager.java:1141)
...
..when I attempt to activate changes to my newly installed application
archive.
It seems supremely presumptuous of WebLogic to assume that I intend to
implement versionable support simply because Maven elects to include
versioning information in all archives that it generates. My question is,
does anyone know how I might either
a) Make an entry in the RA deployment descriptor to disable the appserver
from attempting to version the RA, or
b) Inhibit the Maven archiver from making the entries that are inciting
WebLogic to attempt to version the RA
Extension-Name: my-ra
Specification-Vendor: my-vendor
Implementation-Vendor: my-vendor
Implementation-Title: my-ra
Implementation-Version: my-version
WebLogic 9.2 throws the exception:
weblogic.connector.exception.RAException: Trying to version a resource
adapter that is not versionable
at
weblogic.connector.common.RAInstanceManager.initialize(RAInstanceManager.java:1141)
...
..when I attempt to activate changes to my newly installed application
archive.
It seems supremely presumptuous of WebLogic to assume that I intend to
implement versionable support simply because Maven elects to include
versioning information in all archives that it generates. My question is,
does anyone know how I might either
a) Make an entry in the RA deployment descriptor to disable the appserver
from attempting to version the RA, or
b) Inhibit the Maven archiver from making the entries that are inciting
WebLogic to attempt to version the RA