File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes EJB and other Java EE Technologies and the fly likes Container Managed Persistence question Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Container Managed Persistence question" Watch "Container Managed Persistence question" New topic

Container Managed Persistence question

Jason Dolan

Joined: Mar 11, 2005
Posts: 2
hi all, recently i enquired the following but to no avail
hi all

i'm new to these here forums and i'm also a student currently doing EJB's for my fourth year project and i have a problem when deploying a CMP bean in suns deploy tool:

i somehow managed to accidently try to run the client jar file in the cmd line as i was undeploying the bean in suns deploy tool (i don't know if this caused the problem though), now it tells me every time i try to redeploy the bean:

ERROR - Deploy Application in Domain
! ! ! Operation Failed ! ! !

[ Completed (time = 3,2 sec, status = 13) ]

i even tried to go thru the motions of painstakingly deploying it by hand again
this is driving me nuts

has anyone any idea what is going on, i restarted the JAS and computer several times also and i have no idea what the problem is - keep in mind that i am a student and while the answer may be clearly evident to some, it isn't to me. i also have no idea what exactly the error is telling me, damn ambiguous sun! grr i spent 3 hours trying to solve it in college today but to no avail

thanks for your help and thanks for reading this

ps i know i'm using basic tools to create the beans but our college budget is squat and i have to make do


this error seems to come up if i add a new field into the bean and redeploy
any thoughts???

thanks, jason
Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 32810

Welcome to JavaRanch!

I suspect nobody answered that question last time because we didn't know. As you can see, the error message isn't exactly descriptive.

One thing to try: see if you can create a new, simpler bean. Maybe one with just a primary key. Then see if you can add a field to that bean. Aside from giving a simpler test case to work with, you can see if it is only the initial bean that got corrupted or something more insiduous.

[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
I agree. Here's the link:
subject: Container Managed Persistence question
jQuery in Action, 3rd edition