Community
Participate
Working Groups
Following are changes: 1. add websphere.properties and websphere.xml under trunk\jpa\eclipselink.jpa.test for WebSphere special env properties and targets for install,start,stop server, config server and deploy & undeploy applications on server. 2. add configWebSphere.py, installApps.py and unInstallApps.py trunk\jpa\eclipselink.jpa.test for config server, deploy and undeploy applications. Configuring server includes creating datasource, and shared library. 3. add websphere dir under trunk\jpa\eclipselink.jpa.test\resource, to have websphere's jaxp.properties 4. modified build.xml under trunk\jpa\eclipselink.jpa.test: (1). add "detect-os" target to decide which command(Windows, or Unix) should be used in WebSphere testing (2). add "create-ejb-stubs" for generating ejb stubs for WebSphere testing (3). change "<sysproperty key="server.url" value="${server.url}${MODEL_NAME}"/>" to be <sysproperty key="server.url" value="${server.url}${APP_NAME}"/>, because WebSphere doesn't work with server.url which has application name appended during jndi lookup (4). change <copy todir="${env.JAVA_HOME}/jre/lib" file="${eclipselink.jpa.test}/resource/weblogic/jaxp.properties" failonerror="false"/> to be <copy todir="${env.JAVA_HOME}/jre/lib" file="${eclipselink.jpa.test}/resource/${server.name}/jaxp.properties" failonerror="false"/>, since WebSphere's jaxp.properties is different with WebLogic one
Created attachment 106118 [details] add support for running jpa tests on WebSphere
Created attachment 106143 [details] add support for running jpa tests on WebSphere
Adding the Jython libraries and any related scripts to EclipseLink will require a CQ. I would prefer not to do this as we approach our 1.0 release. I would also like general agreement on the dev mailing list that Jython is the general solution that will be used across the project's components.
Created attachment 107230 [details] add support for running jpa tests on WebSphere without config files This patch only includes build.xml, websphere.properties, websphere.xml, resource/websphere/jaxp.properties. The websphere config .py files configWebSphere.py, installApps.py and unInstallApps.py will be checked in later once the files finishing CQ.
Created attachment 108566 [details] patch file for changes This patch has a revised webshphere.xml, which expects the jython scripts in extension.lib.external directory rather than trunk/jpa/eclipselink.jpa.test/resource/websphere
On Yiping's behalf, I have checked in the Initial patch in both the trunk and 1.0.1 branch
The final patch requires a CQ, that may never happen.
I would like to document where developers can access copies of the WebSphere python scripts configWebSphere.py, installApps.py and unInstallApps.py for future reference either from their WebSphere install or online.
1) We need another shared library created for jpa\plugins\javax.persistence_2.0_preview.jar in the same manner as the one created for eclipselink.jar below configWebSphere.py library = AdminConfig.create('Library', n1, [['name', 'eclipselinkjpa'], ['classPath', '%%eclipselinkLibDir%%/eclipselink.jar']]) 2) I entered a separate bug so that we document the process of getting the tests running on WebSphere on Wiki. http://bugs.eclipse.org/261235 websphere.properties test.properties jndi.properties configWebSphere.py
see change in support of manual test config http://fisheye2.atlassian.com/changelog/eclipselink/?cs=3821
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
