-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
In order to support AS7-3694 I need to associate a META-INF/jboss-all.xml descriptor with a bundle deployment. I currently do this in six discrete steps
{
"address" => ("deployment-overlay" => "bundle-b.jar/META-INF/jboss-all.xml"),
"operation" => "add"
}
{
"address" => undefined,
"operation" => "upload-deployment-stream",
"input-stream-index" => 0
}
{
"address" => [
("deployment-overlay" => "bundle-b.jar/META-INF/jboss-all.xml"),
("content" => "META-INF/jboss-all.xml")
],
"operation" => "add",
"content" => {"hash" => bytes {
0xdb, 0x79, 0x11, 0xff, 0xdf, 0x8f, 0xfc, 0x65,
0xc2, 0xe3, 0x6b, 0x20, 0xa5, 0x89, 0xa7, 0xdb,
0x10, 0xed, 0xcc, 0xc0
}}
}
{
"address" => [
("deployment-overlay" => "bundle-b.jar/META-INF/jboss-all.xml"),
("deployment" => "bundle-b.jar")
],
"operation" => "add"
}
{
"operation" => "add",
"address" => [("deployment" => "bundle-b.jar")],
"runtime-name" => "bundle-b.jar",
"content" => [{"input-stream-index" => 0}]
}
{
"operation" => "deploy",
"address" => [("deployment" => "bundle-b.jar")]
}
As far as I know these cannot be combined in a composite operation because step #3 uses the result of #2.
The management API should allow this to happen in a single composite operation.
