[JBoss JIRA] (JGRP-1820) XML schema broken for AUTH
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1820?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1820:
--------------------------------
Re: changing the schema, dude, it's April 2nd not 1 :-)
I'll investigate whether I can generate the schema...
> XML schema broken for AUTH
> --------------------------
>
> Key: JGRP-1820
> URL: https://issues.jboss.org/browse/JGRP-1820
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.1
> Reporter: Dennis Reed
> Assignee: Bela Ban
> Priority: Minor
>
> The XML schema does not pass validation for AUTH.
> AUTH merges in properties for the pluggable auth_class, which are not currently included in the schema.
> For example the fixed_members_value when using FixedMembershipToken is not included in the schema and fails validation:
> <AUTH auth_class="org.jgroups.auth.FixedMembershipToken"
> fixed_members_value="localhost/7900">
> </AUTH>
--
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
12 years, 3 months
[JBoss JIRA] (JGRP-1820) XML schema broken for AUTH
by Dennis Reed (JIRA)
[ https://issues.jboss.org/browse/JGRP-1820?page=com.atlassian.jira.plugin.... ]
Dennis Reed commented on JGRP-1820:
-----------------------------------
Two possible fixes:
- Scan for all classes that extend AuthToken and include their properties in the schema.
- Change the config so it's more generic and can fit into a schema (wasn't that the reason for EAP's custom JGroups config format?)
(A similar issue also affects any custom protocols -- AUTH is just the only shipped protocol that doesn't match the schema)
> XML schema broken for AUTH
> --------------------------
>
> Key: JGRP-1820
> URL: https://issues.jboss.org/browse/JGRP-1820
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.1
> Reporter: Dennis Reed
> Assignee: Bela Ban
> Priority: Minor
>
> The XML schema does not pass validation for AUTH.
> AUTH merges in properties for the pluggable auth_class, which are not currently included in the schema.
> For example the fixed_members_value when using FixedMembershipToken is not included in the schema and fails validation:
> <AUTH auth_class="org.jgroups.auth.FixedMembershipToken"
> fixed_members_value="localhost/7900">
> </AUTH>
--
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
12 years, 3 months
[JBoss JIRA] (JGRP-1820) XML schema broken for AUTH
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1820?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1820:
--------------------------------
I don't know how this can be changed as the auth tokens are pluggable and thus added dynamically. I don't think we can generate a schema for the AUTH tokens...
> XML schema broken for AUTH
> --------------------------
>
> Key: JGRP-1820
> URL: https://issues.jboss.org/browse/JGRP-1820
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.1
> Reporter: Dennis Reed
> Assignee: Bela Ban
> Priority: Minor
>
> The XML schema does not pass validation for AUTH.
> AUTH merges in properties for the pluggable auth_class, which are not currently included in the schema.
> For example the fixed_members_value when using FixedMembershipToken is not included in the schema and fails validation:
> <AUTH auth_class="org.jgroups.auth.FixedMembershipToken"
> fixed_members_value="localhost/7900">
> </AUTH>
--
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
12 years, 3 months
[JBoss JIRA] (JGRP-1820) XML schema broken for AUTH
by Dennis Reed (JIRA)
Dennis Reed created JGRP-1820:
---------------------------------
Summary: XML schema broken for AUTH
Key: JGRP-1820
URL: https://issues.jboss.org/browse/JGRP-1820
Project: JGroups
Issue Type: Bug
Affects Versions: 3.4.1
Reporter: Dennis Reed
Assignee: Bela Ban
The XML schema does not pass validation for AUTH.
AUTH merges in properties for the pluggable auth_class, which are not currently included in the schema.
For example the fixed_members_value when using FixedMembershipToken is not included in the schema and fails validation:
<AUTH auth_class="org.jgroups.auth.FixedMembershipToken"
fixed_members_value="localhost/7900">
</AUTH>
--
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
12 years, 3 months
[JBoss JIRA] (JGRP-1820) XML schema broken for AUTH
by Dennis Reed (JIRA)
[ https://issues.jboss.org/browse/JGRP-1820?page=com.atlassian.jira.plugin.... ]
Dennis Reed updated JGRP-1820:
------------------------------
Priority: Minor (was: Major)
> XML schema broken for AUTH
> --------------------------
>
> Key: JGRP-1820
> URL: https://issues.jboss.org/browse/JGRP-1820
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.1
> Reporter: Dennis Reed
> Assignee: Bela Ban
> Priority: Minor
>
> The XML schema does not pass validation for AUTH.
> AUTH merges in properties for the pluggable auth_class, which are not currently included in the schema.
> For example the fixed_members_value when using FixedMembershipToken is not included in the schema and fails validation:
> <AUTH auth_class="org.jgroups.auth.FixedMembershipToken"
> fixed_members_value="localhost/7900">
> </AUTH>
--
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
12 years, 3 months
[JBoss JIRA] (WFLY-3203) Inconsistent handling of @Resource for URL in EJB vs JSF managed bean
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-3203?page=com.atlassian.jira.plugin.... ]
David Lloyd updated WFLY-3203:
------------------------------
Description:
Given a set of simple jndi bindings like the following:
{code:xml}
<subsystem xmlns="urn:jboss:domain:naming:2.0">
<bindings>
<simple name="java:global/NSPDomain" value="domain" type="java.lang.String"/>
<simple name="java:global/NSPURL" value="http://red-hat-summit.cloudapp.net:8081/" type="java.net.URL"/>
<simple name="java:global/NotificationCallbackURL" value="http://dmz.starkinternational.com:8080/iotbof-web/rest/events/send" type="java.net.URL"/>
</bindings>
<remote-naming/>
</subsystem>
{code}
The following works from an EJB:
{code}
import javax.ejb.Singleton;
import javax.ejb.Startup;
@Singleton
@Startup
public class NSPConnector {
...
@Resource(name = "java:global/NotificationCallbackURL")
private URL notificationURL;
{code}
but fails with a NameNotFoundException when used from within a JSF managed bean.
{code}
import javax.enterprise.context.ApplicationScoped;
import javax.inject.Named;
@Named("nspmodel")
@ApplicationScoped
public class NSPModel {
private static Logger logger = Logger.getLogger(NSPModel.class);
@Resource(name = "java:global/NotificationCallbackURL")
private URL notificationURL;
{code}
Has the following error when accessed:
{noformat}
Caused by: javax.naming.NameNotFoundException: env/java:global/NotificationCallbackURL -- service jboss.naming.context.java.module.iot-ear.iotbof-web.env.java:global.NotificationCallbackURL
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0]
at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0]
at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:185) [wildfly-weld-8.0.0.Final.jar:8.0.0.Final]
... 71 more
{noformat}
was:
Given a set of simple jndi bindings like the following:
<subsystem xmlns="urn:jboss:domain:naming:2.0">
<bindings>
<simple name="java:global/NSPDomain" value="domain" type="java.lang.String"/>
<simple name="java:global/NSPURL" value="http://red-hat-summit.cloudapp.net:8081/" type="java.net.URL"/>
<simple name="java:global/NotificationCallbackURL" value="http://dmz.starkinternational.com:8080/iotbof-web/rest/events/send" type="java.net.URL"/>
</bindings>
<remote-naming/>
</subsystem>
The following works from an EJB:
import javax.ejb.Singleton;
import javax.ejb.Startup;
@Singleton
@Startup
public class NSPConnector {
...
@Resource(name = "java:global/NotificationCallbackURL")
private URL notificationURL;
but fails with a NameNotFoundException when used from within a JSF managed bean.
import javax.enterprise.context.ApplicationScoped;
import javax.inject.Named;
@Named("nspmodel")
@ApplicationScoped
public class NSPModel {
private static Logger logger = Logger.getLogger(NSPModel.class);
@Resource(name = "java:global/NotificationCallbackURL")
private URL notificationURL;
Has the following error when accessed:
Caused by: javax.naming.NameNotFoundException: env/java:global/NotificationCallbackURL -- service jboss.naming.context.java.module.iot-ear.iotbof-web.env.java:global.NotificationCallbackURL
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0]
at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0]
at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:185) [wildfly-weld-8.0.0.Final.jar:8.0.0.Final]
... 71 more
Assignee: Stuart Douglas (was: David Lloyd)
Component/s: CDI / Weld
(was: EJB)
(was: JSF)
I think this is actually a Weld issue, judging from the stack trace.
> Inconsistent handling of @Resource for URL in EJB vs JSF managed bean
> ---------------------------------------------------------------------
>
> Key: WFLY-3203
> URL: https://issues.jboss.org/browse/WFLY-3203
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: CDI / Weld
> Affects Versions: 8.0.0.Final
> Environment: [standalone 526]$ /Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/bin/java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build 1.8.0-b132)
> Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
> Reporter: Scott Stark
> Assignee: Stuart Douglas
>
> Given a set of simple jndi bindings like the following:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:naming:2.0">
> <bindings>
> <simple name="java:global/NSPDomain" value="domain" type="java.lang.String"/>
> <simple name="java:global/NSPURL" value="http://red-hat-summit.cloudapp.net:8081/" type="java.net.URL"/>
> <simple name="java:global/NotificationCallbackURL" value="http://dmz.starkinternational.com:8080/iotbof-web/rest/events/send" type="java.net.URL"/>
> </bindings>
> <remote-naming/>
> </subsystem>
> {code}
> The following works from an EJB:
> {code}
> import javax.ejb.Singleton;
> import javax.ejb.Startup;
> @Singleton
> @Startup
> public class NSPConnector {
> ...
> @Resource(name = "java:global/NotificationCallbackURL")
> private URL notificationURL;
> {code}
> but fails with a NameNotFoundException when used from within a JSF managed bean.
> {code}
> import javax.enterprise.context.ApplicationScoped;
> import javax.inject.Named;
> @Named("nspmodel")
> @ApplicationScoped
> public class NSPModel {
> private static Logger logger = Logger.getLogger(NSPModel.class);
> @Resource(name = "java:global/NotificationCallbackURL")
> private URL notificationURL;
> {code}
> Has the following error when accessed:
> {noformat}
> Caused by: javax.naming.NameNotFoundException: env/java:global/NotificationCallbackURL -- service jboss.naming.context.java.module.iot-ear.iotbof-web.env.java:global.NotificationCallbackURL
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
> at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0]
> at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0]
> at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:185) [wildfly-weld-8.0.0.Final.jar:8.0.0.Final]
> ... 71 more
> {noformat}
--
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
12 years, 3 months
[JBoss JIRA] (WFLY-3203) Inconsistent handling of @Resource for URL in EJB vs JSF managed bean
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-3203?page=com.atlassian.jira.plugin.... ]
David Lloyd updated WFLY-3203:
------------------------------
Issue Type: Bug (was: Feature Request)
> Inconsistent handling of @Resource for URL in EJB vs JSF managed bean
> ---------------------------------------------------------------------
>
> Key: WFLY-3203
> URL: https://issues.jboss.org/browse/WFLY-3203
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CDI / Weld
> Affects Versions: 8.0.0.Final
> Environment: [standalone 526]$ /Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/bin/java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build 1.8.0-b132)
> Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
> Reporter: Scott Stark
> Assignee: Stuart Douglas
>
> Given a set of simple jndi bindings like the following:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:naming:2.0">
> <bindings>
> <simple name="java:global/NSPDomain" value="domain" type="java.lang.String"/>
> <simple name="java:global/NSPURL" value="http://red-hat-summit.cloudapp.net:8081/" type="java.net.URL"/>
> <simple name="java:global/NotificationCallbackURL" value="http://dmz.starkinternational.com:8080/iotbof-web/rest/events/send" type="java.net.URL"/>
> </bindings>
> <remote-naming/>
> </subsystem>
> {code}
> The following works from an EJB:
> {code}
> import javax.ejb.Singleton;
> import javax.ejb.Startup;
> @Singleton
> @Startup
> public class NSPConnector {
> ...
> @Resource(name = "java:global/NotificationCallbackURL")
> private URL notificationURL;
> {code}
> but fails with a NameNotFoundException when used from within a JSF managed bean.
> {code}
> import javax.enterprise.context.ApplicationScoped;
> import javax.inject.Named;
> @Named("nspmodel")
> @ApplicationScoped
> public class NSPModel {
> private static Logger logger = Logger.getLogger(NSPModel.class);
> @Resource(name = "java:global/NotificationCallbackURL")
> private URL notificationURL;
> {code}
> Has the following error when accessed:
> {noformat}
> Caused by: javax.naming.NameNotFoundException: env/java:global/NotificationCallbackURL -- service jboss.naming.context.java.module.iot-ear.iotbof-web.env.java:global.NotificationCallbackURL
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) [wildfly-naming-8.0.0.Final.jar:8.0.0.Final]
> at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0]
> at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0]
> at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:185) [wildfly-weld-8.0.0.Final.jar:8.0.0.Final]
> ... 71 more
> {noformat}
--
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
12 years, 3 months