[JBoss JIRA] (ARQ-74) Base test deployment on project in which test is run
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/ARQ-74?page=com.atlassian.jira.plugin.sys... ]
Matous Jobanek commented on ARQ-74:
-----------------------------------
This issue can be solved by using EmbeddedMaven feature implemented in ShrinkWrap Resolver: https://github.com/shrinkwrap/resolver#embedded-maven
The resulting deployment method would look like this:
{code:java}
@Deployment
public static Archive deploy(){
return EmbeddedMaven.forProject("pom.xml").setGoals("package").build().getDefaultBuiltArchive();
}
{code}
> Base test deployment on project in which test is run
> ----------------------------------------------------
>
> Key: ARQ-74
> URL: https://issues.jboss.org/browse/ARQ-74
> Project: Arquillian
> Issue Type: Feature Request
> Components: Packaging Enricher SPI
> Reporter: Pete Muir
> Fix For: 2.0.0.Beta1
>
>
> A common testing scenario will be to deploy the artifact generated by the current project, and run tests against it.
> For example, say my project was building a war, I want to be able to deploy that war, inserting the test case and any beans into the deployment, and have my tests run.
> In this case the deep control of the classpath through shrinkwrap is getting in the way.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (ARQ-2036) Migrating to wildfly10, I get an error with the jboss logging
by Manuel Aznar Pérez (JIRA)
[ https://issues.jboss.org/browse/ARQ-2036?page=com.atlassian.jira.plugin.s... ]
Manuel Aznar Pérez commented on ARQ-2036:
-----------------------------------------
I resolve excluding jboss-logging, at hibernate for example:
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-entitymanager</artifactId>
<version>4.3.1.Final</version>
<scope>provided</scope>
<exclusions>
<exclusion>
<groupId>org.jboss.logging</groupId>
<artifactId>jboss-logging</artifactId>
</exclusion>
</exclusions>
</dependency>
> Migrating to wildfly10, I get an error with the jboss logging
> -------------------------------------------------------------
>
> Key: ARQ-2036
> URL: https://issues.jboss.org/browse/ARQ-2036
> Project: Arquillian
> Issue Type: Bug
> Environment: WildFly10 mode managed in arquillian:
> org.wildfly.arquillian:wildfly-arquillian-parent:2.0.0.Final
> org.jboss.arquillian:arquillian-build:1.1.11.Final (modelversion: 4.0.0)
> Reporter: lamiae obila
> Priority: Blocker
>
> I was migrating my application from Jboss AS7 to Wildfly10 using arquillian for tests.
> But, I get this error :
> {code:java}
> Exception in thread "Remoting "endpoint" task-4" java.lang.NoSuchMethodError: org.jboss.logging.Logger.tracef(Ljava/lang/String;I)V
> at org.jboss.remotingjmx.VersionedConectionFactory$ClientVersionReceiver.handleMessage(VersionedConectionFactory.java:158)
> at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:456)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> I use the wildfly-arquillian-container-managed: version 2.0.0.Final for my test arquillian.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (ARQGRA-496) JavaScript interface returns null instead of false for Booleans
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-496?page=com.atlassian.jira.plugin... ]
Vsevolod Golovanov updated ARQGRA-496:
--------------------------------------
Description:
{code}
@JavaScript(value = "MyObject")
public interface MyJsInterface {
Boolean getSomeValue();
}
{code}
If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states with Boolean. I want an exception for null with boolean.
{code:title=call.js/invokeInterface}
if (property && target[property]) {
return target[property];
}
{code}
There are 2 problems here.
# Instead of {{target\[property\]}} there should be an explicit {{typeof(target\[property\]}) !== 'undefined')}} check (or {{property in target}}, if you want to distinguish the "property is defined, but its value is undefined" case).
# When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
The problem probably affects not only Booleans, but other types with falsey values too.
was:
{code}
@JavaScript(value = "MyObject")
public interface MyJsInterface {
Boolean getSomeValue();
}
{code}
If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states with Boolean. I want an exception for null with boolean.
{code:title=call.js/invokeInterface}
if (property && target[property]) {
return target[property];
}
{code}
There are 2 problems here.
# Instead of {{target\[property\]}} there should be an explicit {{typeof(target\[property\]}) !== 'undefined')}} check (or {{property in target}}, if you want to distinguish the "property is defined, but its value is undefined" case).
# When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
The problem probably affects not only Booleans, but other types with falsey values.
> JavaScript interface returns null instead of false for Booleans
> ---------------------------------------------------------------
>
> Key: ARQGRA-496
> URL: https://issues.jboss.org/browse/ARQGRA-496
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.1.0.Final
> Reporter: Vsevolod Golovanov
>
> {code}
> @JavaScript(value = "MyObject")
> public interface MyJsInterface {
> Boolean getSomeValue();
> }
> {code}
> If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
> If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states with Boolean. I want an exception for null with boolean.
> {code:title=call.js/invokeInterface}
> if (property && target[property]) {
> return target[property];
> }
> {code}
> There are 2 problems here.
> # Instead of {{target\[property\]}} there should be an explicit {{typeof(target\[property\]}) !== 'undefined')}} check (or {{property in target}}, if you want to distinguish the "property is defined, but its value is undefined" case).
> # When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
> The problem probably affects not only Booleans, but other types with falsey values too.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (ARQGRA-496) JavaScript interface returns null instead of false for Booleans
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-496?page=com.atlassian.jira.plugin... ]
Vsevolod Golovanov updated ARQGRA-496:
--------------------------------------
Description:
{code}
@JavaScript(value = "MyObject")
public interface MyJsInterface {
Boolean getSomeValue();
}
{code}
If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states with Boolean. I want an exception for null with boolean.
{code:title=call.js/invokeInterface}
if (property && target[property]) {
return target[property];
}
{code}
There are 2 problems here.
# Instead of {{target\[property\]}} there should be an explicit {{typeof(target\[property\]}) !== 'undefined')}} check (or {{property in target}}, if you want to distinguish the "property is defined, but its value is undefined" case).
# When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
The problem probably affects not only Booleans, but other types with falsey values.
was:
{code}
@JavaScript(value = "MyObject")
public interface MyJsInterface {
Boolean getSomeValue();
}
{code}
If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states with Boolean. I want an exception for null with boolean.
{code:title=call.js/invokeInterface}
if (property && target[property]) {
return target[property];
}
{code}
There are 2 problems here.
# Instead of {{target\[property\]}} there should be an explicit {{typeof(target\[property\]}) !== 'undefined')}} check (or {{property in target}}, if you want to distinguish the "property is defined, but its value is undefined" case).
# When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
> JavaScript interface returns null instead of false for Booleans
> ---------------------------------------------------------------
>
> Key: ARQGRA-496
> URL: https://issues.jboss.org/browse/ARQGRA-496
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.1.0.Final
> Reporter: Vsevolod Golovanov
>
> {code}
> @JavaScript(value = "MyObject")
> public interface MyJsInterface {
> Boolean getSomeValue();
> }
> {code}
> If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
> If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states with Boolean. I want an exception for null with boolean.
> {code:title=call.js/invokeInterface}
> if (property && target[property]) {
> return target[property];
> }
> {code}
> There are 2 problems here.
> # Instead of {{target\[property\]}} there should be an explicit {{typeof(target\[property\]}) !== 'undefined')}} check (or {{property in target}}, if you want to distinguish the "property is defined, but its value is undefined" case).
> # When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
> The problem probably affects not only Booleans, but other types with falsey values.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (ARQGRA-496) JavaScript interface returns null instead of false for Booleans
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-496?page=com.atlassian.jira.plugin... ]
Vsevolod Golovanov updated ARQGRA-496:
--------------------------------------
Description:
{code}
@JavaScript(value = "MyObject")
public interface MyJsInterface {
Boolean getSomeValue();
}
{code}
If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states with Boolean. I want an exception for null with boolean.
{code:title=call.js/invokeInterface}
if (property && target[property]) {
return target[property];
}
{code}
There are 2 problems here.
# Instead of {{target\[property\]}} there should be an explicit {{typeof(target\[property\]}) !== 'undefined')}} check (or {{property in target}}, if you want to distinguish the "property is defined, but its value is undefined" case).
# When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
was:
{code}
@JavaScript(value = "MyObject")
public interface MyJsInterface {
Boolean getSomeValue();
}
{code}
If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states with Boolean. I want an exception for null with boolean.
{code:title=call.js/invokeInterface}
if (property && target[property]) {
return target[property];
}
{code}
There are 2 problems here.
# Instead of {{target\[property\]}} there should be an explicit {{typeof !== 'undefined') check.
# When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
> JavaScript interface returns null instead of false for Booleans
> ---------------------------------------------------------------
>
> Key: ARQGRA-496
> URL: https://issues.jboss.org/browse/ARQGRA-496
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.1.0.Final
> Reporter: Vsevolod Golovanov
>
> {code}
> @JavaScript(value = "MyObject")
> public interface MyJsInterface {
> Boolean getSomeValue();
> }
> {code}
> If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
> If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states with Boolean. I want an exception for null with boolean.
> {code:title=call.js/invokeInterface}
> if (property && target[property]) {
> return target[property];
> }
> {code}
> There are 2 problems here.
> # Instead of {{target\[property\]}} there should be an explicit {{typeof(target\[property\]}) !== 'undefined')}} check (or {{property in target}}, if you want to distinguish the "property is defined, but its value is undefined" case).
> # When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (ARQGRA-496) JavaScript interface returns null instead of false for Booleans
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-496?page=com.atlassian.jira.plugin... ]
Vsevolod Golovanov commented on ARQGRA-496:
-------------------------------------------
Curiously the setter case has the 'undefined' check.
> JavaScript interface returns null instead of false for Booleans
> ---------------------------------------------------------------
>
> Key: ARQGRA-496
> URL: https://issues.jboss.org/browse/ARQGRA-496
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.1.0.Final
> Reporter: Vsevolod Golovanov
>
> {code}
> @JavaScript(value = "MyObject")
> public interface MyJsInterface {
> Boolean getSomeValue();
> }
> {code}
> If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
> If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states with Boolean. I want an exception for null with boolean.
> {code:title=call.js/invokeInterface}
> if (property && target[property]) {
> return target[property];
> }
> {code}
> There are 2 problems here.
> # Instead of {{target\[property\]}} there should be an explicit {{typeof !== 'undefined') check.
> # When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (ARQGRA-496) JavaScript interface returns null instead of false for Booleans
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-496?page=com.atlassian.jira.plugin... ]
Vsevolod Golovanov updated ARQGRA-496:
--------------------------------------
Description:
{code}
@JavaScript(value = "MyObject")
public interface MyJsInterface {
Boolean getSomeValue();
}
{code}
If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states with Boolean. I want an exception for null with boolean.
{code:title=call.js/invokeInterface}
if (property && target[property]) {
return target[property];
}
{code}
There are 2 problems here.
# Instead of {{target\[property\]}} there should be an explicit {{typeof !== 'undefined') check.
# When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
was:
{code}
@JavaScript(value = "MyObject")
public interface MyJsInterface {
Boolean getSomeValue();
}
{code}
If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states.
{code:title=call.js/invokeInterface}
if (property && target[property]) {
return target[property];
}
{code}
There are 2 problems here.
# Instead of {{target\[property\]}} there should be an explicit {{typeof !== 'undefined') check.
# When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
> JavaScript interface returns null instead of false for Booleans
> ---------------------------------------------------------------
>
> Key: ARQGRA-496
> URL: https://issues.jboss.org/browse/ARQGRA-496
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.1.0.Final
> Reporter: Vsevolod Golovanov
>
> {code}
> @JavaScript(value = "MyObject")
> public interface MyJsInterface {
> Boolean getSomeValue();
> }
> {code}
> If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
> If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states with Boolean. I want an exception for null with boolean.
> {code:title=call.js/invokeInterface}
> if (property && target[property]) {
> return target[property];
> }
> {code}
> There are 2 problems here.
> # Instead of {{target\[property\]}} there should be an explicit {{typeof !== 'undefined') check.
> # When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (ARQGRA-496) JavaScript interface returns null instead of false for Booleans
by Vsevolod Golovanov (JIRA)
Vsevolod Golovanov created ARQGRA-496:
-----------------------------------------
Summary: JavaScript interface returns null instead of false for Booleans
Key: ARQGRA-496
URL: https://issues.jboss.org/browse/ARQGRA-496
Project: Arquillian Graphene
Issue Type: Bug
Affects Versions: 2.1.0.Final
Reporter: Vsevolod Golovanov
{code}
@JavaScript(value = "MyObject")
public interface MyJsInterface {
Boolean getSomeValue();
}
{code}
If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states.
{code:title=call.js/invokeInterface}
if (property && target[property]) {
return target[property];
}
{code}
There are 2 problems here.
# Instead of {{target\[property\]}} there should be an explicit {{typeof !== 'undefined') check.
# When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months