Endpoint registration

[monkeyden]

I have an endpoint, in my ejb jar file, deployed to JBoss 4.2.2GA. I can see the bean is being deployed but I see nothing about the endpoint registration, like I do all the portal services. I also see the portal services endpoints at the services URL http://localhost:8080/jbossws/services but not mine. Is there something else I need to do to get it to register? Perhaps a cfg file in the ear? I am using the first example from Java Web Services: Up and Running

Interface

@WebService
@SOAPBinding(style = Style.RPC) // more on this later
public interface TimeServer {
 @WebMethod String getTimeAsString();
 @WebMethod long getTimeAsElapsed();
}

Impl

@WebService(endpointInterface = "com.symcare.ids.services.TimeServer")
public class TimeServerImpl implements TimeServer {
 public String getTimeAsString() { return new Date().toString(); }
 public long getTimeAsElapsed() { return new Date().getTime(); }
}

Thanks!

[monkeyden]

The above deployment was in an ear file. I tried it according to the JBossWS documentation and had no mention of the service in the server log. I packaged the the impl and the interface in a jar file and deployed it to the "deploy" directory as directed in:

Simply wrap up the service implementation class, the endpoint interface and any custom data types in a JAR and drop them in the deploy directory. No additional deployment descriptors required.

Anyone have an idea?

[monkeyden]

I was able to get the endpoint registered when deployed in it's own jar file, but I'm not able to deploy it when it's lives within my ejb jar inside the ear file. I would imagine the solution is simple but I have yet to track it down. Suggestions are greatly appreciated.

Thanks

P.S.
Is this forum still active or should I be asking somewhere else?

[asoldano]

Have a look at the eardeployment sample in the jbossws testsuite, it does what you're trying to do.

The forum is still active, but you might not get a lot of replies in this period of the year ;-)

[monkeyden]

Are there any special files or configuration needed to get it to deploy in an ear? I have looked at the testsuite example as well as the "seam bay" example and have found no differences at all. These are the very same SEI and impl files, which deployed just fine in its own independent jar file.