[
https://issues.apache.org/jira/browse/JS2-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707293#action_12707293
]
Ate Douma commented on JS2-973:
-------------------------------
I found the cause of it:
http://www-01.ibm.com/support/docview.wss?uid=swg24014758 (IBM - PK33090)
Solving it requires defining (yet) another IBM webcontainer custom property in
web.xml like this:
<context-param>
<param-name>com.ibm.ws.webcontainer.invokefilterscompatibility</param-name>
<param-value>true</param-value>
</context-param>
Or, alternatively and easier, define it as webcontainer global custom property
for all web applications (see above link for instructions doing that).
Although the latter is less intrusive (for the developer/deployer), I'll use
the first solution for j2-admin to make it more explicit and to ensure it just
always works.
With this, j2-admin WicketPortlet works fine also on Webpshere 6.1
> Running Jetspeed 2.2 on Websphere 6.1 / Oracle10
> ------------------------------------------------
>
> Key: JS2-973
> URL: https://issues.apache.org/jira/browse/JS2-973
> Project: Jetspeed 2
> Issue Type: Task
> Affects Versions: 2.2.0
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.2.0
>
>
> Testing current Jetspeed 2.2-SNAPSHOT on Websphere 6.1 I;'ve encountered some
> issues which I'm recording here for the record and/or as outstanding TODO
> tasks.
> - xml-apis jar: all the JAXP apis are now part of Java5+ and having this jar
> in WEB-INF/lib causes problems on Websphere
> TODO: remove/exclude this dependency in maven poms
> - stax-api-1.0.1.jar: this artifact (incorrectly) contains
> javax.xml.namespace.* classes (QName specifically) which breaks JAXB on
> Websphere
> TODO: upgrade to stax-api-1.0.2.jar which no longer contains the
> javax.xml.namespace package
> - DDLUtils generates SEQUENCE seq_SECURITY_DOMAIN_DOMAIN_ID and TRIGGER
> trg_SECURITY_DOMAIN_DOMAIN_ID for SECURITY_DOMAIN.UIX_DOMAIN_NAME for an
> Oracle database
> During creation of the schema in the database the trigger code fails to be
> created. However, both the sequence and the trigger are not needed anyway.
> TODO: figure out how to disable the sequence and trigger generation from
> DDLUtils
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
