– SomeService.java will be annotated with @WebService class annotation

– Web methods will be annotated with @WebMethod annot.

* To Test, right click on (the ‘services’ trigger ‘Run As’) SomeService.java and do ‘Run As’ with ‘Run On Server’ selection.

– The web service test page is displayed with URL:

http://host:7001/wls_utc/WebServiceProjectName/WebServiceName?WSDL

– The web service test client page:

http://host:7001/wls_utc/

>> To enable or disable the domain configuration locking feature in a development domain:

In browser, http://host:7001/console, log in as admin..

1. In the banner toolbar region at the top of the right pane of the Console, click Preferences.
2. Click User Preferences.
3. Select or clear Automatically Acquire Lock and Activate Changes to enable or disable the feature.
4. Click Save.

In WebLogic 10.3, I was not able to do the same thing.
The exception said that WebLogic JNDI failed to find the bean.
As some searches indicated, I should have used something like this for
the lookup string: “BookTestBean#com.blah.BookTestBeanRemote” ..
I tried all kinds of combinations but I was not able to make it work.

In JBoss, the “Home” interface is not required. In WebLogic, it is required.
This may have something to do with different levels of implementation
of the EJB spec but I would think JBoss 5 and WebLogic 10
should be pretty close in compatibility.. maybe.. what do I know?

Based on this, the only way I was able to make WebLogic work, was via
the “Home” interface:

Porting JBoss EJB3s to WebLogic is not trivial.. Here are some of the compliance exceptions:

weblogic.ejb.container.compliance.ComplianceException: Home methods are not allowed on session beans: BookTestBean.test()

weblogic.ejb.container.compliance.ComplianceException: In EJB BookTestBean, method test() on the home interface does not throw java.rmi.RemoteException. This is a required exception.

weblogic.ejb.container.compliance.ComplianceException: In EJB BookTestBean, the home interface de.laliluna.library.BookTestBeanLocal must extend the javax.ejb.EJBHome interface.

weblogic.ejb.container.compliance.ComplianceException: In EJB BookTestBean, the home interface of a stateless session bean must have one create method that takes no arguments.

weblogic.ejb.container.compliance.ComplianceException: In EJB BookTestBean, the return type for the home create method create() must be the remote interface type of the bean.

Persistence-related exception:

org.apache.openjpa.util.MetaDataException: “de.laliluna.library.Book.id” declares generator name “book_sequence”, but uses the AUTO generation type. The only valid generator names under AUTO are “uuid-hex” and “uuid-string”.

— Using the WL Scripting Tool (WLST)
If you are working on the WL server you can use the WL Scripting Tool to browse the available Runtime beans:
D:\Data\bea\wlserver_10.0\server\bin>setWLSEnv.cmd
D:\Data\bea\wlserver_10.0\server\bin>java weblogic.WLST
connect(‘username’,’password’,’t3://host:8003′)
serverRuntime()
ls()
cd(“JMSRuntime”)
ls()
cd(“server01_01.jms”)
ls()
…