[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1152) service-ref in ejb-jar.xml is ignored
Carlo de Wolf (JIRA)
jira-events at lists.jboss.org
Mon Sep 15 02:34:34 EDT 2008
[ https://jira.jboss.org/jira/browse/EJBTHREE-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlo de Wolf updated EJBTHREE-1152:
------------------------------------
Fix Version/s: 1.0.0-Beta4
(was: 1.0.0-Beta3)
> service-ref in ejb-jar.xml is ignored
> -------------------------------------
>
> Key: EJBTHREE-1152
> URL: https://jira.jboss.org/jira/browse/EJBTHREE-1152
> Project: EJB 3.0
> Issue Type: Bug
> Reporter: Thomas Diesler
> Assignee: Carlo de Wolf
> Fix For: 1.0.0-Beta4
>
>
> [tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase one-test
> one-test:
> [junit] Running org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase
> [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 8.761 sec
> [junit] Test org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase FAILED
> Caused by: javax.naming.NameNotFoundException: service1 not bound
> at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
> at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
> at org.jnp.server.NamingServer.getObject(NamingServer.java:556)
> at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
> at org.jnp.server.NamingServer.lookup(NamingServer.java:270)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:776)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
> at javax.naming.InitialContext.lookup(InitialContext.java:351)
> at org.jboss.test.ws.jaxws.samples.serviceref.EJBClient.echo(EJBClient.java:52)
> <ejb-jar version="3.0"
> xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
> <enterprise-beans>
> <session>
> <ejb-name>EJBClient</ejb-name>
> <remote>org.jboss.test.ws.jaxws.samples.serviceref.EJBRemote</remote>
> <ejb-class>org.jboss.test.ws.jaxws.samples.serviceref.EJBClient</ejb-class>
> <session-type>Stateless</session-type>
> <transaction-type>Container</transaction-type>
>
> <service-ref>
> <service-ref-name>service1</service-ref-name>
> <service-interface>javax.xml.ws.Service</service-interface>
> <wsdl-file>META-INF/wsdl/TestEndpoint.wsdl</wsdl-file>
> <service-qname xmlns:ns1="http://serviceref.samples.jaxws.ws.test.jboss.org/">ns1:TestEndpointService</service-qname>
> </service-ref>
>
> <service-ref>
> <service-ref-name>service2</service-ref-name>
> <service-interface>org.jboss.test.ws.jaxws.samples.serviceref.TestEndpointService</service-interface>
> <wsdl-file>META-INF/wsdl/TestEndpoint.wsdl</wsdl-file>
> <service-qname xmlns:ns1="http://serviceref.samples.jaxws.ws.test.jboss.org/">ns1:TestEndpointService</service-qname>
> <port-component-ref>
> <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.serviceref.TestEndpoint</service-endpoint-interface>
> <enable-mtom>true</enable-mtom>
> </port-component-ref>
> </service-ref>
>
> </session>
> </enterprise-beans>
>
> </ejb-jar>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list