Creating and deploying ejb 3.0 session bean with annotated pojo

Question

I try to create and deploy a EJB 3.0 stateless session bean (and associated webservice) with the following steps:
1) Create Interface "Repository"
package de.xxx.config;
import java.rmi.Remote;
import java.rmi.RemoteException;
import javax.jws.WebMethod;
import javax.jws.WebService;
@WebService
public interface Repository extends Remote {
     @WebMethod(operationName = "findCampaignByChannel")
     public String findCampaignByChannel(String channelName) throws RemoteException;
2) create dummy "RepositoryImpl"
package de.xxx.config;
import java.rmi.RemoteException;
import javax.ejb.Stateless;
import javax.jws.WebService;
@WebService(endpointInterface="de.xxx.config.Repository")
@Stateless
public class RepositoryImpl implements Repository {
     public String findCampaignByChannel(String channelName) throws RemoteException {
          return null;
3) The two class files are packaged into a jar without any further descriptors
4) The jar is deployed with admin_client into the oc4j instance using the commands:
-deploy -file <jarfile> -deploymentName <name>
Result:
An ear was constructed and started but no session bean or webservice is found (using the console). But according to to the docs a jar file without a ejb-jar.xml should be recognized as a EJB 3.0 ejb-jar file and the necessary steps to create session bean and expose webservice should be done automatically.
My question:
Which step do i miss here ?
Tools used:
Eclipse 3.2 for the jar file
SoaSuite 10.1.3.1 for oc4j

Answer 1

another strange problem.
i have an APplication server added ( JBOSS ).
when i create deployment profile (EAR ) application server is showed in the ComboBox .
But when i create Java Test Client for some EJB and when i check " Connect Remote Application server" there is 2 comboboxes
J2EE Application
App Server Connection.
first combo is ok there is EJB applicaiton
Secound is empty .. but i Have App Server.
Another think is that when i create EJB 3.0 its BAD to see J2EE app it must be J EE 5 app or just Java EE app