Exposing EJB interfaces as Web Service

Hi all,
I created a prototype using EJBs and Web Services and found out that JDeveloper only allows to expose as Web
Services the Remote interfaces of EJBs and not the Local ones.
Assuming I have included Local and Remote interfaces for each of my EJBs exposed, my questions is, after deploying the application on OC4J 10g are the Web Services accessing the EJBs through the Local interface (I assume it should) but then why I am only allowed to expose the Remote one as Web Service?
TIA,
Best Regards,
Giovanni

Hi,
no, inbound interfaces can only call web services
that are exposed on some other web servers
only outobund XI interfaces can be exposed as web services
(in this case XI acts as a web server)
and other applicaitons can call this outbound interface
Regards,
michal

Similar Messages

Exposing Inbound Interfaces as Web Service

Hi,
when it comes to expose XI interfaces as web services, the XI documentation quotes:
"Sie können sowohl von Outbound- als auch von Inbound-Message-Interfaces WSDL-Beschreibungen erzeugen."
-> i.e. Inbound interfaces can be exposed as web services.
But the web service definition wizard expects the quotation of an outbound interface. So am I right when I say that I always need an outbound interface? If yes, why is it possible to expose inbound interfaces???
Cheers,
Heiko

Hi,
no, inbound interfaces can only call web services
that are exposed on some other web servers
only outobund XI interfaces can be exposed as web services
(in this case XI acts as a web server)
and other applicaitons can call this outbound interface
Regards,
michal

EJB 3.0 Web Service

Hi!
I tried to create a Web Service (through wizard) from existing EJB 3.0 Session Bean. Basicly, the wizard just added @WebService annotation to my existing code...
Now, the problem is that simple methods like:
@WebMethod
public String helloWorld() {
return "Hello World!";
}works fine. Expect that if I use Local Interface for this Session Bean, the WSDL shows two helloWorld methods (and one is with exclamation icon showing some kind of problem with multiple methods with same name - but it is not true, I have one and the other one is just interface).
But, when I want to expose my real business service methods like:
@WebMethod
public List<Employee> getEmployees() {
return (List<Employee>)q.getResultList();
}it doesn't work (the Web Service create wizard finishes ok but service doesn't work)! When I try "Test Web Service" (from Session Bean context-menu) or "Show WSDL for Web Service annotations" the error is thrown (Null pointer exception in WSDL).
Basically, it looks to me that Web Service cannot use EJB Entities as parameters or results. Is this correct? I saw some examples on EJB 3.0 web services and there are entities routinely used as both input and output parameters.
Can someone, please, explain me what I'm doing wrong here.
Thanks in advance,
Pedja
P.S. In Web Service wizard, only SOAP 1.1 is enabled. How can I choose SOAP 1.2? And what EJB 3.0 bindings are in same context (SOAP 1.2 or EJB 3.0 bindings?)?

Hi Frank,
Most of those problems are resolved (NPE was due to Timestamp field, and two methods with the same name in WSDL because of not choosing to generate SEI in wizard, so the generated WSDL had one method from the Session bean and the other from it's Local interface). But, the errors should DEFINITELY be more descriptive.
Does the wizard work correctly? I noticed plenty of "bug like" details. For example, if I choose to create asynchronous web service, later when I go to Properties the "Asynchronous Web Service" checkbox isn't checked. Also, the @WebMethod annotations are sometimes generated and sometimes not (even if the method is checked to be exposed).
I am also getting these exceptions when I create a proxy for the asynchronous web service (I selected "Generate asynchronous methods for all operations"), could be I'm doing something wrong:
WARNING: The parameter/return type "java.util.concurrent.Future" in the method
"public abstract java.util.concurrent.Future<?>
view.proxy.MyAsyncWebService1.queryDepartmentFindAllAsync(javax.xml.ws.AsyncHandler<view.proxy.types.QueryDepartmentFindAllResponse>)"
is not supported. This method will not be exposed.
WARNING: The parameter/return type "java.util.concurrent.Future" in the method
"public abstract java.util.concurrent.Future<?>
view.proxy.MyAsyncWebService1.returnEmployeeAsync(javax.xml.ws.AsyncHandler<view.proxy.types.ReturnEmployeeResponse>)"
is not supported. This method will not be exposed.
Exception in thread "main" java.lang.NullPointerException
     at com.sun.xml.bind.v2.runtime.Coordinator.popCoordinator(Coordinator.java:122)
     at com.sun.xml.bind.v2.runtime.XMLSerializer.close(XMLSerializer.java:823)
     at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:310)
     at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:230)
     at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:87)
     at oracle.j2ee.ws.common.databinding.runtime.jaxb20.Jaxb20Serializer.serialize(Jaxb20Serializer.java:218)
     at oracle.j2ee.ws.common.databinding.runtime.SerializerBase.serializeSequenceWrapper(SerializerBase.java:80)
     at oracle.j2ee.ws.client.jaxws.SoapRequestorSerializer.populateSoapMessage(SoapRequestorSerializer.java:89)
     at oracle.j2ee.ws.client.jaxws.WsClientProxyInvocationHandler.invoke(WsClientProxyInvocationHandler.java:184)
     at $Proxy11.returnEmployee(Unknown Source)
     at MyAsyncWebService1SoapHttpPortClient.main(MyAsyncWebService1SoapHttpPortClient.java:22)
Process exited with exit code 1.Can anyone throw some light on this?
Thanks,
Pedja

Exposing RFC as a Web Service

Hello All,
I am working on a SOAP to SOAP (Backend as ECC where I am exposing an RFC as Web Service). Once the Web service is generated for RFC and the WSDL is imported in PI, I can see that all the fields in different nodes become mandatory.
Is it how normally Web Service for BAPI works or can this behaviour (mandatory / optional) be controlled ?
Also when I execute the end to end scenario via SOAP UI, I don't get any error back but also neither get the Return table nor the Sales Order NO. I am using the BAPI BAPI_SALESORDER_CREATEFROMDAT2.
Can it be because of no COMMIT (The BAPI uses external commit although this reason seems less likely as executing a RFC wo any commit atleast gives me a Sales Order no) ?
How can this call be analysed in backend ECC system ? (As I assume that messages will not be visible in SXMB_MONI as explained by the Harald's thread below. I am currently in process of getting authorization of SOAMANAGER logs but wondering how it'll help?
Thanking you in advance.
SOAP to SOAP scenario: XML messages not visible in SXMB_MONI
Cheers
KanesI

Hi,
Please see the SOAP ststud..
http://<host>:5<sys#>00/mdt/amtServlet
also you might check any error logs.
The error is because of invalid xml document. So check the validity of the xml message ie. after first mapping i.e Req mapping.
For this you can refer this -
http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
See the below links
Also this blog may help you-/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
Could not post a SOAP request to the interface
Message Servlet is in Status ERROR
Error while posting messages to SOAP sender adapter SP 13
http://localhost:50000/XISOAPAdapter/HelperServlet?action=FindChannel&channel=PartyA:SOAPService:soapchannel
SOAP Adapter in PCK
Regards
Chilla..

No business interface, component interface or web service endpoint interface found for Session Bean SessionEJB

hi ,
i am just using EJb in my Application
just created an SessionBean and with Local interface in it i am getting this wierd exception with weblogic NetBeans and eclipse also
weblogic.ejb.container.compliance.ComplianceException: No business interface, component interface or web service endpoint interface found for Session Bean SessionEJB
weblogic.ejb.container.compliance.ComplianceException: No business interface, component interface or web service endpoint interface found for Session Bean SessionEJB
    at weblogic.ejb.container.compliance.SessionBeanClassChecker.checkInterfacesExist(SessionBeanClassChecker.java:177)
    at weblogic.ejb.container.compliance.Ejb30SessionBeanClassChecker.checkInterfacesExist(Ejb30SessionBeanClassChecker.java:27)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at weblogic.ejb.container.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:331)
    at weblogic.ejb.container.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:280)
    at weblogic.ejb.container.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:789)
    at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:222)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:461)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:428)
    at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:437)
    at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:795)
    at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:683)
    at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1254)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:442)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    at weblogic.ejb.container.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:321)
    at weblogic.ejb.container.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:280)
    at weblogic.ejb.container.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:789)
    at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:222)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:461)
    Truncated. see log file for complete stacktrace
>

Hi Rajendar,
I think the problem with having empty interfaces, or interfaces without methods for EJBs, is that they don't really make "sense". After deploying your EJB, a client application will use JNDI or dependency injection to access your EJB. So in your case it will look something like this
@EJB
    mytestSSBLocal myejb; //(In this case we are using the local interface)
In the second step, you will want to do something will your EJB, but since mytestSSBLocal doesn't define any methods, there is nothing you can do with your ejb.
The Exception is telling you that weblogic couldn't find a complaint interface for your EJB.
best regards, Nicolas

Overloaded ejb methods as web service

I implemented an ejb as a web service. The ejb has 4 overloaded methods. When I looked at the generated wsdl, only one signature was exposed as a web service. Is there a way to make all 4 overloaded methods available to the web service ?

Hi Sandy,
The WLS 6.1 docs clear states that method overloading is not supported with WebLogic
Web Services:
http://e-docs.bea.com/wls/docs61/webServices/develop.html#1034539
However, you might be able to simulate something similar by passing a org.w3c.dom.DocumentFragment
to the method. For example,
public org.w3c.dom.DocumentFragment overloadedMethod(org.w3c.dom.DocumentFragment
variableArgs)
This allows you to use the flexibility of XML to provide various input and output
parameters for the method. In the method's implementation, you determine which
arguments have been passed by parsing the variableArgs node. For quasi type safety,
you could use the xsi:type attribute to associate data types with fragment elements.
Note that you will need to use literal XML encoding to do this.
HTH,
Mike Wooten
Sandy <[email protected]> wrote:
I implemented an ejb as a web service. The ejb has 4 overloaded methods.
When I looked at the generated wsdl, only one signature was exposed
as a web service. Is there a way to make all 4 overloaded methods available
to the web service ?

Exposing a process as web service on Oracle BPM 11g

Hi!
Does somebody know how can I expose a process as a web service on Oracle BPM 11g? How does it works?
In the version 10.3, when we exposed a process as web service it always had 3 default methods: startSession, getInstanceStatus and discardSession, is it the same in the 11g version?
Where can I found some info about it? Any tutorial?
Thanks a lot!
Ana

Typically you would use a Message Start event to start the process in conjunction with a Message End event. This will allow your process to be called as an asynchronous web service.
In the "Implementation" section for the start event, you specify the input parameters. You can specify "Define Interface" to directly define the interface, or use an existing interface from the BPM Catalog (the From Catalog option).
For further details on the different event types and their use cases, refer to the modeling and implementation guide:
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15176/toc.htm
You can test the web service and examine the WSDL and endpoints by using FMW control (Enterprise Manager). In the menu on the left hand side: expand SOA -> SOA-Infra -> <Partition Name> -> Composite Name, then click the "Test" button at the top.

Article written on EJB 3.0 , web services develop n deploy on JBOSS AS

Dear Friends
I would like to announce the article written on EJB 3.0 , web services development and deployment on JBOSS AS at the following location http://jamessmithjava.100webcustomers.com/index.html , I think this would help developers to increase interest on JBoss as well as EJBs
Regards
James
[email protected]
http://tech.groups.yahoo.com/group/james_smithjava

Dear Friends
I would like to announce the article written on EJB 3.0 , web services development and deployment on JBOSS AS at the following location http://jamessmithjava.100webcustomers.com/index.html , I think this would help developers to increase interest on JBoss as well as EJBs
Regards
James
[email protected]
http://tech.groups.yahoo.com/group/james_smithjava

Benefits of exposing function module as web services

Hi All,
We are developing a case study about exposing function modules as web services.
Those web services would be later used for integration to SAP box with a Java application.
Kindly help me with the pros and cons of exposing function modules as web services when compared to SAP PI. Also please do quote some examples, wherever possible.
Thanks,
Varun

Hi Varun,
Pros--->
1)Exposing FM as Web Services is indeed a good choice when you want service consumer to be platform and language independent.
i.e it can be consumed by .Net, java or any other language.
2) You are moving towards SOA
3) Composing Business Process by concatenating different functional modules is easy.
4) Complexity is less while consuming services Java, CAF etc.
Cons----> Performance for Web Services is comparatively less than JCo .
If you are bringing PI in between landscape, you are increasing one more layer of middleware which would also hit performance.
The benefit which PI can give is monitoring your company wide integrations at one central point when you have huge systems.
Hope this helps.
Piyush

Binding RESTful web service / being exposed to a RESTful web service

Hi , I have two quick questions
1. can ORACLE BPEL bind a RESTful web service?
2. can a BPEL process be exposed to a RESTful web service?
Thanks

Bumping back to the top of the list.
Has anyone got any experience with RESTful web services saving to an item vs. a collection? Any pointers are greatly appreciated.
Earl

Exposing backend data as Web Service

I have an RFC which takes in employee name as input and supervisor name as output.
I want to expose this functionality as Web Service using NWDS. What should I do? Any good tutorial?

Hi,
Check this weblog, which mentions how to convert RFCs as Webservices
Using RFC as WebService in WebDynpro
Regards,
Ganesh N

Cannot find the WSDL as I expose a process to web service

Hi,
I have a simple process, and I try to expose it to a web service by using "Process Web Service", and I start the studio web server and test it with "http://localhost:8598/Lesson19-4WebService/webservices/ProcessService?WSDL" but no WSDL appear. Could you help me? Thanks in advance.
Best Regards,
Bill

Please find the following forum.
Process exposed as a web service does not work when deployed
This should resolve the issue.
Hope this helps.
Sarat

Follow up to web services question: How do I expose java components as web services on iPlanet 6.0 app server?

My task - my company has several legacy PowerBuilder applications that access a variety of Sybase and MS SQL databases. Rather than re-inventing the wheel by re-writing these applications in Java, we would like to enable these applications to call java components (EJBs) that will provide new functionality. I would need a piece of software called CSXtend (from www.cynergysystems.com) to allow PowerBuilder to call a web service. However, I am not sure how to expose my business functions (EJBs) as web services on the iPlanet 6.0 App server. Thanks for all previous responses! Any additional info would be greatly appreciated! Mike

I have used Glue (http://www.themindelectric.com/products/glue/glue.html) to expose some of our stuff as Web Services. I recently found this on serverside. It's pretty good.
http://www.theserverside.com/resources/article.jsp?l=Systinet-web-services-part-1
I believe that the middleware they use can be plugged into IPlanet. There is also an article in the knowledge base on the IPlanet site.
Jon

EJB 3.0 Web Services - Custom Request/Response Wrappers

Hi All,
I'm having an issue using Document Literal Wrapped web services with EJB 3.0. I have declared a service endpoint interface(SEI) in one jar file, along with custom wrapper classes for the requests and responses. The wrappers have the XML content customized a bit (different type names, etc.), but should be compatible with the @RequestWrapper and @ResponseWrapper annotations. The implementation is in an EJB jar file that includes the jar with the SEI in it. My issue is that the wrapper classes I declared are not being used, and instead new ones are being generated. Is it even possible for it to use supplied wrappers, or does it have to generate its own (and if so, is it in any way possible to specify the XML types it generates). I've tested this with wsgen, and I get the same result (new wrapper classes, the ones I supplied ignored) as when I deploy it. Here is the output from wsgen:
Note: ap round: 1
[ProcessedMethods Interface: com.company.IngestorService]
[should process method: ingestProductDirectory hasWebMethods: false ]
[endpointReferencesInterface: true]
[declaring class has WebSevice: true]
[returning: true]
[WrapperGen - method: ingestProductDirectory(java.lang.String,java.lang.String)]
[method.getDeclaringType(): com.company.IngestorService]
[requestWrapper: com.company.IngestProductDirectoryRequest]
[should process method: datatypes hasWebMethods: false ]
[endpointReferencesInterface: true]
[declaring class has WebSevice: true]
[returning: true]
[WrapperGen - method: datatypes()]
[method.getDeclaringType(): com.company.IngestorService]
[requestWrapper: com.company.DatatypesRequest]
com\company\DatatypesRequest.java
com\company\DatatypesResponse.java
com\company\IngestProductDirectoryRequest.java
com\company\IngestProductDirectoryResponse.java
Note: ap round: 2
I note that is says "hasWebMethods: false". Could that be an issue? Could it not be seeing my methods as web methods. The SEI and the implementation class are in different jar files and different packages. Could this be an issue?
Here is the web service interface:
@WebService(
name = "IngestorService",
targetNamespace = "http://company.com/"
@SOAPBinding(
style = SOAPBinding.Style.DOCUMENT,
parameterStyle = SOAPBinding.ParameterStyle.WRAPPED
public interface IngestorService
@WebMethod(
action = "http://company.com/ingestProductDirectory"
@WebResult(
name = "response",
targetNamespace = ""
@RequestWrapper(
className = "com.company.IngestProductDirectoryRequest"
@ResponseWrapper(
className = "com.company.IngestProductDirectoryResponse"
public void ingestProductDirectory(
@WebParam(
name = "sourceDirectory",
targetNamespace = ""
String sourceDirectory,
@WebParam(
name = "datatype",
targetNamespace = ""
String datatype);
@WebMethod(
operationName = "datatypes",
action = "http://company.com/datatypes"
@WebResult(
name = "datatypes",
targetNamespace = ""
@RequestWrapper(
localName = "DatatypesRequest",
className = "com.company.DatatypesRequest"
@ResponseWrapper(
localName = "DatatypesResponse",
className = "com.company.DatatypesResponse"
public List datatypes();
Here are the datatype request and response wrappers:
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(
name = "DatatypesRequest"
public class DatatypesRequest
DatatypesResponse.java:
@XmlAccessorType(XmlAccessType.PROPERTY)
@XmlType(
name = "DatatypesResponse",
propOrder =
"datatypes"
public class DatatypesResponse
private List<String> _datatypes;
@XmlElementWrapper(
name = "datatypes",
required = true,
nillable = false
@XmlElement(
name = "datatype",
required = false
public List<String> getDatatypes() {
if (_datatypes == null) {
_datatypes = new ArrayList<String>();
return _datatypes;
Any help would be greatly appreciated. Thanks.

I have been trying to do the same... and it seems to be impossible... (or completly undocumented).
It seems that OC4J 10.3.x is ... no exactly fully EJB3/J2EE5 compliant...
Or something like that:
http://blogs.infosupport.com/berte/archive/2005/09/09/1117.aspx
IMHO... OC4J 10.3.x is still a preview for OC4J 11...
OC4J 10.3.x is kind of a J2EE4/5 hybrid... if you start digging in the documentation, you will find out that the only
way to have WS-Security is going back to J2EE4 http://www.oracle.com/technology/products/jdev/howtos/1013/wssecure/10gwssecurity_howto.html
(of course, I hope you probe me wrong)
Message was edited by:
luxspes

EJB 3.0 web services security (WS-Security)

How do I enable WS-Security on EJB 3.0 based web services? Since only the @WebService annotation is required to expose a EJB 3.0 bean as a web service, how do I configure options that were previously in oracle-webservices.xml under the <security> tag?

I have been trying to do the same... and it seems to be impossible... (or completly undocumented).
It seems that OC4J 10.3.x is ... no exactly fully EJB3/J2EE5 compliant...
Or something like that:
http://blogs.infosupport.com/berte/archive/2005/09/09/1117.aspx
IMHO... OC4J 10.3.x is still a preview for OC4J 11...
OC4J 10.3.x is kind of a J2EE4/5 hybrid... if you start digging in the documentation, you will find out that the only
way to have WS-Security is going back to J2EE4 http://www.oracle.com/technology/products/jdev/howtos/1013/wssecure/10gwssecurity_howto.html
(of course, I hope you probe me wrong)
Message was edited by:
luxspes

Exposing EJB interfaces as Web Service

Similar Messages

Maybe you are looking for