[
https://issues.apache.org/jira/browse/JS2-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701498#action_12701498
]
Ate Douma commented on JS2-973:
-------------------------------
With the jetspeed//j2-admin migration to slf4j commit (see JS2-972, r767444)
I've also excluded the xml-apis dependencies.
In addition, I've added the following section to the web.xml for both j2-admin
and jetspeed:
<!-- for deploying on Websphere: disable Websphere default portletcontainer
-->
<context-param>
<param-name>com.ibm.websphere.portletcontainer.PortletDeploymentEnabled</param-name>
<param-value>false</param-value>
</context-param>
Without this, the default Websphere 6.1 potletcontainer will try to "manage" a
portletcontainer by itself which for our purposes of course is unwanted, and
would result in errors being logged to the Websphere Systemout.log
although those can be ignored.
Remaining task therefore (so far) is fixing the unwanted generation of the
SEQUENCE and TRIGGER for the SECURITY_DOMAIN table by DDLUtils.
> 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
> 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]
