Notes on upgrading from Orbeon Forms 3.8 to 3.9

Need to change theme.xsl as follows:

From:
<!– Copy body attributes –>
<xsl:apply-templates select=”/xhtml:html/xhtml:body/@*”/>

<xsl:apply-templates select=”/xhtml:html/xhtml:body/node()”/>

<xsl:for-each select=”/xhtml:html/xhtml:head/xhtml:script”>
<xsl:element name=”xhtml:{local-name()}” namespace=”{namespace-uri()}”>
<xsl:apply-templates select=”@*|node()”/>
</xsl:element>
</xsl:for-each>

To:
<!– Body –>
<xsl:apply-templates select=”/xhtml:html/xhtml:body”/>
<!– Handle post-body scripts if present. They can be placed here by oxf:resources-aggregator –>
<xsl:apply-templates select=”/xhtml:html/xhtml:script”/>

Use of xxforms:get-remote-user (xforms:setvalue)

From:
<xforms:setvalue ref=”instance(‘ins-current-user’)/name” value=”xxforms:get-remote-user()”/>

To:
<xforms:setvalue ref=”instance(‘ins-current-user’)/name/text()” value=”xxforms:get-remote-user()”/>

Ongoing is the use of XBL – the map component in particular
(Fixed in the final release)

Rather carelessly I filled up my root partition and was therefore unable to login as I kept getting thrown back to the login screen

The solution was to boot from the original ubuntu iso image via the virtual box settings and ‘Try Ubuntu’

From there it’s possible to mount /dev/sda1 and delete some files to make some space

After that it’s possible to login again and create a new disk/partition in the usual fdisk, mkfs way

Symptom:
Running `mysql` gives:
ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)

Running `mysql -h “hostname”` works

Fix:
Add the following to /etc/hosts.allow
mysqld:127.0.0.1:ALLOW

To cut a long story short I needed to ensure that the following lines were present in public_html/php.ini

extension=pdo.so
extension=pdo_sqlite.so
extension=sqlite.so
extension=pdo_mysql.so

In Settings/Network select Bridged Adapter if you want to be able to connect to the vm

In Settings/Display increase the amount of video memory

apt-get update
apt-get upgrade
apt-get install dkms

reboot

Then use the file manager to select/mount the additions so that they can be installed

Create a file settings.xml in ~/.m2 that’s C:Documents and Settingsiwright.m2 in my case using cygwin on XP

Create a server entry with the necessary info e.g. if using ssh
<servers>
<server>
<id>cggh</id>
<username>iwright</username>
<privateKey>C:Documents and Settingsiwright.sshid_rsa</privateKey>
<passphrase>mypassphrase</passphrase>
<directoryPermissions>775</directoryPermissions>
<filePermissions>664</filePermissions>
</server>
</servers>

Note that if you are using cygwin then you will probably need to copy your .ssh directory from /cygwin/home/username to Documents and Settingusername

Run a deploy command
mvn verify install:install deploy:deploy

If the deployment repository isn’t set in the pom then you can also define it using:
-DaltDeploymentRepository=cggh::default::scp://cloud1.cggh.org/var/www/maven

(Note the id cggh must match the id in settings.xml otherwise the permissions won’t be resolved from the settings.xml)

Creating a web application to update an existing database with Roo is extremely simple…

project –topLevelPackage org.cggh.quac –projectName quac –java 6
persistence setup –provider HIBERNATE –database MYSQL –databaseName drupal_users –userName drupal6 –password drupal6
database introspect –schema drupal_users
database reverse engineer –package ~.model –schema drupal_users
controller all –package ~.web

Some notes:
Make sure that the database has foreign keys set up
If you want security then run:
security setup

For password encoding:
(See https://jira.springsource.org/browse/ROO-1133)
Add the following to src/main/resources/META-INF/spring/applicationContext.xml
<bean id=”passwordEncoder” class=”org.springframework.security.authentication.encoding.MessageDigestPasswordEncoder”>
<constructor-arg value=”MD5″ />
</bean>

Add the following to the Users class:
@Autowired
@Transient
transient private MessageDigestPasswordEncoder passwordEncoder;

private String pass;

public void setPass(String password) {
if(password==null||password.equals(“”)) {
return; //don’t update password if blank is sent
}
String encodedPassword = passwordEncoder.encodePassword(password, null);
this.pass = encodedPassword;
}

With thanks to http://www.mail-archive.com/users@tomcat.apache.org/msg74521.html

Although it’s deprecated putting the context in server.xml seems to work quite nicely
however if you want to auto deploy e.g. on a CI server then you need to get a bit cleverer….

Don’t keep the application in the appBase – locate it outside of
Tomcat’s directory structure, and use the docBase attribute of the
element to tell Tomcat where to find it. Replace the .war file at your
leisure, and then do a touch of the .xml file to trigger an application redeployment

1) I have created a folder with absolute path:
##war directory##
2) In this folder I have placed my WAR file, ##Application##.war
3) In apache-tomcat-6.0.20/conf/Catalina/localhost
I have placed a file called ##Application.xml## (contents of file below).

<?xml version="1.0" encoding="UTF-8"?>

<Context docBase="##war directory##/##Application.war##">
        <Resource name="jdbc/postgres" auth="Container"
                type="javax.sql.DataSource"
driverClassName="org.postgresql.Driver"
                url="jdbc:postgresql://localhost:5432/XXXXXX"
                username="YYYYYY" password="ZZZZZZ" maxActive="20"
maxIdle="10"
                maxWait="-1"/>
</Context>