[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26793:
------------------------------------
Steps to Reproduce:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name *Bean1*
5) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_2_0.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
</beans>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
was:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name *Bean1*
5) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_2_0.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
</beans>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26793:
------------------------------------
Steps to Reproduce:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name *Bean1*
5) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_2_0.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
</beans>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
was:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name *Bean1*
5) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_2_0.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
</beans>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26793:
------------------------------------
Steps to Reproduce:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name *Bean1*
5) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_2_0.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
</beans>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
was:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name Bean1
5) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_2_0.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
</beans>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26793:
------------------------------------
Steps to Reproduce:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name Bean1
5) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_2_0.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
</beans>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
was:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name Bean1
5) Add the following code to the beans.xml file
{code:xml}
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26793:
------------------------------------
Steps to Reproduce:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name Bean1
5) Add the following code to the beans.xml file
{code:xml}
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
was:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all* and extend the <beans> openning tag by adding the following code <beans {color:#DE350B}_here_{color} >:
{code:java}
xmlns:weld="http://jboss.org/schema/weld/beans"
{code}
3) Create new package with name *exclude.p1*
4) Create new Bean with name Bean1
5) Add the following code to the beans.xml file
{code:xml}
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26793:
------------------------------------
Steps to Reproduce:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all* and extend the <beans> openning tag by adding the following code <beans {color:#DE350B}_here_{color} >:
{code:java}
xmlns:weld="http://jboss.org/schema/weld/beans"
{code}
3) Create new package with name *exclude.p1*
4) Create new Bean with name Bean1
5) Add the following code to the beans.xml file
{code:xml}
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
was:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name Bean1
5) Add the following code to the beans.xml file
{code:xml}
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26793:
------------------------------------
Steps to Reproduce:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name Bean1
5) Add the following code to the beans.xml file
{code:xml}
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
was:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name Bean1
5) Add the following code to the beans.xml file
{code:xml}
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26793:
------------------------------------
Environment: OS X, RHEL 7, Windows 10 (was: OS X, RHEL 7, Windows 10 (both java 8 and java 11))
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26793:
------------------------------------
Steps to Reproduce:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name Bean1
5) Add the following code to the beans.xml file
{code:xml}
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10 (both java 8 and java 11)
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by Josef Kopriva (Jira)
Josef Kopriva created JBIDE-26794:
-------------------------------------
Summary: OpenShift: Remote debugging is very slow
Key: JBIDE-26794
URL: https://issues.jboss.org/browse/JBIDE-26794
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.11.0.Final
Environment: Version: 12.11.0.GA
Build id: GA-v20190329-0120-B4247
Build date: 20190329-0120
RHPDS
Reporter: Josef Kopriva
>From Email on devtools-team:
{code:java}
Hi Folks:
Using this version of Code Ready Studio
Version: 12.11.0.GA
Build id: GA-v20190329-0120-B4247
Build date: 20190329-0120
I recently ran an Openshift Starter Workshop lab and witnessed a clear
issue with Code Ready Studio and INtelliJ
Workshop Starter Lab
(http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
Lab 19 has a remote debugging setup. The remote debugger in Code Ready
connected very very slowly and would not step over or step out making
using it as a debugger virtually impossible.
One of the lab participants had IntelliJ and it connected immediately
and worked just fine.
Clearly, something is broken in CRS. Maybe someone would want to test
this out and fix?
You can find this lab on RHPDS.
Just FYI to the PM's.
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months