• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

EJB Deployment on WebSphere 4.0 AEs

 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I am trying to deploy EJBs on Websphere 4.0 using the AAT tool.
I see a score of errors in the default_server_stdout.log. The same EJBs work fine on Orion Application Server 1.4.5. The error log is given below. Any help is highly appreciated.
Committing working copy...
[01.11.15 19:04:55:753 EST] 2a64d88e SystemOut U Updating.
[01.11.15 19:04:55:773 EST] 2a64d88e SystemOut U Building: /Deployed_ejbmg.jar.
[01.11.15 19:04:55:813 EST] 2a64d88e SystemOut U Invoking Java Builder on /Deployed_ejbmg.jar.
[01.11.15 19:04:56:044 EST] 2a64d88e SystemOut U Scrubbing output folder
[01.11.15 19:04:56:044 EST] 2a64d88e SystemOut U Analyzing packages
[01.11.15 19:04:56:064 EST] 2a64d88e SystemOut U Analyzing sources
[01.11.15 19:04:56:675 EST] 2a64d88e SystemOut U Compiling content of ejbModule/com/mi/smartpath/dp/EjbRemoteInterface
[01.11.15 19:04:56:815 EST] 2a64d88e SystemOut U Compiling content of ejbModule/com/mi/smartpath/extension/EjbRemoteInterface
[01.11.15 19:04:56:915 EST] 2a64d88e SystemOut U Compiling content of ejbModule/com/mi/smartpath/document/EjbRemoteInterface
[01.11.15 19:04:57:075 EST] 2a64d88e SystemOut U Compiling content of ejbModule/com/mi/smartpath/common/EjbRemoteInterface
[01.11.15 19:04:57:115 EST] 2a64d88e SystemOut U Compiling content of ejbModule/com/mi/smartpath/workflow/EjbRemoteInterface
[01.11.15 19:04:59:649 EST] 2a64d88e SystemOut U Compiling content of ejbModule/com/mi/smartpath/dp/EjbRemoteInterface
[01.11.15 19:05:01:281 EST] 2a64d88e SystemOut U Compiling content of ejbModule/com/mi/smartpath/extension/EjbRemoteInterface
[01.11.15 19:05:02:563 EST] 2a64d88e SystemOut U Compiling content of ejbModule/com/mi/smartpath/document/EjbRemoteInterface
[01.11.15 19:05:03:935 EST] 2a64d88e SystemOut U (257 problems found) Copying all resources on the classpath
[01.11.15 19:05:04:025 EST] 2a64d88e SystemOut U (257 problems found) Build done
[01.11.15 19:05:04:145 EST] 2a64d88e SystemOut U Java build completed
[01.11.15 19:05:04:145 EST] 2a64d88e SystemOut U Invoking Validation on /Deployed_ejbmg.jar.
[01.11.15 19:05:04:356 EST] 2a64d88e SystemOut U ejbModule/com/mi/smartpath/document/EjbRemoteInterface/EJSBMPPDBinderHomeBean.java(28): PDBinderBean cannot be resolved or is not a type
[01.11.15 19:05:04:356 EST] 2a64d88e SystemOut U ejbModule/com/mi/smartpath/document/EjbRemoteInterface/EJSBMPPDBinderHomeBean.java(28): PDBinderBean cannot be resolved or is not a type
[01.11.15 19:05:04:356 EST] 2a64d88e SystemOut U ejbModule/com/mi/smartpath/document/EjbRemoteInterface/EJSBMPPDBinderHomeBean.java(46): PDBinderBean cannot be resolved or is not a type
[01.11.15 19:05:04:356 EST] 2a64d88e SystemOut U ejbModule/com/mi/smartpath/document/EjbRemoteInterface/EJSBMPPDBinderHomeBean.java(46): PDBinderBean cannot be resolved or is not a type
[01.11.15 19:05:04:366 EST] 2a64d88e SystemOut U ejbModule/com/mi/smartpath/document/EjbRemoteInterface/EJSBMPPDBinderHom
Thanks
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Are these EJB 2.0 EJB's or EJB 1.1 EJB's -- WAS 4.0 only supports EJB 1.1...
Kyle
------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.
 
Krishna, Alle
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Kyle,
They are EJB 1.1 EJBs.
thanks
 
Kyle Brown
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
OK, since you encountered 275 compile errors my next guess is that your EAR file doesn't contain all of the classes referenced in your EJB's. Is that true? Are you certain that all classes you reference (not provided by Sun of course) are inside the EAR?
Kyle
------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.
 
Krishna, Alle
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Kyle,
All the other files which the EJBs are refering are inside the jar file and not the ear file. The jar of course is inside the
ear file.
Also, can you please let me know if any EJB 2.0 spec code can be
ported into IBM WebSphere 4.0. I know that IBM WebSphere 4.0
supports only EJB 1.1 spec.
Is it a possibility that the errors I might be seeing is because the of the EJB 2.0 spec code being tried to be deployed on IBM WebSphere 4.0?
Thanks
Vasanth
 
Kyle Brown
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If your developers wrote the code to the EJB 2.0 spec, it will not work -- it is not backwards portable. You should ask the developers what level of the spec they wrote the code to.
It is conceivable that the errors are because of writing to the wrong level of the spec, but your developers should be able to tell you that relatively quickly.
On second glance it appears that most of the errors you define refer to a "PDBinderBean". What is that class and are you certain that it is included in the JAR?
Kyle
------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think this sollution might solve your problem, though I am not sure why it actually occurs. It seems like websphere didn't add the jar with the original code to the classpath while compiling the stubs, and therefore cannot compile them.
We had a similar problem and the way I fixed it was to change the ejbdeploy.bat script a little. This script is envoked by websphere while deploying.
If you add '%finput%' to the last argument of the java invokation line in that script ( change -cp "%ws_cp%" to -cp "%ws_cp%;%finput%" ), it should work.
There must of course be something weird causing this, but I haven't bothered to investigate it any further.
- Morten
 
Kyle Brown
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Let's try getting some things straight:
(1) PLEASE tell us; are all of these classes in a single JAR file or not? If not, then give us an indication of what your JAR and EAR file structure are. This is important.
(2) Do you see the same errors if you use the "Generate Deployment code" option in AAT?
Kyle
------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic