I will take a look today and will let you know when the update is available.
I was able to successfully install the demo today. I think what you are seeing is a whitespace issue with the standalone.diff file.
Can you try "git apply --whitespace=fix standalone.diff" and let me know if that helps?
Thanks for the response. It only works on deploying teiid to openshift application where jbosseap-6.0 cartridge is installed.
But for me, I am trying to deploy teiid to openshift application with jbossas-7 cartridge installed, this call still fails, here is the error:
c:\openshift\teiiddemo>git apply --whitespace=fix standalone.diff
standalone.diff:9: trailing whitespace.
standalone.diff:17: trailing whitespace.
<driver name="teiid-local" module="org.jboss.teiid">
standalone.diff:18: trailing whitespace.
standalone.diff:19: trailing whitespace.
standalone.diff:20: trailing whitespace.
error: patch failed: .openshift/config/standalone.xml:32
error: .openshift/config/standalone.xml: patch does not apply
You see, even I add the "--whitespace=fix" option, the "git apply" command still failed.
1 of 1 people found this helpful
Sorry, but we no longer support the AS7 cartridge for the Teiid OpenShift Demo. There were a couple significant bug fixes that are resolved by using the jbosseap-6.0 cartridge.
Thanks Mark for that info.
During the teiid deploy (git push), I saw floowing error from screen output:
remote: Running .openshift/action_hooks/deploy
remote: ERROR 1146 (42S02) at line 1: Table 'teiiddemo.ACCOUNT' doesn't exist
remote: Schema not found --> Importing schema from .openshift/action_hooks/customer-schema.sql
But it looks like teiid got deployed successfully, and database tables got created at mysql. so what is this error?
You can ignore that error message. When the demo is first installed, there is an action hook that loads demo data into the mysql database. To determine whether to load the data, the script does a check against the db to see if the ACCOUNT table exists. That message shows up on the initial install because the ACCOUNT table is not there. Then If user makes any subsequent changes to their OpenShift installation, the script will skip the db loading.