-
Bug
-
Resolution: Done
-
Critical
-
glassfish_1.0.0.CR1
-
None
-
Release Notes
When deploying applications that use GlassFish's built-in database, the deployment often succeeds with a warning like the one mentioned below. The "SEQUENCE" already exists is a very common case.
Unfortunately, arquillian-glassfish-container treats every response with non-success response as deployment failures - which is wrong. As a result, an application that would normally deploy with a warning and work as expected cannot be tested with Arquillian ATM.
The proposed solution is to log the WARNING message and consider the deployment successful.
<?xml version="1.0" encoding="UTF-8" standalone="no"?><map><entry key="message" value=""http://localhost:4848/management/domain/applications/application/seam-booking" created successfully. PER01003: Deployment encountered SQL Exceptions: 	PER01000: Got SQLException executing statement "CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50) NOT NULL, SEQ_COUNT DECIMAL(15), PRIMARY KEY (SEQ_NAME))": java.sql.SQLException: Table/View 'SEQUENCE' already exists in Schema 'APP'."/><entry key="exit_code" value="WARNING"/><entry key="command"/><entry key="subReports"><list><map><entry key="message" value=" PER01003: Deployment encountered SQL Exceptions: 	PER01000: Got SQLException executing statement "CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50) NOT NULL, SEQ_COUNT DECIMAL(15), PRIMARY KEY (SEQ_NAME))": java.sql.SQLException: Table/View 'SEQUENCE' already exists in Schema 'APP'."/><entry key="exit_code" value="WARNING"/><entry key="command"/></map></list></entry></map>
- duplicates
-
-
- Closed
-
