[JBoss JIRA] (ARQ-1009) ClassNotFoundException when using CLEAN_INSERT
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1009?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1009:
-------------------------------
Fix Version/s: persistence_1.0.0.Alpha7
(was: persistence_1.0.0.next)
> ClassNotFoundException when using CLEAN_INSERT
> ----------------------------------------------
>
> Key: ARQ-1009
> URL: https://issues.jboss.org/browse/ARQ-1009
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: persistence_1.0.0.Alpha4
> Environment: Windows 7, Java 1.6.0_31
> Reporter: Karsten Ohme
> Assignee: Bartosz Majsak
> Fix For: persistence_1.0.0.Alpha7
>
>
> I set in arquillian.xml the configuration property:
> <property name="dataSeedStrategy">CLEAN_INSERT</property>
> When starting the test I get a ClassNotFoundException in ConfigurationTypeConverter in line 182:
> Object instance = Class.forName(value).newInstance();
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ARQ-1360) Persistence extension doesn't handle certain special characters.
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1360?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1360:
-------------------------------
Fix Version/s: persistence_1.0.0.Alpha7
(was: persistence_1.0.0.next)
> Persistence extension doesn't handle certain special characters.
> ----------------------------------------------------------------
>
> Key: ARQ-1360
> URL: https://issues.jboss.org/browse/ARQ-1360
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: persistence_1.0.0.Alpha6
> Reporter: John Ament
> Assignee: Bartosz Majsak
> Fix For: persistence_1.0.0.Alpha7
>
>
> The persistence extension seems to choke when sql scripts (.sql files) contain certain characters.
> 1. If I put "©" in my statement it treats the ; as a terminator.
> 2. If I put a new line in my file, it treats that as a terminator.
> 3. If I put a / (e.g. </some-tag> from xml) in my SQL, it gets very confused.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ARQ-1572) Marry Persistence and JRebel extensions
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1572?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1572:
-------------------------------
Fix Version/s: persistence_1.0.0.Alpha7
(was: persistence_1.0.0.next)
> Marry Persistence and JRebel extensions
> ---------------------------------------
>
> Key: ARQ-1572
> URL: https://issues.jboss.org/browse/ARQ-1572
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: persistence_1.0.0.Alpha6
> Reporter: Bernard Labno
> Assignee: Bartosz Majsak
> Fix For: persistence_1.0.0.Alpha7
>
>
> JRebel extension currently does not pick up changes in datasets.
> Here is how it works:
> If there is no target/jrebel-temp/.../*.meta file for given deployment then it assumes user wants full redeploy. If such file is present then deployment is blocked and tests are run at once.
> JRebel extension also checks if there is a rebel.xml file in the archive. If not then it generates such file based on exact content of the archive and explodes archive into target/jrebel-temp/*.
> Now the problem is that if resource is not in the archive then it will not be included in generated rebel.xml and thus won't be picked up by JRebel.
> Datasets are now automatically packed inside WEB-INF/lib/randomUUID.jar. JRebel will not substitute resources or classes from bundled libs. We could generate additional rebel.xml for that but I'd have to know what is the name of such archive and we would tightly couple both extensions.
> It would be easiest if Persistence ext would pack datasets directly into WE-INF/classes.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ARQ-1352) Script can not insert unix path separator '/' into the DB
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1352?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1352:
-------------------------------
Fix Version/s: persistence_1.0.0.Alpha7
(was: persistence_1.0.0.next)
> Script can not insert unix path separator '/' into the DB
> ---------------------------------------------------------
>
> Key: ARQ-1352
> URL: https://issues.jboss.org/browse/ARQ-1352
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: persistence_1.0.0.Alpha6
> Reporter: Sandor Bodo-Merle
> Assignee: Sandor Bodo-Merle
> Fix For: persistence_1.0.0.Alpha7
>
> Attachments: 0001-ScriptExecutor-fix-commit-parsing.patch
>
>
> I have a test class which try to insert a unix path value in the DB on schema creation:
> @CreateSchema({"setup.sql"})
> public class UserTest {
> ...
> }
> Th the ScriptExecutor introduced in 1.0.0.Alpha6 will iron out the '/' character from the path on insert - like in the following small example:
> public class main {
> public static void main(String[] args) {
> final String ANSI_SQL_COMMENTS_PATTERN = "--.*|//.*|(?s)/\\\\*.*?\\\\*/|(?s)\\{.*?\\}";
> String script = "INSERT INTO config (name, value) VALUES ('path', '/home/sbodo/test.txt');";
> System.out.println(script.replaceAll(ANSI_SQL_COMMENTS_PATTERN, ""));
> }
> }
> Output is:
> INSERT INTO config (name, value) VALUES ('path', 'sbodo/test.txt');
> instead of:
> INSERT INTO config (name, value) VALUES ('path', '/home/sbodo/test.txt');
> Tested with Jboss 7.1.1 and Postgres 9.1.
> The test worked fine in 1.0.0.Alpha5.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ARQ-1440) Performance drops > 300%
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1440?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1440:
-------------------------------
Fix Version/s: persistence_1.0.0.Alpha7
(was: persistence_1.0.0.next)
> Performance drops > 300%
> ------------------------
>
> Key: ARQ-1440
> URL: https://issues.jboss.org/browse/ARQ-1440
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: transaction_1.0.0.Alpha3, persistence_1.0.0.Alpha6
> Environment: Windows 7 / JDK 1.7.0_25 x64 / Oracle 11gR2 / Oracle ojdbc6 driver / Glassfish 3.1.2 b23 / Arquillian 1.1.0-Final / Arq persistence ext 1.0.0a6 / Arq tx ext 1.0.0a3
> Reporter: Noah White
> Assignee: Bartosz Majsak
> Priority: Critical
> Fix For: persistence_1.0.0.Alpha7
>
>
> I updated my Arquillian environment to 1.1.0-Final, Arq persistence ext 1.0.0a6 and Arq 1.0.0a3 FROM Arq 1.0.1, persistence 1.0.0a5 (no tx ext in that env since it was part of the persistence ext) and my Arquillian persistence tests which deploy to a managed Glassfish container take over 3x as long as they did in the old environment.
> For example one test which took 13s to run in the old environment now takes 44s.
> This slow down only seems to affect tests which use the persistence extension.
> Arquillian tests which do not use the persistence extension take the same amount of time as they did in the old environment. If I switch the environment back I see the performance goes back up for persistence extension tests.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month