unfortunately no, but you should use the exploded version of JBoss Portal.
if you use the cvs build, you can do sh build.sh explode, which explodes the sar file and its content and provide you easy configuration.
$ ./build.sh explode
build.sh: *WARNING* Ignoring environment value for $ANT_HOME
build.sh: Executing: /cygdrive/c/projs/jboss-portal-2.2/tools/bin/ant -logger org.apache.tools.ant.NoBannerLogger explode
Target `explode' does not exist in this project.
Total time: 0 seconds
p.s. Thanks for your thorough explanation of JBoss Portal during today's conference!
actually you need to do it in the core module where the sar portal-service.sar is built.
I hope that the explanations were clear enough even if I had to go quickly on the subject. That was a pleasure for me to expose my work to all of you guys.
It's getting worse with the latest changes to JBoss Portal 2.2 deployed onto JBoss AS 4.0.3RC2.
Now, there're 3 directories - instance, portal and user - with Hibernate configuration files and it's a tedious task to change the dialect to org.hibernate.dialect.HSQLDialect every time I update and build Portal. It's 5 files to change.
I wonder how developers work. Do they change these files, too or is there a way to work it out? There must be a simpler solution.
One solution would be too code the dialect in the mbean service SessionFactoryBinder.
Each service would have that property, this property could eventually be overriden by a system property.
What do you think ?
The other option is to use a property file that would be in conf and setup the mapping for the sessions.
I update the code of 2.2 in order to make the detection effective for schema export and improved the code of the persistence too.