October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBVFS-199) RealFileSystem:exists is not case sensitive in windows leading to a compilation failure with undertow and jbossweb

by Enrique González Martínez (JIRA)

Enrique González Martínez created JBVFS-199: ----------------------------------------------- Summary: RealFileSystem:exists is not case sensitive in windows leading to a compilation failure with undertow and jbossweb Key: JBVFS-199 URL: https://issues.jboss.org/browse/JBVFS-199 Project: JBoss VFS Issue Type: Bug Affects Versions: 3.2.5.Final, 3.5.0.Alpha1 Environment: Windows 64 bits JDK 1.7.0_71 Reporter: Enrique González Martínez Assignee: Enrique González Martínez In Wildfly, during jsp compilation the lookup function uses the Classloader::getResourceAsStream that relies on VFSResourceLoader for opening an InputStream. This function is working differently due to windows file system (not case sensitive). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3159) upgrade Generic JMS RA to 1.0.3.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3159?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3159: ----------------------------------------------- Ondrej Chaloupka <ochaloup(a)redhat.com> changed the Status of [bug 1033008|https://bugzilla.redhat.com/show_bug.cgi?id=1033008] from ASSIGNED to CLOSED > upgrade Generic JMS RA to 1.0.3.Final > ------------------------------------- > > Key: WFLY-3159 > URL: https://issues.jboss.org/browse/WFLY-3159 > Project: WildFly > Issue Type: Component Upgrade > Components: JCA, JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.1.0.CR1, 8.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4029) Upgrade Hibernate Validator to 5.1.3.Final

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/WFLY-4029?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik updated WFLY-4029: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/6881, https://github.com/wildfly/wildfly/pull/6882 (was: https://github.com/wildfly/wildfly/pull/6881) > Upgrade Hibernate Validator to 5.1.3.Final > ------------------------------------------ > > Key: WFLY-4029 > URL: https://issues.jboss.org/browse/WFLY-4029 > Project: WildFly > Issue Type: Task > Components: EE > Reporter: Hardy Ferentschik > Assignee: David Lloyd > Fix For: 8.2.0.CR1, 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4023) javax.el.ImportHandler#importClass & #importPackage doesn't import WEB-INF/classes

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-4023?page=com.atlassian.jira.plugin.... ] Farah Juma commented on WFLY-4023: ---------------------------------- Thanks for the app, Patrick! > javax.el.ImportHandler#importClass & #importPackage doesn't import WEB-INF/classes > ---------------------------------------------------------------------------------- > > Key: WFLY-4023 > URL: https://issues.jboss.org/browse/WFLY-4023 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 8.1.0.Final > Environment: Win7, Wildfly 8.1.0.Final > Reporter: Patrick Garner > Assignee: Farah Juma > Attachments: ImportHandlerDebug.zip > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > ImportHandler is not importing classes in WEB-INF/classes and, thus, developers are unable to import classes into the EL evaluation environment per EL 3.0 spec. section 1.22.2 "Imports of Packages, Classes, and Static Fields" > Here's the ImportHandler relevant code (https://github.com/jboss/jboss-el-api_spec/blob/master/src/main/java/java...) > {code:java} > private Class<?> getClassFor(String className) { > if (!notAClass.contains(className)) { > try { > return Class.forName(className, false, getClass().getClassLoader()); > } catch (ClassNotFoundException ex) { > notAClass.add(className); > } > } > return null; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4029) Upgrade Hibernate Validator to 5.1.3.Final

by Hardy Ferentschik (JIRA)

Hardy Ferentschik created WFLY-4029: --------------------------------------- Summary: Upgrade Hibernate Validator to 5.1.3.Final Key: WFLY-4029 URL: https://issues.jboss.org/browse/WFLY-4029 Project: WildFly Issue Type: Task Components: EE Reporter: Hardy Ferentschik Assignee: David Lloyd Fix For: 8.2.0.CR1, 9.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3776) ClassNotFound exception when running Arquillian test

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-3776?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos updated WFLY-3776: ------------------------------------------ Affects Version/s: 9.0.0.Alpha1 > ClassNotFound exception when running Arquillian test > ---------------------------------------------------- > > Key: WFLY-3776 > URL: https://issues.jboss.org/browse/WFLY-3776 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 8.1.0.Final, 9.0.0.Alpha1 > Environment: Mac > Reporter: xiaodong xie > Assignee: Panagiotis Sotiropoulos > > org.jboss.as.embedded.EmbeddedStandAloneServerFactory uses org.jboss.as.protocol.StreamUtils, which belongs to "org.jboss.as.protocol" module. This module is not imported in "org.jboss.as.embedded" module. > Adding the import fix the issue. > Thanks. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-644) no-loop attribute and named consequences

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-644?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-644: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > no-loop attribute and named consequences > ---------------------------------------- > > Key: DROOLS-644 > URL: https://issues.jboss.org/browse/DROOLS-644 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Reporter: Pedro Martins > Assignee: Mario Fusco > Labels: named_consequence, no-loop > > I wrote a rule that modifies a fact from within a named consequence. The no-loop attribute failed to prevent the rule from reactivating. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3776) ClassNotFound exception when running Arquillian test

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-3776?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos reassigned WFLY-3776: --------------------------------------------- Assignee: Panagiotis Sotiropoulos (was: Jason Greene) > ClassNotFound exception when running Arquillian test > ---------------------------------------------------- > > Key: WFLY-3776 > URL: https://issues.jboss.org/browse/WFLY-3776 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 8.1.0.Final > Environment: Mac > Reporter: xiaodong xie > Assignee: Panagiotis Sotiropoulos > > org.jboss.as.embedded.EmbeddedStandAloneServerFactory uses org.jboss.as.protocol.StreamUtils, which belongs to "org.jboss.as.protocol" module. This module is not imported in "org.jboss.as.embedded" module. > Adding the import fix the issue. > Thanks. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3799) Wrong WildFly version when WildFly standalone is started

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-3799?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos commented on WFLY-3799: ----------------------------------------------- INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha9) started in 1687ms - Started 199 of 361 services (192 services are lazy, passive or on-demand) Tested and version is ok. > Wrong WildFly version when WildFly standalone is started > -------------------------------------------------------- > > Key: WFLY-3799 > URL: https://issues.jboss.org/browse/WFLY-3799 > Project: WildFly > Issue Type: Bug > Components: Build System, Server > Affects Versions: 9.0.0.Alpha1 > Reporter: Juergen Zimmermann > Assignee: Panagiotis Sotiropoulos > Fix For: 9.0.0.Beta1 > > > I compiled the WildFly snapshot from GitHub. When I start WildFly standalone, then I see this final log message with the version number from WildFly Core: > {code} > INFO [org.jboss.as] WFLYSRV0025: WildFly 1.0.0.Alpha5 "Kenny" started in 2454ms - Started 216 of 319 services (143 services are lazy, passive or on-demand) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3830) Use external-context for remote TIBCO ems lookup

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-3830?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-3830: ----------------------------------- As explained in the PR, the TIBCO JNDI provider accepts only CompoundName in its lookup(Name) method. With the PR, it is possible to use the external-context with TIBCO EMS by using the StringOnlyInitialContext wrapper that convert the lookup(Name) call to the corresponding lookup(String) call. {noformat} <external-context name="java:global/tibco" module="com.tibco" class="org.jboss.as.naming.StringOnlyInitialContext"> <environment> <property name="java.naming.factory.initial" value="com.tibco.tibjms.naming.TibjmsInitialContextFactory"/> <property name="java.naming.provider.url" value="tcp:/<server>:<port>"/> <property name="java.naming.factory.url.pkgs" value="com.tibco.tibjms.naming"/> </environment> </external-context> {noformat} Note that the com.tibco module *must* have a dependency on the org.jboss.as.naming module to access this wrapper. > Use external-context for remote TIBCO ems lookup > ------------------------------------------------ > > Key: WFLY-3830 > URL: https://issues.jboss.org/browse/WFLY-3830 > Project: WildFly > Issue Type: Bug > Components: Naming > Affects Versions: 8.1.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > If an users uses the generic JMS RA with the TIBCO EMS messaging server, he has to duplicate all the JNDI parameters in the MDB annotations. > Instead, he should be able to use a naming's external-context to connect to the Remote TIBCO server with the following configuration: > {noformat} > <bindings> > <external-context name="java:global/tibco" module="com.tibco" class="javax.naming.InitialContext"> > <environment> > <property name="java.naming.factory.initial" value="com.tibco.tibjms.naming.TibjmsInitialContextFactory"/> > <property name="java.naming.provider.url" value="tcp://<tibco_server>:<tibco_port>"/> > <property name="java.naming.factory.url.pkgs" value="com.tibco.tibjms.naming"/> > </environment> > </external-context> > </bindings> > {noformat} > With these settings, the user only needs to pass the expected connection factory and destination lookup in the MDB: > {noformat} > @ActivationConfigProperty(propertyName = "connectionFactory", propertyValue = "java:global/tibco/XACF"), > @ActivationConfigProperty(propertyName = "destination", propertyValue = "java:global/tibco/Q1"), > {noformat} > The local JNDI lookup "java:global/tibco/Q1" will then use the external context (bound to "java:global/tibco") to lookup the "Q1" name on the TIBCO EMS. > There are a few bugs in the ExternalObjectFactory that prevents to use this configuration with a regular javax.naming.InitialContext to build the external context. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 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 October 2014