From issues at jboss.org Thu Jun 14 03:26:00 2018 From: issues at jboss.org (Nicklas Karlsson (JIRA)) Date: Thu, 14 Jun 2018 03:26:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1800) SQL scripts are loaded with the default charset In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591269#comment-13591269 ] Nicklas Karlsson commented on ARQ-1800: --------------------------------------- Apparently the fix is still unreleased? Is there some workaround for this since I can't find *any* encoding that would work for my cleanup script. I have ??? in the tables and no matter if I use UTF-8, ISO-8859-1 etc the table names get garbled :-/ It's probably not the JDBC connection since DBUnit seeds the tables just fine, it's just the scripts (which I have to use since the DBUnit can never clean up stuff correctly due to foreign keys) > SQL scripts are loaded with the default charset > ----------------------------------------------- > > Key: ARQ-1800 > URL: https://issues.jboss.org/browse/ARQ-1800 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: jean-fran?ois Lefebvre > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > SQLSripts are loaded with the default plateform charset. > Could you please add a property like this : > > XXX > > to set the default scripts encoding. > see org.jboss.arquillian.persistence.script.ScriptLoader > reader = new BufferedReader(new InputStreamReader(inputStream)); -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Jun 29 10:48:00 2018 From: issues at jboss.org (kostd kostd (JIRA)) Date: Fri, 29 Jun 2018 10:48:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2185) non-managed deployment cannot be testable In-Reply-To: References: Message-ID: kostd kostd created ARQ-2185: -------------------------------- Summary: non-managed deployment cannot be testable Key: ARQ-2185 URL: https://issues.jboss.org/browse/ARQ-2185 Project: Arquillian Issue Type: Bug Components: core Affects Versions: 1.2.0.Final Environment: arquillian universe 1.2.0.1 wildfly 10 java 8 Reporter: kostd kostd I have uber-ear and wanna to ci some EE-integration tests on it My ear has two incarnations: prod and test. Test-ear contains productive modules + test-modules (+ arquillian auxiliary jars for Servlet 3 proto support). So I can`t deploy my ear per test nor per suite, only once per ci-build - in same build on same ear also runs drone ui-tests. i need not arq to manage my ear, so I set @Deployment(managed=false). The problem is tests are executing in RunAsClient-mode, but I need server-side mode! This is because of RunmodeUtils#isRunAsClient: {code} if (deployment != null) { runAsClient = deployment.getDescription().testable() ? false : true; runAsClient = deployment.isDeployed() ? runAsClient : true; // -- my ear not managed so not isDeployed() {code} I created my own DoNothingDeployer, but can`t override ClientDeployer nor ContainerDeployer. I tried to call deployment.deployed() before ClientTestExecuter#execute, but cannot understand event model so good enough -- either Instance#get() is null, or deployment.deployed() doesn`t affect at all. Maybe exists good doc (or javadoc) about arq event model? can`t find :'( Why can`t run server-side tests with not-managed deployment? Why in general we can`t run server-side tests without any @Deployment? We using @Drone-tests without @Deployment and it`s very good. We preparin` deployment through non-shrinkwrap way, so why we need to define non-useful @Deployment-method (or DeploymentScenarioGenerator)? -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Jun 29 13:12:00 2018 From: issues at jboss.org (kostd kostd (JIRA)) Date: Fri, 29 Jun 2018 13:12:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2185) non-managed deployment cannot be testable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599079#comment-13599079 ] kostd kostd commented on ARQ-2185: ---------------------------------- Tried to override ClientTestExecuter#execute in the way that RemoteExecutionEvent called even if managed=false. But ClientTestExecuter#deployment.get() returns null, so RemoteTestExecuter#execute ends with NPE because deployment is null and protocol cannot be found > non-managed deployment cannot be testable > ----------------------------------------- > > Key: ARQ-2185 > URL: https://issues.jboss.org/browse/ARQ-2185 > Project: Arquillian > Issue Type: Bug > Components: core > Affects Versions: 1.2.0.Final > Environment: arquillian universe 1.2.0.1 > wildfly 10 > java 8 > Reporter: kostd kostd > > I have uber-ear and wanna to ci some EE-integration tests on it > My ear has two incarnations: prod and test. Test-ear contains productive modules + test-modules (+ arquillian auxiliary jars for Servlet 3 proto support). So I can`t deploy my ear per test nor per suite, only once per ci-build - in same build on same ear also runs drone ui-tests. > i need not arq to manage my ear, so I set @Deployment(managed=false). The problem is tests are executing in RunAsClient-mode, but I need server-side mode! This is because of RunmodeUtils#isRunAsClient: > {code} > if (deployment != null) { > runAsClient = deployment.getDescription().testable() ? false : true; > runAsClient = deployment.isDeployed() ? runAsClient : true; // -- my ear not managed so not isDeployed() > {code} > I created my own DoNothingDeployer, but can`t override ClientDeployer nor ContainerDeployer. > I tried to call deployment.deployed() before ClientTestExecuter#execute, but cannot understand event model so good enough -- either Instance#get() is null, > or deployment.deployed() doesn`t affect at all. Maybe exists good doc (or javadoc) about arq event model? can`t find :'( > Why can`t run server-side tests with not-managed deployment? > Why in general we can`t run server-side tests without any @Deployment? We using @Drone-tests without @Deployment and it`s very good. > We preparin` deployment through non-shrinkwrap way, so why we need to define non-useful @Deployment-method (or DeploymentScenarioGenerator)? -- This message was sent by Atlassian JIRA (v7.5.0#75005)