September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1023) Use datasource class as default

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1023?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1023: ------------------------------------------------ Martin Simka <msimka(a)redhat.com> changed the Status of [bug 1019186|https://bugzilla.redhat.com/show_bug.cgi?id=1019186] from ASSIGNED to CLOSED > Use datasource class as default > ------------------------------- > > Key: JBJCA-1023 > URL: https://issues.jboss.org/browse/JBJCA-1023 > Project: IronJacamar > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JDBC > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.1.0.Beta5 > > > Switch priority from driver class to datasource class -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3701) Investigate HTTPSManagementInterfaceTestCase.testHTTPS and HTTPSWebConnectorTestCase.testVerifyingConnector failures

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3701?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3701: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1136412|https://bugzilla.redhat.com/show_bug.cgi?id=1136412] from POST to MODIFIED > Investigate HTTPSManagementInterfaceTestCase.testHTTPS and HTTPSWebConnectorTestCase.testVerifyingConnector failures > --------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-3701 > URL: https://issues.jboss.org/browse/WFLY-3701 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 9.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > Those tests are failing on Brontes: > http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=19132&tab=buil... > Need to investigate -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3189) Error validating jboss-ejb3.xml.

by Michael Hauke (JIRA)

[ https://issues.jboss.org/browse/WFLY-3189?page=com.atlassian.jira.plugin.... ] Michael Hauke commented on WFLY-3189: ------------------------------------- Would https://github.com/jbosstools/jbosstools-server be the correct repository to fork? > Error validating jboss-ejb3.xml. > -------------------------------- > > Key: WFLY-3189 > URL: https://issues.jboss.org/browse/WFLY-3189 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Final > Environment: WildFly 8.0.0.Final > Reporter: shinzey shinzey > Assignee: David Lloyd > Attachments: p.patch > > > I'm trying to configure code completion for jboss-ejb3.xml with schema, but fail to do that due to the following validation error: > {noformat} > src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' to a(n) 'type definition' component. [33] > src-resolve: Cannot resolve the name 'javaee:jboss-ejb-jarType' to a(n) 'type definition' component. [35] > src-resolve: Cannot resolve the name 'javaee:jboss-enterprise-beansType' to a(n) 'type definition' component. [37] > src-resolve: Cannot resolve the name 'javaee:assembly-descriptor-entry' to a(n) 'element declaration' component. [35] > src-resolve: Cannot resolve the name 'javaee:jboss-assembly-descriptor-bean-entryType' to a(n) 'type definition' component. [39] > {noformat} > The jboss-ejb3.xml is quite simple: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <jboss:ejb-jar version="3.1" impl-version="2.0" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns:s="urn:security:1.1" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd > http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd"> > <assembly-descriptor> > <s:security> > <ejb-name>*</ejb-name> > <s:security-domain>testsd</s:security-domain> > </s:security> > </assembly-descriptor> > </jboss:ejb-jar> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3189) Error validating jboss-ejb3.xml.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-3189?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on WFLY-3189: ------------------------------------------- [~mchlhke] can you create github PR to make review/feedback easier ? > Error validating jboss-ejb3.xml. > -------------------------------- > > Key: WFLY-3189 > URL: https://issues.jboss.org/browse/WFLY-3189 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Final > Environment: WildFly 8.0.0.Final > Reporter: shinzey shinzey > Assignee: David Lloyd > Attachments: p.patch > > > I'm trying to configure code completion for jboss-ejb3.xml with schema, but fail to do that due to the following validation error: > {noformat} > src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' to a(n) 'type definition' component. [33] > src-resolve: Cannot resolve the name 'javaee:jboss-ejb-jarType' to a(n) 'type definition' component. [35] > src-resolve: Cannot resolve the name 'javaee:jboss-enterprise-beansType' to a(n) 'type definition' component. [37] > src-resolve: Cannot resolve the name 'javaee:assembly-descriptor-entry' to a(n) 'element declaration' component. [35] > src-resolve: Cannot resolve the name 'javaee:jboss-assembly-descriptor-bean-entryType' to a(n) 'type definition' component. [39] > {noformat} > The jboss-ejb3.xml is quite simple: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <jboss:ejb-jar version="3.1" impl-version="2.0" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns:s="urn:security:1.1" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd > http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd"> > <assembly-descriptor> > <s:security> > <ejb-name>*</ejb-name> > <s:security-domain>testsd</s:security-domain> > </s:security> > </assembly-descriptor> > </jboss:ejb-jar> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-82) Further review of TrivialSaltedDigestPassword naming

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-82: ----------------------------------- Summary: Further review of TrivialSaltedDigestPassword naming Key: ELY-82 URL: https://issues.jboss.org/browse/ELY-82 Project: WildFly Elytron Issue Type: Task Security Level: Public (Everyone can see) Components: Password Types Reporter: Darran Lofthouse Fix For: 1.0.0.Beta1 Can we find a better name for it? It is not specific to a vendor but commonly only described as a simple approach that can be used to add salt to a password. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3724) Batch jobs don't receive partition-specific parameters

by Ari Silvan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3724?page=com.atlassian.jira.plugin.... ] Ari Silvan commented on WFLY-3724: ---------------------------------- OK. That sample: http://javaee-samples.github.io/sample/batch-chunk-mapper/ shows the correct way to handle partition properties. > Batch jobs don't receive partition-specific parameters > ------------------------------------------------------ > > Key: WFLY-3724 > URL: https://issues.jboss.org/browse/WFLY-3724 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Batch > Affects Versions: 8.1.0.Final > Environment: Windows 7 Home Premium Service Pack 1 64-bit + JDK8u11 + WildFly 8.1.0 Final > Reporter: Ari Silvan > Assignee: Enrique González Martínez > > When defining a batch job chunk step to run as partitions, ItemReader doesn't receive the partition-specific parameters specified by an implementation of the PartitionPlan interface. Parameters are null. See steps to reproduce for further details. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2492) <valid-connection-checker> does not have module attribute

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2492?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2492: ----------------------------------------------- tom.jenkinson(a)redhat.com changed the Status of [bug 1029311|https://bugzilla.redhat.com/show_bug.cgi?id=1029311] from NEW to CLOSED > <valid-connection-checker> does not have module attribute > --------------------------------------------------------- > > Key: WFLY-2492 > URL: https://issues.jboss.org/browse/WFLY-2492 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: James Livingston > Assignee: Stefano Maestri > Priority: Minor > > A datasource's <valid-connection-checker> element lets you specify the class name. It does not let you specify the module name, so you can only use IJ-provided ones. It should let you specify a module name too, so you can use custom connection checkers. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3804) WildFly Multi JSF Feature do not support myfaces 1.2

by roman jablonka (JIRA)

[ https://issues.jboss.org/browse/WFLY-3804?page=com.atlassian.jira.plugin.... ] roman jablonka commented on WFLY-3804: -------------------------------------- I have done alike the discription Steps to add any new JSF implementation or version to WildFly on WildFly 8.1.0 final and test ist with the provided test application there for mojarra-1.2_15 which works as expected myfaces-2.1.14 which works as expected myfaces-1.2.12 which produces exception while deployment, and is marked deployment failed. MyFaces 1.2.12 is an implementation of Faces 1.2, so I would expect, it is working at WildFly. if nessesary, I can provide the slot installation cli and of course the testapplications. > WildFly Multi JSF Feature do not support myfaces 1.2 > ---------------------------------------------------- > > Key: WFLY-3804 > URL: https://issues.jboss.org/browse/WFLY-3804 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Class Loading, JSF > Affects Versions: 8.1.0.Final > Environment: Windows 7 64, Java 8 64 (jdk1.8_11) Myfaces Slot 1.2.12 > Reporter: roman jablonka > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3804) WildFly Multi JSF Feature do not support myfaces 1.2

by roman jablonka (JIRA)

roman jablonka created WFLY-3804: ------------------------------------ Summary: WildFly Multi JSF Feature do not support myfaces 1.2 Key: WFLY-3804 URL: https://issues.jboss.org/browse/WFLY-3804 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Class Loading, JSF Affects Versions: 8.1.0.Final Environment: Windows 7 64, Java 8 64 (jdk1.8_11) Myfaces Slot 1.2.12 Reporter: roman jablonka Assignee: David Lloyd -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-298) NPE on addFilter in WsServerContainer

by Remy Maucherat (JIRA)

[ https://issues.jboss.org/browse/JBWEB-298?page=com.atlassian.jira.plugin.... ] Remy Maucherat resolved JBWEB-298. ---------------------------------- Fix Version/s: JBossWeb-7.5.0.GA Resolution: Done r2499 in web. > NPE on addFilter in WsServerContainer > ------------------------------------- > > Key: JBWEB-298 > URL: https://issues.jboss.org/browse/JBWEB-298 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat > Reporter: Bartosz Baranowski > Assignee: Remy Maucherat > Priority: Minor > Fix For: JBossWeb-7.5.0.GA > > Attachments: jboss-websocket-hello.war > > > I'm not sure if this is just faulty test/edge case/WFLY/EAP integration failure, but there is case when org.apache.tomcat.websocket.server.WsSci is scheduled and triggered twice. This makes WsServerContainer throw NPE, since servletContext.addFilter[1] return null if filter with specified name exist. > Regardless this case being a valid one or not, WsServerContainer should handle this either with proper message or different exception than NPE. > I'm assigning this to myself for time being( until I can establish if WFLY/EAP being at fault and procure testcase ) > [1] https://source.jboss.org/browse/JBossWeb/branches/7.4.x/src/main/java/org... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2014