[JBoss JIRA] (WFLY-4811) Batch subsystem should be renamed batch-jberet and the model updated for usabliity
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-4811?page=com.atlassian.jira.plugin.... ]
James Perkins updated WFLY-4811:
--------------------------------
Description:
The batch subsystem is currently not designed well. The model needs to be updated for better validation and usability. During this process the resource should be renamed to {{batch-jberet}}.
Current model:
{code}
{
"outcome" => "success",
"result" => {
"job-repository-type" => "in-memory",
"job-repository" => {"jdbc" => {"jndi-name" => undefined}},
"thread-factory" => undefined,
"thread-pool" => {"batch" => {
"keepalive-time" => {
"time" => 30L,
"unit" => "SECONDS"
},
"max-threads" => 10,
"name" => "batch",
"thread-factory" => undefined
}}
}
}
{code}
If possible the {{thread-factory}} should be removed and the {{thread-pool}} should use attribute groups.
The {{job-repository-type}} will be removed as well as the {{job-repository=jdbc}}. A new {{jdbc-job-repository}} and {{in-memory-job-repository}} resource will be added. There will also be a {{default-job-repository}} which will accept a name from one of the defined job repositories.
The {{jndi-name}} will no longer be used and a {{data-source}} name will be used for the JDBC job repository. For example resource value might be {{ExampleDS}}.
A new deployment descriptor will be added to allow a user to defined a job repository configured on the subsystem.
Due to these changes the persisted XML will likely need some small alterations. Mainly ensuring a name attribute is persisted and multiple repositories are allowed to be defined.
was:
The batch subsystem is currently not designed well. The model needs to be updated for better validation and usability. During this process the resource should be renamed to {{batch-jberet}}.
Current model:
{code}
{
"outcome" => "success",
"result" => {
"job-repository-type" => "in-memory",
"job-repository" => {"jdbc" => {"jndi-name" => undefined}},
"thread-factory" => undefined,
"thread-pool" => {"batch" => {
"keepalive-time" => {
"time" => 30L,
"unit" => "SECONDS"
},
"max-threads" => 10,
"name" => "batch",
"thread-factory" => undefined
}}
}
}
{code}
If possible the {{thread-factory}} should be removed and the {{thread-pool}} should use attribute groups.
The {{job-repository-type}} will be removed as well as the {{job-repository=jdbc}}. A new {{jdbc-job-repository}} and {{in-memory-job-repository}} resource will be added. There will also be a {{default-job-repository}} which will accept a name from one of the defined job repositories.
A new deployment descriptor will be added to allow a user to defined a job repository configured on the subsystem.
Due to these changes the persisted XML will likely need some small alterations. Mainly ensuring a name attribute is persisted and multiple repositories are allowed to be defined.
> Batch subsystem should be renamed batch-jberet and the model updated for usabliity
> ----------------------------------------------------------------------------------
>
> Key: WFLY-4811
> URL: https://issues.jboss.org/browse/WFLY-4811
> Project: WildFly
> Issue Type: Enhancement
> Components: Batch
> Reporter: James Perkins
> Assignee: James Perkins
> Fix For: 10.0.0.Final
>
>
> The batch subsystem is currently not designed well. The model needs to be updated for better validation and usability. During this process the resource should be renamed to {{batch-jberet}}.
> Current model:
> {code}
> {
> "outcome" => "success",
> "result" => {
> "job-repository-type" => "in-memory",
> "job-repository" => {"jdbc" => {"jndi-name" => undefined}},
> "thread-factory" => undefined,
> "thread-pool" => {"batch" => {
> "keepalive-time" => {
> "time" => 30L,
> "unit" => "SECONDS"
> },
> "max-threads" => 10,
> "name" => "batch",
> "thread-factory" => undefined
> }}
> }
> }
> {code}
> If possible the {{thread-factory}} should be removed and the {{thread-pool}} should use attribute groups.
> The {{job-repository-type}} will be removed as well as the {{job-repository=jdbc}}. A new {{jdbc-job-repository}} and {{in-memory-job-repository}} resource will be added. There will also be a {{default-job-repository}} which will accept a name from one of the defined job repositories.
> The {{jndi-name}} will no longer be used and a {{data-source}} name will be used for the JDBC job repository. For example resource value might be {{ExampleDS}}.
> A new deployment descriptor will be added to allow a user to defined a job repository configured on the subsystem.
> Due to these changes the persisted XML will likely need some small alterations. Mainly ensuring a name attribute is persisted and multiple repositories are allowed to be defined.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4811) Batch subsystem should be renamed batch-jberet and the model updated for usabliity
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-4811?page=com.atlassian.jira.plugin.... ]
James Perkins reassigned WFLY-4811:
-----------------------------------
Assignee: James Perkins (was: Cheng Fang)
> Batch subsystem should be renamed batch-jberet and the model updated for usabliity
> ----------------------------------------------------------------------------------
>
> Key: WFLY-4811
> URL: https://issues.jboss.org/browse/WFLY-4811
> Project: WildFly
> Issue Type: Enhancement
> Components: Batch
> Reporter: James Perkins
> Assignee: James Perkins
> Fix For: 10.0.0.Final
>
>
> The batch subsystem is currently not designed well. The model needs to be updated for better validation and usability. During this process the resource should be renamed to {{batch-jberet}}.
> Current model:
> {code}
> {
> "outcome" => "success",
> "result" => {
> "job-repository-type" => "in-memory",
> "job-repository" => {"jdbc" => {"jndi-name" => undefined}},
> "thread-factory" => undefined,
> "thread-pool" => {"batch" => {
> "keepalive-time" => {
> "time" => 30L,
> "unit" => "SECONDS"
> },
> "max-threads" => 10,
> "name" => "batch",
> "thread-factory" => undefined
> }}
> }
> }
> {code}
> If possible the {{thread-factory}} should be removed and the {{thread-pool}} should use attribute groups.
> The {{job-repository-type}} will be removed as well as the {{job-repository=jdbc}}. A new {{jdbc-job-repository}} and {{in-memory-job-repository}} resource will be added. There will also be a {{default-job-repository}} which will accept a name from one of the defined job repositories.
> A new deployment descriptor will be added to allow a user to defined a job repository configured on the subsystem.
> Due to these changes the persisted XML will likely need some small alterations. Mainly ensuring a name attribute is persisted and multiple repositories are allowed to be defined.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4811) Batch subsystem should be renamed batch-jberet and the model updated for usabliity
by James Perkins (JIRA)
James Perkins created WFLY-4811:
-----------------------------------
Summary: Batch subsystem should be renamed batch-jberet and the model updated for usabliity
Key: WFLY-4811
URL: https://issues.jboss.org/browse/WFLY-4811
Project: WildFly
Issue Type: Enhancement
Components: Batch
Reporter: James Perkins
Assignee: Cheng Fang
Fix For: 10.0.0.Final
The batch subsystem is currently not designed well. The model needs to be updated for better validation and usability. During this process the resource should be renamed to {{batch-jberet}}.
Current model:
{code}
{
"outcome" => "success",
"result" => {
"job-repository-type" => "in-memory",
"job-repository" => {"jdbc" => {"jndi-name" => undefined}},
"thread-factory" => undefined,
"thread-pool" => {"batch" => {
"keepalive-time" => {
"time" => 30L,
"unit" => "SECONDS"
},
"max-threads" => 10,
"name" => "batch",
"thread-factory" => undefined
}}
}
}
{code}
If possible the {{thread-factory}} should be removed and the {{thread-pool}} should use attribute groups.
The {{job-repository-type}} will be removed as well as the {{job-repository=jdbc}}. A new {{jdbc-job-repository}} and {{in-memory-job-repository}} resource will be added. There will also be a {{default-job-repository}} which will accept a name from one of the defined job repositories.
A new deployment descriptor will be added to allow a user to defined a job repository configured on the subsystem.
Due to these changes the persisted XML will likely need some small alterations. Mainly ensuring a name attribute is persisted and multiple repositories are allowed to be defined.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JGRP-1934) Add external protocol ID to jg-protocol-ids.xml
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1934?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1934:
--------------------------------
OK, I added an attribute {{external}} to {{jg-protocol-ids.xml}} and {{jg-magic-map.xml}}. If true, JGroups won't load the class at initialization time:
{noformat}
<!-- Reserved IDs for external classes: [500..1000] -->
<class id="500" name="org.jgroups.protocols.azure.AZURE_PING" external="true"/>
{noformat}
IDs for external protocols have to start at 500.
> Add external protocol ID to jg-protocol-ids.xml
> -----------------------------------------------
>
> Key: JGRP-1934
> URL: https://issues.jboss.org/browse/JGRP-1934
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.6.4
>
>
> If some external project needs a protocol ID, allow to add an external protocol to {{jg-protocol-ids.xml}}.
> Possibly do the same for magic numbers ({{jg-magic-map.xml}}).
> This needs to be marked specially, so we don't try to load that protocol / class.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFCORE-570) Provide ability to display module dependencies via Management API
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-570?page=com.atlassian.jira.plugin... ]
Tomaz Cerar edited comment on WFCORE-570 at 6/19/15 9:46 AM:
-------------------------------------------------------------
Sample output of current WIP
{noformat}
[standalone@localhost:9990 /] /core-service=module-loading:module-info(name=io.undertow.core)
{
"outcome" => "success",
"result" => {
"name" => "io.undertow.core:main",
"fallback-loader" => "<not defined>",
"dependencies" => [
{
"dependency-name" => "ModuleDependency",
"module-name" => "org.jboss.xnio:main",
"export-filter" => "Reject",
"import-filter" => "multi-path filter {exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}",
"optional" => false
},
{
"dependency-name" => "ModuleDependency",
"module-name" => "org.jboss.xnio.nio:main",
"export-filter" => "Reject",
"import-filter" => "multi-path filter {include equals \"META-INF/services\", include children of \"META-INF/services/\", exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}",
"optional" => false
},
{
"dependency-name" => "ModuleDependency",
"module-name" => "org.jboss.logging:main",
"export-filter" => "Reject",
"import-filter" => "multi-path filter {exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}",
"optional" => false
},
{
"dependency-name" => "ModuleDependency",
"module-name" => "javax.api:main",
"export-filter" => "Reject",
"import-filter" => "multi-path filter {exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}",
"optional" => false
},
{
"dependency-name" => "ModuleDependency",
"module-name" => "sun.jdk:main",
"export-filter" => "Reject",
"import-filter" => "multi-path filter {exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}",
"optional" => false
}
],
"resource-loaders" => [
{
"type" => "org.jboss.modules.JarFileResourceLoader",
"paths" => [
"",
"io/undertow/security/idm",
"META-INF/maven/io.undertow/undertow-core",
"io/undertow/websockets/core",
"io/undertow/server/session",
"io/undertow/websockets/core/protocol/version13",
"META-INF/maven/io.undertow",
"io/undertow/server/handlers/error",
"io/undertow/security",
"io/undertow/server/protocol/http",
"io/undertow/client/spdy",
"io/undertow/protocols/spdy",
"io/undertow/server",
"io/undertow/protocols/ajp",
"io/undertow/client",
"io/undertow/protocols/http2",
"io/undertow/websockets/core/protocol/version08",
"io/undertow/client/http2",
"io",
"io/undertow/client/http",
"io/undertow/security/api",
"io/undertow/server/handlers/builder",
"io/undertow/websockets/client",
"io/undertow/server/protocol/spdy",
"io/undertow/conduits",
"io/undertow/server/protocol",
"io/undertow/websockets/core/protocol/version07",
"META-INF",
"io/undertow/websockets",
"io/undertow/server/handlers/cache",
"io/undertow/client/ajp",
"META-INF/maven",
"io/undertow/protocols",
"io/undertow/server/protocol/framed",
"io/undertow",
"io/undertow/server/handlers/resource",
"io/undertow/server/handlers/proxy",
"io/undertow/server/handlers/accesslog",
"META-INF/services",
"io/undertow/security/handlers",
"io/undertow/server/handlers/encoding",
"io/undertow/server/handlers/proxy/mod_cluster",
"io/undertow/websockets/spi",
"io/undertow/server/protocol/ajp",
"io/undertow/server/handlers",
"io/undertow/server/protocol/http2",
"io/undertow/server/handlers/sse",
"io/undertow/server/handlers/form",
"io/undertow/util",
"io/undertow/security/impl",
"io/undertow/websockets/core/protocol",
"io/undertow/predicate",
"io/undertow/websockets/extensions",
"io/undertow/protocols/ssl",
"io/undertow/attribute",
"io/undertow/channels",
"io/undertow/websockets/core/function",
"io/undertow/io"
]
},
{
"type" => "org.jboss.modules.NativeLibraryResourceLoader",
"paths" => undefined
}
]
}
}
{noformat}
was (Author: ctomc):
Sample output of current WIP
{noformat}
[standalone@localhost:9990 /] /core-service=module-loading:module-info(name=io.undertow.core)
{
"outcome" => "success",
"result" => {
"name" => "io.undertow.core:main",
"fallback-loader" => "<not defined>",
"dependencies" => [
{
"dependency-name" => "ModuleDependency",
"module-name" => "org.jboss.xnio:main",
"export-filter" => "Reject",
"import-filter" => "multi-path filter {exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}",
"optional" => false
},
{
"dependency-name" => "ModuleDependency",
"module-name" => "org.jboss.xnio.nio:main",
"export-filter" => "Reject",
"import-filter" => "multi-path filter {include equals \"META-INF/services\", include children of \"META-INF/services/\", exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}",
"optional" => false
},
{
"dependency-name" => "ModuleDependency",
"module-name" => "org.jboss.logging:main",
"export-filter" => "Reject",
"import-filter" => "multi-path filter {exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}",
"optional" => false
},
{
"dependency-name" => "ModuleDependency",
"module-name" => "javax.api:main",
"export-filter" => "Reject",
"import-filter" => "multi-path filter {exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}",
"optional" => false
},
{
"dependency-name" => "ModuleDependency",
"module-name" => "sun.jdk:main",
"export-filter" => "Reject",
"import-filter" => "multi-path filter {exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}",
"optional" => false
}
],
"resource-loaders" => [
{
"type" => "org.jboss.modules.JarFileResourceLoader",
"paths" => "[, io/undertow/security/idm, META-INF/maven/io.undertow/undertow-core, io/undertow/websockets/core, io/undertow/server/session, io/undertow/websockets/core/protocol/version13, META-INF/maven/io.undertow, io/undertow/server
/handlers/error, io/undertow/security, io/undertow/server/protocol/http, io/undertow/client/spdy, io/undertow/protocols/spdy, io/undertow/server, io/undertow/protocols/ajp, io/undertow/client, io/undertow/protocols/http2, io/undertow/websockets/core/
protocol/version08, io/undertow/client/http2, io, io/undertow/client/http, io/undertow/security/api, io/undertow/server/handlers/builder, io/undertow/websockets/client, io/undertow/server/protocol/spdy, io/undertow/conduits, io/undertow/server/protoc
ol, io/undertow/websockets/core/protocol/version07, META-INF, io/undertow/websockets, io/undertow/server/handlers/cache, io/undertow/client/ajp, META-INF/maven, io/undertow/protocols, io/undertow/server/protocol/framed, io/undertow, io/undertow/serve
r/handlers/resource, io/undertow/server/handlers/proxy, io/undertow/server/handlers/accesslog, META-INF/services, io/undertow/security/handlers, io/undertow/server/handlers/encoding, io/undertow/server/handlers/proxy/mod_cluster, io/undertow/websocke
ts/spi, io/undertow/server/protocol/ajp, io/undertow/server/handlers, io/undertow/server/protocol/http2, io/undertow/server/handlers/sse, io/undertow/server/handlers/form, io/undertow/util, io/undertow/security/impl, io/undertow/websockets/core/proto
col, io/undertow/predicate, io/undertow/websockets/extensions, io/undertow/protocols/ssl, io/undertow/attribute, io/undertow/channels, io/undertow/websockets/core/function, io/undertow/io]"
},
{
"type" => "org.jboss.modules.NativeLibraryResourceLoader",
"paths" => "[]"
}
]
}
}
{noformat}
> Provide ability to display module dependencies via Management API
> -----------------------------------------------------------------
>
> Key: WFCORE-570
> URL: https://issues.jboss.org/browse/WFCORE-570
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI, Domain Management
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 2.0.0.Alpha5
>
>
> Provide ability to display module dependencies via Management API
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JGRP-1934) Add external protocol ID to jg-protocol-ids.xml
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1934?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1934:
---------------------------
Description:
If some external project needs a protocol ID, allow to add an external protocol to {{jg-protocol-ids.xml}}.
Possibly do the same for magic numbers ({{jg-magic-map.xml}}).
This needs to be marked specially, so we don't try to load that protocol / class.
was:
If some external project needs a protocol ID, allow to add an external protocol to {{jg-protocol-ids.xml}}.
Possibly do the same for magic numbers ({{jg-magic-map.xml}})
> Add external protocol ID to jg-protocol-ids.xml
> -----------------------------------------------
>
> Key: JGRP-1934
> URL: https://issues.jboss.org/browse/JGRP-1934
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.6.4
>
>
> If some external project needs a protocol ID, allow to add an external protocol to {{jg-protocol-ids.xml}}.
> Possibly do the same for magic numbers ({{jg-magic-map.xml}}).
> This needs to be marked specially, so we don't try to load that protocol / class.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JGRP-1934) Add external protocol ID to jg-protocol-ids.xml
by Bela Ban (JIRA)
Bela Ban created JGRP-1934:
------------------------------
Summary: Add external protocol ID to jg-protocol-ids.xml
Key: JGRP-1934
URL: https://issues.jboss.org/browse/JGRP-1934
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 3.6.4
If some external project needs a protocol ID, allow to add an external protocol to {{jg-protocol-ids.xml}}.
Possibly do the same for magic numbers ({{jg-magic-map.xml}})
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month