[Isomorphic]

This doesn't sound like a behavior that's changed? Fields of type "binary" are never sent to the client in the Record. They are always downloaded via a separate "viewFile" dsRequest.

[msturzen]

Hi,

we just migrated from smartgwtPower 2.3 to smartgwtPower 2.4 and ran into the CLOB issue described above.

When trying smartgwtPower 2.5 nightlies (2011-01-19) we ran into a class File issue. A quick look into the jars revealed they have been compiled for Java SE 6.0. Unfortunately we're bound to WebSphere AS 6.1 which supports JSE 5.0 only.

- Do you (isomorphic) plan to drop JSE 5.0 support starting with smartgwt 2.5?
- Could you supply a JSE 5.0 compliant version ?

- Is there a way to get a bugfix release of smartgwtPower 2.4 having the CLOB issue solved? I'm asking this because we plan to put a new version to production soon and I really don't feel very well doing so with a nightly.

Thanks for the otherwise amazing job you did with smartgwt.

[msturzen]

Hi,

in my previous post i forgot to mention the CLOB issue comes up in hosted mode as well as in the regular deployment.

Regards

[Isomorphic]

The latest nightly build should be back to Java 5 versions (which we do not plan to drop support for any time soon).

[msturzen]

Thanks for the pleasant reply.

One more question regarding the nightly build: Is it "safe" to be used in an production environment?

[Isomorphic]

Up to you - we set expectations regarding support here.

[msturzen]

In bullet #3 you state:
(If you have a support contract with Isomorphic, ...)

Do not put nightly builds into production deployments unless you have written commitments from Isomorphic indicating that a specific nightly is supported for a specific deployment scenario.


- We don't have a support contract with Isomorphic, just some "Power" licenses.
- We'd like to use some of the new features of smartgwtPower 2.4.
- You admitted the CLOB issue is a bug an quickly fixed it (in the nightlies).

--> Is there any chance (despite missing a support contract) to get a "written commitment" to use the nightly safely in our deployment? Alternatively, do you plan to release a smartgwtXXX 2.4 bugfix release (fixing the CLOB issue and possibly more) any time soon?

This is important for us to know, so we can either drop 2.4 and look for workarounds (which would be a pity and really disappointing) or continue to extend and test our application based on the current nightly. Since there is currently no way for us to know which features have been added to the nightly we can never be sure it is suitable for production, we don't even have enough information to test code areas that have been changed.

Please try to understand our dilemma. We'd like to use some features of the new version that has a confirmed regression and the only version having it fixed may contain bugs we're unable to oversee.

[Isomorphic]

A bugfix release is planned for within roughly a month. As far as all of your other concerns, such as getting a written commitment of some kind - these are the reasons you buy support.

[msturzen]

Hi again,

roughly a month is over now ;-) I'd like to ask how the 2.4 bugfix release is doing? Do you already have a planned release date?

Regards