[JBoss JIRA] (WFCORE-710) Make ServerOperationResolver handle deployment-overlays similarly to deployments
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-710?page=com.atlassian.jira.plugin... ]
Kabir Khan updated WFCORE-710:
------------------------------
Fix Version/s: 3.0.0.Alpha1
(was: 2.0.0.CR1)
> Make ServerOperationResolver handle deployment-overlays similarly to deployments
> --------------------------------------------------------------------------------
>
> Key: WFCORE-710
> URL: https://issues.jboss.org/browse/WFCORE-710
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Affects Versions: 2.0.0.Alpha2
> Reporter: Kabir Khan
> Assignee: Kabir Khan
> Fix For: 3.0.0.Alpha1
>
>
> Currently in domain mode a
> {code}
> /deployment-overlay=xxx:add(...)
> {code}
> results in a deployment overlay on ALL servers.
> However for deployments
> {code}
> /deployment=xxx:add(...)
> {code}
> does not get pushed to the servers. This happens when it is associated with a server group:
> {code}
> /server-group=zzz/deployment=xxx:add(...)
> {code}
> Similarly
> {code}
> /deployment-overlay=xxx:add(...)
> {code}
> should not get pushed to the servers, until we have a
> {code}
> /server-group=zzz/deployment=yyy:add(...)
> {code}
> which picks out the servers we want to have the overlay
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (JBRULES-1972) Show DRL for decision tables
by Toni Rikkola (JIRA)
[ https://issues.jboss.org/browse/JBRULES-1972?page=com.atlassian.jira.plug... ]
Toni Rikkola resolved JBRULES-1972.
-----------------------------------
Resolution: Done
Just happened to run into this while searching for another ticket. This function is now in both guided and XLS dtables.
> Show DRL for decision tables
> ----------------------------
>
> Key: JBRULES-1972
> URL: https://issues.jboss.org/browse/JBRULES-1972
> Project: JBRULES
> Issue Type: Feature Request
> Components: drools-eclipse
> Reporter: Simon Spielmann
> Fix For: FUTURE
>
>
> Sometimes it is very useful to see the generated drl for a decision table. Without it you can't even set breakpoints.
> I suggest to add a menu item e.g. "show drl" to the context menu for a spreadsheet file in the eclipse ide.
> I think this shouldn't be to hard to implement.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (WFLY-5252) Fix MDB20TestCase
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-5252:
---------------------------------
Summary: Fix MDB20TestCase
Key: WFLY-5252
URL: https://issues.jboss.org/browse/WFLY-5252
Project: WildFly
Issue Type: Bug
Components: Test Suite
Affects Versions: 10.0.0.Beta2
Reporter: Jeff Mesnil
Priority: Minor
Fix For: 10.0.0.CR1
The MDB20TestCase is failing often on our test suite with the error:
{noformat}
java.lang.AssertionError: Reply message was null on reply queue: ActiveMQQueue[ejb2x/replyQueueB]
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertNotNull(Assert.java:621)
at org.jboss.as.test.integration.ejb.mdb.ejb2x.MDB20TopicTestCase.testEjb20TopicMDBs(MDB20TopicTestCase.java:118)
{noformat}
>From the logs, only 1 of the MDB receives the message sent to the topic.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (WFLY-5250) wildfly-jts-application-component-2 quickstart fails to validate in eclipse
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/WFLY-5250?page=com.atlassian.jira.plugin.... ]
Rob Stryker updated WFLY-5250:
------------------------------
Description:
The above quickstart fails to validate in eclipse. It has the following lines in it:
{code}
<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:iiop="urn:iiop"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
urn:iiop jboss-ejb-iiop_1_0.xsd"
version="3.1"
impl-version="2.0">
<assembly-descriptor>
<iiop:iiop>
<ejb-name>InvoiceManagerEJBImpl</ejb-name>
<iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name>
</iiop:iiop>
</assembly-descriptor>
</jboss:ejb-jar>
{code}
The key line to note is:
{code}
urn:iiop jboss-ejb-iiop_1_0.xsd"
{code}
Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you replace this with:
{code}
urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
{code}
However, even once that is fixed, the quickstart still has other problems. For one example:
{code}
cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http://
java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method-
permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/
javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http://
java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application-
exception}' is expected.
{code}
I strongly suggest someone test the quickstart in JBossTools and help come up with a descriptor that passes validation.
was:
The above quickstart fails to validate in eclipse. It has the following lines in it:
{code}
<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:iiop="urn:iiop"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
version="3.1"
impl-version="2.0">
<assembly-descriptor>
<iiop:iiop>
<ejb-name>InvoiceManagerEJBImpl</ejb-name>
<iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name>
</iiop:iiop>
</assembly-descriptor>
</jboss:ejb-jar>
{code}
The key line to note is:
{code}
urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
{code}
Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you replace this with:
{code}
urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
{code}
However, even once that is fixed, the quickstart still has other problems. For one example:
{code}
cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http://
java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method-
permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/
javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http://
java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application-
exception}' is expected.
{code}
I strongly suggest someone test the quickstart in JBossTools and help come up with a descriptor that passes validation.
> wildfly-jts-application-component-2 quickstart fails to validate in eclipse
> ---------------------------------------------------------------------------
>
> Key: WFLY-5250
> URL: https://issues.jboss.org/browse/WFLY-5250
> Project: WildFly
> Issue Type: Bug
> Reporter: Rob Stryker
> Assignee: Jason Greene
>
> The above quickstart fails to validate in eclipse. It has the following lines in it:
> {code}
> <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
> xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:iiop="urn:iiop"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
> http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
> urn:iiop jboss-ejb-iiop_1_0.xsd"
> version="3.1"
> impl-version="2.0">
> <assembly-descriptor>
> <iiop:iiop>
> <ejb-name>InvoiceManagerEJBImpl</ejb-name>
> <iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name>
> </iiop:iiop>
> </assembly-descriptor>
> </jboss:ejb-jar>
> {code}
> The key line to note is:
> {code}
> urn:iiop jboss-ejb-iiop_1_0.xsd"
> {code}
> Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you replace this with:
> {code}
> urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
> {code}
> However, even once that is fixed, the quickstart still has other problems. For one example:
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http://
> java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method-
> permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/
> javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http://
> java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application-
> exception}' is expected.
> {code}
> I strongly suggest someone test the quickstart in JBossTools and help come up with a descriptor that passes validation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months