Last updated on MARCH 08, 2017
Applies to:Oracle JDeveloper - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 12c]
Information in this document applies to any platform.
Upon running a deployment of a Java application in JDeveloper 184.108.40.206.0 following messages are returned:
[02:23:31 PM] ---- Deployment started. ----
[02:23:31 PM] Target platform is Standard Java EE.
[02:23:31 PM] Running dependency analysis...
[02:23:31 PM] Building...
[02:23:31 PM] Deploying profile...
[02:23:31 PM] Deployment cancelled.
[02:23:31 PM] ---- Deployment incomplete ----.
[02:23:31 PM] Unable to package module
[02:23:31 PM] Cannot construct a stateful Packager for given set of Filegroups
[02:23:31 PM] DefaultStatefulFileGroupsPackagerProvider could not handle filegroup with type 2
[02:23:31 PM] Cannot construct a stateful Packager for given Filegroup
[02:23:31 PM] A stateful ArchiveEntry Processor could not be built for oracle.jdeveloper.deploy.common.ProjectFileGroup
[02:23:31 PM] A StatefulProcessor that supports oracle.jdeveloper.deploy.ArchiveEntry could not be found for Contributor filegroup.
[02:23:31 PM] Cannot construct OffsetPath processor for filegroup oracle.jdeveloper.deploy.common.ProjectFileGroup
[02:23:31 PM] A StatefulProcessor that supports oracle.jdeveloper.deploy.pkg.contrib.OffsetPath could not be found for Contributor filegroup.
[02:23:31 PM] Cannot create toolkit for oracle.jdeveloper.deploy.contrib.spi.StatefulProcessor
[02:23:31 PM] jar-file not recognized in given context. Requested: oracle.jdeveloper.deploy.contrib.spi.StatefulProcessor
The deploy jar file is not created
This used to work in older versions.
Upgrade to JDeveloper 220.127.116.11.0
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms