May 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-155) Javadoc for WebSocketContainer.connectToServer mentions ServerEndpoint instead of ClientEndpoint

by Ron Šmeral (JIRA)

Ron Šmeral created JBEE-155: ------------------------------- Summary: Javadoc for WebSocketContainer.connectToServer mentions ServerEndpoint instead of ClientEndpoint Key: JBEE-155 URL: https://issues.jboss.org/browse/JBEE-155 Project: JBoss JavaEE Spec APIs Issue Type: Bug Components: jboss-websocket-api Affects Versions: JavaEE 7 Spec APIs 1.0.0.Final Reporter: Ron Šmeral Assignee: Shelly McGowan In {{javax.websocket.WebSocketContainer}}, the javadoc for two connectToServer method signatures contains an incorrect statement: {{connectToServer(Object annotatedEndpointInstance, URI path)}} {{connectToServer(Class<?> annotatedEndpointClass, URI path)}} {quote} The supplied object must be a class decorated with the class level \{@link javax.websocket.server.*ServerEndpoint*\} annotation. {quote} which should point to {{javax.websocket.ClientEndpoint}} instead of the ServerEndpoint. Also, in case of {{connectToServer(Object annotatedEndpointInstance, URI path)}}, that sentence should read _...supplied object must be *an instance of* a class..._ -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3414) moduleAlias should be optional in jboss-deployment-structure.xml

by Harald Wellmann (JIRA)

Harald Wellmann created WFLY-3414: ------------------------------------- Summary: moduleAlias should be optional in jboss-deployment-structure.xml Key: WFLY-3414 URL: https://issues.jboss.org/browse/WFLY-3414 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 8.0.0.Final, 8.0.0.CR1 Reporter: Harald Wellmann Assignee: Jason Greene Very similar to WFLY-2851, there is still another issue where the schema {{jboss-deployment-structure-1_2.xsd}} expects a mandatory element {{moduleAlias}} in {{moduleType}}, which should be optional. A module definition without {{moduleAlias}} works fine at runtime, but the {{jboss-deployment-structure.xml}} does not validate against the schema. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3414) moduleAlias should be optional in jboss-deployment-structure.xml

by Harald Wellmann (JIRA)

[ https://issues.jboss.org/browse/WFLY-3414?page=com.atlassian.jira.plugin.... ] Harald Wellmann updated WFLY-3414: ---------------------------------- Affects Version/s: (was: 8.0.0.CR1) > moduleAlias should be optional in jboss-deployment-structure.xml > ---------------------------------------------------------------- > > Key: WFLY-3414 > URL: https://issues.jboss.org/browse/WFLY-3414 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Harald Wellmann > Assignee: Jason Greene > > Very similar to WFLY-2851, there is still another issue where the schema {{jboss-deployment-structure-1_2.xsd}} expects a mandatory element {{moduleAlias}} in {{moduleType}}, which should be optional. > A module definition without {{moduleAlias}} works fine at runtime, but the {{jboss-deployment-structure.xml}} does not validate against the schema. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3414) moduleAlias should be optional in jboss-deployment-structure.xml

by Harald Wellmann (JIRA)

[ https://issues.jboss.org/browse/WFLY-3414?page=com.atlassian.jira.plugin.... ] Harald Wellmann updated WFLY-3414: ---------------------------------- Issue Type: Bug (was: Feature Request) > moduleAlias should be optional in jboss-deployment-structure.xml > ---------------------------------------------------------------- > > Key: WFLY-3414 > URL: https://issues.jboss.org/browse/WFLY-3414 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Harald Wellmann > Assignee: Jason Greene > > Very similar to WFLY-2851, there is still another issue where the schema {{jboss-deployment-structure-1_2.xsd}} expects a mandatory element {{moduleAlias}} in {{moduleType}}, which should be optional. > A module definition without {{moduleAlias}} works fine at runtime, but the {{jboss-deployment-structure.xml}} does not validate against the schema. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3413) Expose support for runtime Resources

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3413?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-3413: ------------------------------ Fix Version/s: 9.0.0.Alpha1 > Expose support for runtime Resources > ------------------------------------ > > Key: WFLY-3413 > URL: https://issues.jboss.org/browse/WFLY-3413 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 9.0.0.Alpha1 > > > Currently we kinda have support for runtime resources but we dont expose this configuration to user so noone uses it. > see ConcreteResourceRegistration#register(final String elementValue, final ResourceDefinition provider, boolean runtimeOnly) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3413) Expose support for runtime Resources

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-3413: --------------------------------- Summary: Expose support for runtime Resources Key: WFLY-3413 URL: https://issues.jboss.org/browse/WFLY-3413 Project: WildFly Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Tomaz Cerar Assignee: Tomaz Cerar Currently we kinda have support for runtime resources but we dont expose this configuration to user so noone uses it. see ConcreteResourceRegistration#register(final String elementValue, final ResourceDefinition provider, boolean runtimeOnly) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3412) Sub ResourceDefinitions shouldn't need ResourceDescriptionResolver

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-3412: --------------------------------- Summary: Sub ResourceDefinitions shouldn't need ResourceDescriptionResolver Key: WFLY-3412 URL: https://issues.jboss.org/browse/WFLY-3412 Project: WildFly Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Domain Management Reporter: Tomaz Cerar Assignee: Tomaz Cerar Fix For: 9.0.0.Alpha1 We could omit forcing users to have resolver set for all subresources as in most cases it is the same and predictable. We could just reuse parent's resolver with some extra prefix. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3411) EJB/JPA error when call to persist

by Wilber Saca (JIRA)

[ https://issues.jboss.org/browse/WFLY-3411?page=com.atlassian.jira.plugin.... ] Wilber Saca commented on WFLY-3411: ----------------------------------- was not a question... Anyway thanks for ur interest... > EJB/JPA error when call to persist > ---------------------------------- > > Key: WFLY-3411 > URL: https://issues.jboss.org/browse/WFLY-3411 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.1.0.CR1, 8.1.0.CR2 > Environment: - WildFly 8.1.0.CR2 > - EclipseLink 2.5.1 (Added) > - JSF > - Netbeans 8 > Reporter: Wilber Saca > Assignee: David Lloyd > Labels: eclipselink, ejb, jpa, jsf > Fix For: 8.1.0.Final > > > I'm getting an exception when I try to persist an object for second time, after get an exception because of duplicate primary key. > I have tested the same application on GlassFish 4 with JSF(Mojarra) 2.2.6, EclipsLink 2.5.1 and this error is not fired, all works fine. > I also tried changing the default datasource setting in Wildfly. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3411) EJB/JPA error when call to persist

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3411?page=com.atlassian.jira.plugin.... ] David Lloyd resolved WFLY-3411. ------------------------------- Resolution: Rejected If you have user questions, ask them on the user forum, not the bug tracker. > EJB/JPA error when call to persist > ---------------------------------- > > Key: WFLY-3411 > URL: https://issues.jboss.org/browse/WFLY-3411 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.1.0.CR1, 8.1.0.CR2 > Environment: - WildFly 8.1.0.CR2 > - EclipseLink 2.5.1 (Added) > - JSF > - Netbeans 8 > Reporter: Wilber Saca > Assignee: David Lloyd > Labels: eclipselink, ejb, jpa, jsf > Fix For: 8.1.0.Final > > > I'm getting an exception when I try to persist an object for second time, after get an exception because of duplicate primary key. > I have tested the same application on GlassFish 4 with JSF(Mojarra) 2.2.6, EclipsLink 2.5.1 and this error is not fired, all works fine. > I also tried changing the default datasource setting in Wildfly. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1845) Null pointer exception in Samsung Q1 using 3G connection

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1845?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-1845 at 5/28/14 10:36 AM: ---------------------------------------------------------- OK, checking for null value in master, 3.3 and 3.4 was (Author: belaban): OK, checking for null value in master and 3.4 > Null pointer exception in Samsung Q1 using 3G connection > -------------------------------------------------------- > > Key: JGRP-1845 > URL: https://issues.jboss.org/browse/JGRP-1845 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.1, 3.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6, 3.2.7, 3.2.8, 3.2.9, 3.2.10, 3.2.12, 3.2.13, 3.3, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.3.5, 3.4, 3.4.1, 3.4.2, 3.4.3, 3.4.4 > Environment: Samsung Q1 with Windows XP Tablet Edition and 3G connection. Java 6 or Java 7. > Reporter: Denis Lamela > Assignee: Bela Ban > Priority: Minor > Fix For: 3.3.6, 3.4.5, 3.5 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Null pointer exception in method "bindToInterfaces" of class "org.jgroups.stack.DiagnosticsHandler". The exception is thrown while executing "i.getInterfaceAddresses().isEmpty()". "i.getInterfaceAddresses()" returns null. > This bug can be fixed checking if "i.getInterfaceAddresses()" returns null. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

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