This week's book giveaway is in the JDBC forum.
We're giving away four copies of Make it so: Java DB Connections & Transactions and have Marcho Behler on-line!
See this thread for details.
The moose likes BEA/Weblogic and the fly likes Weblogic Console Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Make it so: Java DB Connections & Transactions this week in the JDBC forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Weblogic Console" Watch "Weblogic Console" New topic

Weblogic Console

Anurag Mishra
Ranch Hand

Joined: Jun 16, 2003
Posts: 121
i have Deployed a stateless Session Bean on Weblogic7.0. if i go thru Console of Weblogic i am able to see my Bean and its properties.
There is a option where i can change my bean from STATELESS to STATEFUL bean. when i m doing this it is telling me to restart the server to reflect changes.
But i don't know where it is changing as in ejb-jar.xml file it still shows that it is a stateless bean. Pls Clarify.

SCJP 1.2
Chris Mathews
Ranch Hand

Joined: Jul 18, 2001
Posts: 2712
Moving to BEA/WebLogic Forum...
Anurag Mishra
Ranch Hand

Joined: Jun 16, 2003
Posts: 121
As no one replied to my this problem but i got the solution so i m posting it here.
Actually when we change the Deploymentdescriptor file from WebLogic Console it updates the in-memory deployment descriptor only. so when u restart the server changes will be lost and it won't be applied on jar file on Local Disk.
to make the changes permanent i mean in memory and the Deployment descriptor on DISC, we need to
Click the root element of the tree in the left pane. The root element is the either the name of the EJB JAR archive file or the display name of the EJB.
Then in right pane u will get Two Buttons one is
Validate and another is Persist.
Click Validate to to ensure that the entries in the EJB deployment descriptors are valid.
Click Persist to write your edits of the deployment descriptor files to disk in addition to WebLogic Server memory.
I agree. Here's the link:
subject: Weblogic Console
It's not a secret anymore!