Transferred from BugDB:
*** HNASSIRY 03/27/12 12:02 pm ***
Client has created a test case to mimic the issue on our side. I've included
in this ticket and including all of the jars needed. One of the projects in
the newly attached zip has two libraries that you'll need to create. I've
sent you those jars. The JMSJCA library has uses the jmsotd.jar file. The
alerter uses the com.stc.* and com.sun* jar files. You should be able to
fully compile these projects once you create the libraries in NB. Once you
are able to compile all of the projects. Follow these exact steps:
1.) Compile project WEFIWebServiceExternal.
2.) Once the compile is complete, deploy it out to a glassfish instance.
2a.) As the project is deploying, build and compile WEFIWebService
3.) Once the second compile is complete, deploy the second project to
glassfish. You should see the first project get undeployed.
Feel free to set up a webex if you get stuck and we can investigate this
*** HNASSIRY 03/27/12 12:05 pm ***
@ Following file uploaded to
@ ftp://bugftp.us.oracle.com/upload/bug_13/bug13894004 : SamplesForSupport.zip
*** HNASSIRY 03/27/12 12:08 pm ***
@ Escalation Request RECEIVED for review by BDE.
@ Request Id: ESC:13894004.1529960
*** HNASSIRY 03/30/12 01:01 pm ***
just making sure this bug is visible.
Corrected the version info.
It looks like the server plugin is doing what it is told to do...
j2eeserver thinks that the one project has to be undeployed BEFORE the second project deploys.
It looks like the root cause of this is some project name versus directory name issue. In this case we have two projects.
WEFIWebServiceInternal located in %FOO%\WEFIWebServiceInternal\test and
WEFIWebServiceExternal located in %FOO%\WEFIWebServiceExternal\test
see the internal issue for details.
it looks like this issue is NOT happening in 7.1.1.