[JBoss JIRA] (WFLY-8049) Update Artemis SQL statements
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-8049?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-8049:
-------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha1)
> Update Artemis SQL statements
> ------------------------------
>
> Key: WFLY-8049
> URL: https://issues.jboss.org/browse/WFLY-8049
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 11.0.0.Beta1
>
>
> After ARTEMIS-938, SQL statements for Artemis JDBC store uses BIGINT for ids instead of INT.
> The SQL statement used by WildFly (in modules/system/layers/base/org/wildfly/extension/messaging-activemq/main/database/journal-sql.properties) must be updated to also use BIGINT
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-7986) Add some exclusions to the 'org.wildfly.extension.elytron' module.
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-7986?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-7986:
-------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha1)
> Add some exclusions to the 'org.wildfly.extension.elytron' module.
> ------------------------------------------------------------------
>
> Key: WFLY-7986
> URL: https://issues.jboss.org/browse/WFLY-7986
> Project: WildFly
> Issue Type: Task
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 11.0.0.Beta1
>
>
> Likely to be something like: -
> bq. <exports>
> bq. <exclude path="org/wildfly/extension/elytron/ElytronExtension"/>
> bq. <exclude path="org/wildfly/extension/elytron/_private"/>
> bq. <exclude path="org/wildfly/extension/elytron/capabilities"/>
> bq. </exports>
> Although capabilities also needs to be double checked, this may be moved and hidden using standard Java visibility modifiers.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-7816) Camel CXF version not compatible with WildFly CXF
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-7816?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-7816:
-------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha1)
> Camel CXF version not compatible with WildFly CXF
> -------------------------------------------------
>
> Key: WFLY-7816
> URL: https://issues.jboss.org/browse/WFLY-7816
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Web Services
> Affects Versions: 10.1.0.Final
> Reporter: Thomas Diesler
> Assignee: Alessio Soldano
> Fix For: 10.2.0.Final, 11.0.0.Beta1
>
>
> cxf-3.1.9 distributed with camel-2.19.x is not compatible with cxf-3.1.6 from wildfly-10.1.0.Final
> {code}
> Caused by: java.lang.NoSuchMethodError: org.apache.cxf.message.Message.remove(Ljava/lang/Class;)Ljava/lang/Object;
> at org.apache.camel.component.cxf.CxfEndpoint$CamelCxfClientImpl.setParameters(CxfEndpoint.java:1239)
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:470)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:416)
> at org.apache.camel.component.cxf.CxfProducer.process(CxfProducer.java:133)
> {code}
> CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/1546
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-7664) Missing default values in ldap-key-store description in management model.
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-7664?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-7664:
-------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha1)
> Missing default values in ldap-key-store description in management model.
> -------------------------------------------------------------------------
>
> Key: WFLY-7664
> URL: https://issues.jboss.org/browse/WFLY-7664
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Labels: user_experience
> Fix For: 11.0.0.Beta1
>
>
> Some attributes of Elytron {{ldap-key-store}} resource have defined some default value, but description of these attributes in CLI is missing default values. According to XSD following attributes of {{ldap-key-store}} have assigned some default value:
> * {{search-recursive}} has default value {{true}}
> * {{search-time-limit}} has default value {{10000}}
> * {{filter-alias}} has default value {{(alias-attribute=\{0\})}}
> * {{filter-certificate}} has default value {{(certificate-attribute=\{0\})}}
> * {{filter-iterate}} has default value {{(alias-attribute=*)}}
> * {{alias-attribute}} has default value {{cn}}
> * {{certificate-attribute}} has default value {{usercertificate}}
> * {{certificate-type}} has default value {{X.509}}
> * {{certificate-chain-attribute}} has default value {{userSMIMECertificate}}
> * {{certificate-chain-encoding}} has default value {{PKCS7}}
> * {{key-attribute}} has default value {{userPKCS12}}
> * {{key-type}} has default value {{PKCS12}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-7639) Missing XSD for wildfly-config.xml
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-7639?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-7639:
-------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha1)
> Missing XSD for wildfly-config.xml
> ----------------------------------
>
> Key: WFLY-7639
> URL: https://issues.jboss.org/browse/WFLY-7639
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Josef Cacek
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 11.0.0.Beta1
>
>
> There is a new client configuration required in `wildfly-config.xml` (more in JBEAP-7104), but the `docs/schema` folder doesn't contain its XSD (schema definition).
> We have to provide one with a sufficient description of the elements and attributes.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8449) EJB contextData not sent back to client in response
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-8449?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-8449:
-------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha1)
> EJB contextData not sent back to client in response
> ---------------------------------------------------
>
> Key: WFLY-8449
> URL: https://issues.jboss.org/browse/WFLY-8449
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Fedor Gavrilov
> Assignee: Fedor Gavrilov
> Labels: ejb
> Fix For: 11.0.0.Beta1
>
>
> With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors.
> Since AS7 and WildFly the only possibility is to pass such context from the client to the server.
> It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations.
> This was used to return i.e. tracking or additional usefull informations.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month