[JBoss JIRA] (JBAS-9521) WSDLFilePublisher only deploying schemas with the same name once even if there are more in different subdirectories under a WAR
by Adam Kovari (JIRA)
Adam Kovari created JBAS-9521:
---------------------------------
Summary: WSDLFilePublisher only deploying schemas with the same name once even if there are more in different subdirectories under a WAR
Key: JBAS-9521
URL: https://issues.jboss.org/browse/JBAS-9521
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: JBossAS-5.1.0.GA
Environment: - JBoss AS 5.1.0GA
- JBoss EAP 5.1.{1,2}
- JBoss SOA-P 5.{2,3}
- jbossws-native-3.1.2.SP9
Reporter: Adam Kovari
Assignee: Alessio Soldano
Priority: Minor
Attachments: temp.war
JBoss when deploying WSDLs copies the schemas into <profile>/data/wsdl/... directory. If the original WAR file contains 2 subdirectories which contain 2 XSD schemas with the same name, it will only deploy the schemas from the first directory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-5896) jboss-admin.sh accepts crazy values for :add-proxy()
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/AS7-5896?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar moved MODCLUSTER-264 to AS7-5896:
------------------------------------------------
Project: Application Server 7 (was: mod_cluster)
Key: AS7-5896 (was: MODCLUSTER-264)
Workflow: GIT Pull Request workflow (was: jira)
> jboss-admin.sh accepts crazy values for :add-proxy()
> ----------------------------------------------------
>
> Key: AS7-5896
> URL: https://issues.jboss.org/browse/AS7-5896
> Project: Application Server 7
> Issue Type: Bug
> Environment: modcluster subsystem of AS 7.1 trunk
> Reporter: Misty Stanley-Jones
> Assignee: Radoslav Husar
> Priority: Minor
>
> I am allowed to use all of these kinds of syntax with :add-proxy():
> [domain@localhost:9999 subsystem=modcluster] :add-proxy(host=abc.com,port=123)
> {
> "outcome" => "success",
> "result" => {
> "domain-results" => {"step-1" => undefined},
> "server-operations" => [{
> "servers" => [],
> "operation" => {
> "address" => [("subsystem" => "modcluster")],
> "operation" => "add-proxy",
> "port" => 123,
> "host" => "abc.com",
> "operation-headers" => {"execute-for-coordinator" => true}
> }
> }]
> }
> }
> [domain@localhost:9999 subsystem=modcluster] :add-proxy(host=def.com)
> {
> "outcome" => "success",
> "result" => {
> "domain-results" => {"step-1" => undefined},
> "server-operations" => [{
> "servers" => [],
> "operation" => {
> "address" => [("subsystem" => "modcluster")],
> "operation" => "add-proxy",
> "host" => "def.com",
> "operation-headers" => {"execute-for-coordinator" => true}
> }
> }]
> }
> }
> [domain@localhost:9999 subsystem=modcluster] :add-proxy(port=999)
> {
> "outcome" => "success",
> "result" => {
> "domain-results" => {"step-1" => undefined},
> "server-operations" => [{
> "servers" => [],
> "operation" => {
> "address" => [("subsystem" => "modcluster")],
> "operation" => "add-proxy",
> "port" => 999,
> "operation-headers" => {"execute-for-coordinator" => true}
> }
> }]
> }
> }
> I think only the first one should be valid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-5896) jboss-admin.sh accepts crazy values for :add-proxy()
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/AS7-5896?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar updated AS7-5896:
--------------------------------
Fix Version/s: 7.2.0.Alpha1
Component/s: Clustering
This is actually an AS7 issue. I will take it.
> jboss-admin.sh accepts crazy values for :add-proxy()
> ----------------------------------------------------
>
> Key: AS7-5896
> URL: https://issues.jboss.org/browse/AS7-5896
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Environment: modcluster subsystem of AS 7.1 trunk
> Reporter: Misty Stanley-Jones
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 7.2.0.Alpha1
>
>
> I am allowed to use all of these kinds of syntax with :add-proxy():
> [domain@localhost:9999 subsystem=modcluster] :add-proxy(host=abc.com,port=123)
> {
> "outcome" => "success",
> "result" => {
> "domain-results" => {"step-1" => undefined},
> "server-operations" => [{
> "servers" => [],
> "operation" => {
> "address" => [("subsystem" => "modcluster")],
> "operation" => "add-proxy",
> "port" => 123,
> "host" => "abc.com",
> "operation-headers" => {"execute-for-coordinator" => true}
> }
> }]
> }
> }
> [domain@localhost:9999 subsystem=modcluster] :add-proxy(host=def.com)
> {
> "outcome" => "success",
> "result" => {
> "domain-results" => {"step-1" => undefined},
> "server-operations" => [{
> "servers" => [],
> "operation" => {
> "address" => [("subsystem" => "modcluster")],
> "operation" => "add-proxy",
> "host" => "def.com",
> "operation-headers" => {"execute-for-coordinator" => true}
> }
> }]
> }
> }
> [domain@localhost:9999 subsystem=modcluster] :add-proxy(port=999)
> {
> "outcome" => "success",
> "result" => {
> "domain-results" => {"step-1" => undefined},
> "server-operations" => [{
> "servers" => [],
> "operation" => {
> "address" => [("subsystem" => "modcluster")],
> "operation" => "add-proxy",
> "port" => 999,
> "operation-headers" => {"execute-for-coordinator" => true}
> }
> }]
> }
> }
> I think only the first one should be valid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-5894) jboss-ejb3-ext-api is not marked a jboss api module
by Carlo de Wolf (JIRA)
Carlo de Wolf created AS7-5894:
----------------------------------
Summary: jboss-ejb3-ext-api is not marked a jboss api module
Key: AS7-5894
URL: https://issues.jboss.org/browse/AS7-5894
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.3.Final (EAP)
Reporter: Carlo de Wolf
Assignee: jaikiran pai
jboss-ejb3-ext-api-2.0.0-redhat-2.jar does into org.jboss.ejb3 module which is marked as private.
All classes in jboss-ejb3-ext-api should really be public instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-5762) Allow multiple quoted strings within a CLI command
by James Perkins (JIRA)
James Perkins created AS7-5762:
----------------------------------
Summary: Allow multiple quoted strings within a CLI command
Key: AS7-5762
URL: https://issues.jboss.org/browse/AS7-5762
Project: Application Server 7
Issue Type: Bug
Components: CLI
Reporter: James Perkins
Assignee: Alexey Loubyansky
CLI commands with multiple quotes are not properly parsed.
{code}
/subsystem=logging/console-handler=CONSOLE:write-attribute(name=filter, value="all(match(\"pattern1\"),not(match(\"pattern2\")))")
{code}
I would expect the above command to return the following to the OSH.
{code}
all(match("pattern"),not(match("pattern2")))
{code}
What actually gets passed to the OSH is
{code}
all(match(
{code}
Note this filter syntax relies on PR https://github.com/jbossas/jboss-as/pull/3251
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-5893) CLONE - Empty messaging subsystem can not be persisted
by Tom Fonteyne (JIRA)
Tom Fonteyne created AS7-5893:
---------------------------------
Summary: CLONE - Empty messaging subsystem can not be persisted
Key: AS7-5893
URL: https://issues.jboss.org/browse/AS7-5893
Project: Application Server 7
Issue Type: Feature Request
Components: JMS
Affects Versions: 7.1.3.Final (EAP)
Reporter: Tom Fonteyne
Assignee: Jeff Mesnil
Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
When the messaging subsystem is persisted, it requires to have defined hornetq-server nodes but that's not correct.
E.g. when the messaging subsystem is added through the CLI, it should be marshalled even though there is no hornetq-server
The XSD for the messaging subsystem is correct: minOccurs for hornetq-server element is 0.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month