On 16/09/11 14:18, Gabriel Gruber wrote:
Most work would probably be to
to Dojo 1.x. But if we just change the JS library and make the
JS code work again, I think we would be fine. Jeremy's proposal
to Dojo 1.x was much deeper: He actually wanted to implement
and redesign the whole repeater-concept.... In our case we would
quite happy with just upgrading to the latest dojo versions. In
had to tweak cocoon 2.2 already a lot, that the dojo 0.4.3 stuff
for us, there have been really strange problems...
Would it not make more sense to NOT integrate dojo into cocoon 2 (or
3). Dojo is on the client and is designed to receive JSON (or XML)
generated by the server. The server should never use Dojo directly
(just provide Dojo when the cocoon-based application is loaded in
the client). If you keep this separated, it should be very easy to
change to another Dojo version.
Workflow EDV GmbH, Dannebergplatz 6/23, A-1030 Wien
for migrating Cocoon2.2 to Spring 3
I’ve seen plenty of people asking
coming up with a new release Cocoon2.3 where cocoon would ship
- Spring 3
- Dojo 1.x
- EhCache 2.3.x
- FOP 1.0
In our particular case we would
be satisfied with being able to switch to Spring 3. But so far
successful upgrade path has been described on the mailinglist.
also looks as no effort is being put in Cocon2.2 anymore. I
want to get some confirmation on this.
We might be able to hold of making
switch for a small period of time but as a precaution I want to
if it is wiser bet my money on Cocoon3 (which does not even have
version yet) or wait for a new version of Cocoon2.2 which might
Ps. If anyone could already give the
to take to do it ourselves we would be very thankfull.
Andre H. Juffer | Phone: +358-8-553 1161
Biocenter Oulu and | Fax: +358-8-553-1141
Department of Biochemistry | Email: email@example.com
University of Oulu, Finland | WWW: www.biochem.oulu.fi/Biocomputing/
StrucBioCat | WWW: www.strucbiocat.oulu.fi
Triacle Biocomputing | WWW: www.triacle-bc.com