Hi folks,

some more random questions on how SIDE works.... i just started over with a very minimalistic model, containing only one Data Diagram (i.e. Model "Foo", Class Package "Bar", Data Diagram "Main" and a single class "BasisDokument" with exactly one property "hopp").

1) In the created module.SIDE_ModelExtension_Foo_Model.amp, i find some web-client-config-custom.xml containing these language override:



I suppose this doesnt make sense here, as i only want to extend my content model, and would do this kind of customization elsewhere....



2) In the generated model.xml, this fragment is generated:



However, i consider the name "Bar_BasisDokument_hopp" a bit lengthy, i'd prefer to have the short "hopp" here! So, is there some way to override the internal mechanism for output generation with some custom templates? Or something like that.

3) On successfull output generation, i have these files in my "out" folder:



So far i would need model-1.0.5.amp and module.SIDE_ModelExtension_Foo_Model.amp to deploy, but what are the others for?
Especially i wonder why the Side Alfresco Deployer Direct Deployer would deploy mysql-connector-java-5.0.3.jar, which doesn't make sense for me for two reasons:

* Alfresco 3.2 already comes with bundled mysql-connector-java-5.1.7-bin.jar
* Not all Alfresco installations run on mySQL... for example, we run Alfresco on PostgreSQL

Hope you can shed some light on this....

Cheers
Gyro

Hi,
thanks for your feedback. Yes, I thing I can shed you some light

I summarize your questions:

1) languages settings are generated

Yes, by default we directly generate these settings. It could be an option parameter.

2) Content types names are a little lenghty

Yes again, you're right. But the system has been designed so you can deploy lots of models, so to avoid collisions, we use class mechanism. I agree names are a bit lenghty, but it's a usual way to file information without collision. We could maybe imagine a kind of alias to manipulate information more easily.

We also solved it that way without going further because the end user only see translations.

3) why mysql-... jar is packaged?

We had problems a few months ago with an installation on Linux and packaged it into alfresco module for this reason. It may be untrue today.

On which platform are you using Alfresco?

JC

Sorry, were busy the last week doing other things, hope i'll can spend some time with SIDE again
FWIW, we usually run Alfresco-3.2 on CentOS, using JDK 1.6 and PostgreSQL... and then i'm currently with some customer who runs Alfresco on Solaris and PostgreSQL (and wouldn't even consider to use MySQL...)

Cheers and thanks for the elaborations
Gyro