the bug is only in version 3.3.0?
so perhaps i can use version 3.2.0?
no workaround availiable?
We've checked under 3.3.0 only. Workaround (if any) will be available after the issue is investigated. Please track JIRA issue to get notified about that.
ok thank you.
i will test 3.2.0 because i need a solution...soon...because of cebit coming.
any help would be nice :-)