February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-52) Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-52?page=com.atlassian.jira.plugin.... ] Geoffrey De Smet commented on DROOLS-52: ---------------------------------------- Problem is that felix's <Export-Package> also exports packages from dependencies, which bloats our jars. > Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class > ---------------------------------------------------------------------- > > Key: DROOLS-52 > URL: https://issues.jboss.org/browse/DROOLS-52 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > Priority: Blocker > > Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class. > It looks like drools-compiler is fat jar. Fat jars (even shaded fat jars) are evil. See slide 39-42: > http://ge0ffrey.github.com/maven-dependency-puzzlers/maven-dependency-puz... > Certain platforms (android, ...) don't even allow to deploy such jars. Others (osgi, ...) throw warnings. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6625) Cachable Model Descriptions: Retrieve DMR model descriptions through HTTP GET

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6625?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6625: ----------------------------- Summary: Cachable Model Descriptions: Retrieve DMR model descriptions through HTTP GET (was: Cacheble Model Descriptions: Retrieve DMR model descriptions through HTTP GET) > Cachable Model Descriptions: Retrieve DMR model descriptions through HTTP GET > ----------------------------------------------------------------------------- > > Key: AS7-6625 > URL: https://issues.jboss.org/browse/AS7-6625 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > Currently we only support the content type "application/json" for GET responses to the management layer. If we could enable :read-resource-description responses of type "application/dmr" in return of GET requests, then HTTP clients could easily cache that information. Ideally this would be paired with an etag cache header. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6625) Cacheble Model Descriptions: Retrieve DMR model descriptions through HTTP GET

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6625?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6625: ----------------------------- Description: Currently we only support the content type "application/json" for GET responses to the management layer. If we could enable :read-resource-description responses of type "application/dmr" in return of GET requests, then clients could easily cache that information. Ideally this would be paired with an etag cache header. (was: Currently we only support the content type "application/json" for GET responses to the management layer. If we could enable :read-resource-description responses of type "application/dmr" in return of GWT requests, then clients could easily cache that information. Ideally this would be paired with an etag cache header. ) > Cacheble Model Descriptions: Retrieve DMR model descriptions through HTTP GET > ----------------------------------------------------------------------------- > > Key: AS7-6625 > URL: https://issues.jboss.org/browse/AS7-6625 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > Currently we only support the content type "application/json" for GET responses to the management layer. If we could enable :read-resource-description responses of type "application/dmr" in return of GET requests, then clients could easily cache that information. Ideally this would be paired with an etag cache header. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6625) Cacheble Model Descriptions: Retrieve DMR model descriptions through HTTP GET

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6625?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6625: ----------------------------- Description: Currently we only support the content type "application/json" for GET responses to the management layer. If we could enable :read-resource-description responses of type "application/dmr" in return of GET requests, then HTTP clients could easily cache that information. Ideally this would be paired with an etag cache header. (was: Currently we only support the content type "application/json" for GET responses to the management layer. If we could enable :read-resource-description responses of type "application/dmr" in return of GET requests, then clients could easily cache that information. Ideally this would be paired with an etag cache header. ) > Cacheble Model Descriptions: Retrieve DMR model descriptions through HTTP GET > ----------------------------------------------------------------------------- > > Key: AS7-6625 > URL: https://issues.jboss.org/browse/AS7-6625 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > Currently we only support the content type "application/json" for GET responses to the management layer. If we could enable :read-resource-description responses of type "application/dmr" in return of GET requests, then HTTP clients could easily cache that information. Ideally this would be paired with an etag cache header. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6625) Cacheble Model Descriptions: Retrieve DMR model descriptions through HTTP GET

by Heiko Braun (JIRA)

Heiko Braun created AS7-6625: -------------------------------- Summary: Cacheble Model Descriptions: Retrieve DMR model descriptions through HTTP GET Key: AS7-6625 URL: https://issues.jboss.org/browse/AS7-6625 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.3.0.Alpha1 Currently we only support the content type "application/json" for GET responses to the management layer. If we could enable :read-resource-description responses of type "application/dmr" in return of GWT requests, then clients could easily cache that information. Ideally this would be paired with an etag cache header. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6624) Jboss connection pool is not auto reconnects to mySQl (XA-datasource)

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6624?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-6624: ----------------------------------- https://community.jboss.org/en/jbossas7 is a better place to ask for help when your not sure if there is a bug. If you are sure that you are experiencing a bug, try to [recreate with the latest AS version|https://community.jboss.org/thread/167590]. Also, when creating bugs, make sure that the "component(s)" match the bug description (JCA would of been better for this issue). > Jboss connection pool is not auto reconnects to mySQl (XA-datasource) > --------------------------------------------------------------------- > > Key: AS7-6624 > URL: https://issues.jboss.org/browse/AS7-6624 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 7.1.1.Final > Reporter: Alexey S. > Assignee: Scott Marlow > > I am using JPA Hibernate in Timer EJB. > After MySQL's restarted, JBOSS connection pool should be restarted also to renew the transaction, but it doesnt happened. > my datasource is > <xa-datasource jndi-name="java:jboss/datasources/db" pool-name="db" enabled="true" use-java-context="true"> > <xa-datasource-property name="ServerName"> > localhost > </xa-datasource-property> > <xa-datasource-property name="DatabaseName"> > db > </xa-datasource-property> > <xa-datasource-property name="User"> > root > </xa-datasource-property> > <xa-datasource-property name="Password"> > xxxxx > </xa-datasource-property> > <xa-datasource-property name="AutoReconnectForPools"> > true > </xa-datasource-property> > <xa-datasource-property name="FailOverReadOnly"> > false > </xa-datasource-property> > <xa-datasource-property name="MaxReconnects"> > 100 > </xa-datasource-property> > <xa-datasource-property name="ReconnectAtTxEnd"> > true > </xa-datasource-property> > <driver>com.mysql</driver> > <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> > <validation> > <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/> > <check-valid-connection-sql>select 1</check-valid-connection-sql> > <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/> > </validation> > </xa-datasource> -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6624) Jboss connection pool is not auto reconnects to mySQl (XA-datasource)

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6624?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated AS7-6624: ------------------------------ Assignee: Stefano Maestri (was: Scott Marlow) Component/s: JCA (was: JPA / Hibernate) > Jboss connection pool is not auto reconnects to mySQl (XA-datasource) > --------------------------------------------------------------------- > > Key: AS7-6624 > URL: https://issues.jboss.org/browse/AS7-6624 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: 7.1.1.Final > Reporter: Alexey S. > Assignee: Stefano Maestri > > I am using JPA Hibernate in Timer EJB. > After MySQL's restarted, JBOSS connection pool should be restarted also to renew the transaction, but it doesnt happened. > my datasource is > <xa-datasource jndi-name="java:jboss/datasources/db" pool-name="db" enabled="true" use-java-context="true"> > <xa-datasource-property name="ServerName"> > localhost > </xa-datasource-property> > <xa-datasource-property name="DatabaseName"> > db > </xa-datasource-property> > <xa-datasource-property name="User"> > root > </xa-datasource-property> > <xa-datasource-property name="Password"> > xxxxx > </xa-datasource-property> > <xa-datasource-property name="AutoReconnectForPools"> > true > </xa-datasource-property> > <xa-datasource-property name="FailOverReadOnly"> > false > </xa-datasource-property> > <xa-datasource-property name="MaxReconnects"> > 100 > </xa-datasource-property> > <xa-datasource-property name="ReconnectAtTxEnd"> > true > </xa-datasource-property> > <driver>com.mysql</driver> > <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> > <validation> > <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/> > <check-valid-connection-sql>select 1</check-valid-connection-sql> > <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/> > </validation> > </xa-datasource> -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6621) Work on CDI + Bean Validation integration for method validation

by Gunnar Morling (JIRA)

[ https://issues.jboss.org/browse/AS7-6621?page=com.atlassian.jira.plugin.s... ] Gunnar Morling commented on AS7-6621: ------------------------------------- The API for method validation is described in [section 5.1.2|http://beanvalidation.org/1.1/spec/#validationapi-validatorapi-meth...] of the BV 1.1 spec. [Section 5.4|http://beanvalidation.org/1.1/spec/#validationapi-triggeringmethodval...] describes the expected behavior of a technology integrating with method validation. [Section 10.1.2|file:///Users/gunnar/Development/workspaces/hibernate-validator/beanvalidation-spec/build/en/html_single/index.html#integration-general-executable] describes the interaction of {{@MethodValidated}} and the global configuration of validated methods/constructors in Bean Validations {{META-INF/validation.xml}} configuration file. > Work on CDI + Bean Validation integration for method validation > --------------------------------------------------------------- > > Key: AS7-6621 > URL: https://issues.jboss.org/browse/AS7-6621 > Project: Application Server 7 > Issue Type: Sub-task > Components: EE > Reporter: Emmanuel Bernard > Assignee: David Lloyd > Fix For: 8.0.0.Alpha1 > > > Bean Validation and CDI needs to integrate to validate method parameters and return values. This can be done via a portable extension but [~jason.greene] was mentioning doing something proprietary to speed up the bootstrap process. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-266) Cookie Processing of JSON Cookie destroys Cookie Header

by Manuel Coenen (JIRA)

[ https://issues.jboss.org/browse/JBWEB-266?page=com.atlassian.jira.plugin.... ] Manuel Coenen commented on JBWEB-266: ------------------------------------- As I stated earlier our server forwards all headers to another server when loading additional content. This forwarding includes the cookie headers. As it is now we need to examine the headers, filter the cookie header and re-add it to our own RequestWrapper's header map from the {{Cookie[]}} array available via the {{HttpRequest}} object. Addtionally we need to re-escape the contained double-quotes. All of this extra work could be avoided if inside the {{Cookies.unescapeDoubleQuotes(ByteChunk)}} method the {{byte[]}} containing the header is copied prior to modification. This way the cost is reduced to the case when the cookie header contains escaped double-quotes. > Cookie Processing of JSON Cookie destroys Cookie Header > ------------------------------------------------------- > > Key: JBWEB-266 > URL: https://issues.jboss.org/browse/JBWEB-266 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat > Affects Versions: JBossWeb-7.0.1.GA > Environment: Windows 7 x64 and RHEL/CentOS 5.x, Java 1.7.0_11, JBoss AS 7.0.2 Final > Reporter: Manuel Coenen > Assignee: Remy Maucherat > > When sending a cookie with JSON content to JBoss the automatic cookie processing (triggered by looking for a session cookie) modifies the {{byte[]}} buffer which is also used for the HTTP headers. > This is due to multiple objects depending on the same {{byte[]}} buffer instance. The following hierarchy should demonstrate this dependency: > {noformat} > Http11Processor.request (Request) > └> cookies (Cookies) > | └> scookies[] (ServerCookie) > | └> scookies[x] (where x is the index referencing the JSON cookie) > | └> value (MessageByte) > | └>byteC (ByteChunk) > | \ > | |-> buff (byte[]) > | / > | ┌> byteC (ByteChunk) > | ┌> valueB (MessageByte) > | ┌> headers[y] (where y is the index referencing the JSON cookie header) > | ┌> headers[] (MimeHeaderField) > └> headers (MimeHeader) > {noformat} > The method {{Cookies.unescapeDoubleQuotes(ByteChunk)}} modifies this buffer by overwriting its contents when removing the escaped double-quotes. This in return destroys the reference for the header as it will still maintain the {{start}} and {{end}} reference inside this buffer. If the value for this header is read later it will be the unescaped content trailed by the surplus escaped region (see reproduction instructions for a more detailed example). > In my opinion the method {{Cookies.unescapeDoubleQuotes(ByteChunk)}} should copy the {{byte[]}} first to avoid side effects to other parts referencing this {{byte[]}} as it could be (and is in our case) that the headers (including cookie) need to be forwarded unmodified to another server. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6590) JSR-349 Bean Validation 1.1 API support and integration

by Gunnar Morling (JIRA)

[ https://issues.jboss.org/browse/AS7-6590?page=com.atlassian.jira.plugin.s... ] Gunnar Morling commented on AS7-6590: ------------------------------------- The integration points are described in [section 10.3|http://beanvalidation.org/1.1/spec/#d0e11232] of the Bean Validation 1.1 spec. > JSR-349 Bean Validation 1.1 API support and integration > ------------------------------------------------------- > > Key: AS7-6590 > URL: https://issues.jboss.org/browse/AS7-6590 > Project: Application Server 7 > Issue Type: Sub-task > Components: EE > Reporter: David Lloyd > Assignee: Emmanuel Bernard > Fix For: 8.0.0.Alpha1 > > > Integrate Bean Validation 1.1 and Hibernate Validator 5 to support the BV 1.1 requirement of Java EE 7. -- 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

13 years, 2 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 February 2013