Guys-
This issue is now resolved. See http://jira.jboss.com/jira/browse/JBPORTAL-983
for more details
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4009176#4009176
Reply to the post :
hurzeler-
I am looking into this bug right now.
Can you upload the image file that is not working for you, so that I can
reproduce the problem on my box.
You can attach it to this JIRA task or email it to me:
[EMAIL PROTECTED]
JIRA task: http://jira.jboss.com/jira/browse/JBPORTAL-983
Thanks
This didn't work in 2.4 either. See
http://www.jboss.com/index.html?module=bbop=viewtopict=88506.
The JIRA is http://jira.jboss.com/jira/browse/JBPORTAL-983 if you want to vote
for it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4003862#4003862
Reply to
That is correct but as far as I know the issue was attributed to the Oracle
JDBC drivers. The fact that it does not work with Postgres as well point to the
fact that there might be an issue with the way CMS handles blobs or large
objects after all.
I hope the issue gets looked at soon. It is
I tried to get postgres and Portal playing ball, but I think it's a similar
issue to the Oracle one - lousy jdbc implementations.
If you have Oracle, why not try using that again - see my script (blue) for
getting it all going together...
