On Jul 2, 2012, at 1:54 AM, Jean-Louis MONTEIRO wrote: > isn't that issue due to the changes you did before 1.0.0 final regarding > tomee.xml parsing without JaxB?
Good catch! Fixed TOMEE-267 -David > > JLouis > > 2012/7/2 Jonathan S. Fisher <[email protected]> > >> Clone URL (Committers only): >> >> https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openejb.apache.org/ejb-refs.mdtext >> >> Jonathan S. Fisher >> >> Index: trunk/content/ejb-refs.mdtext >> =================================================================== >> --- trunk/content/ejb-refs.mdtext (revision 1355837) >> +++ trunk/content/ejb-refs.mdtext (working copy) >> @@ -1,4 +1,6 @@ >> Title: EJB Refs >> + >> +TomEE complains it doesn't know the container type, so I added >> type="javax.naming.InitialContext" and it worked (mostly). >> <a name="EJBRefs-Referencingabeaninanotherjar(withannotations)"></a> >> ## Referencing a bean in another jar (with annotations) >> >> @@ -126,7 +128,7 @@ >> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> >> <openejb> >> >> - <JndiProvider id="shoe"> >> + <JndiProvider id="shoe" type="javax.naming.InitialContext"> >> java.naming.provider.url = ejbd://localhost:4201 >> java.naming.factory.initial = >> org.apache.openejb.client.RemoteInitialContextFactory >> </JndiProvider> >> @@ -157,7 +159,7 @@ >> >> If say, there are two servers that have the `OrangeBeanRemote` bean, you >> could expand the `<JndiProvider>` delcaration like so: >> >> - <JndiProvider id="shoe"> >> + <JndiProvider id="shoe" type="javax.naming.InitialContext"> >> java.naming.provider.url = failover:ejbd://192.168.1.20:4201 >> ,ejbd://192.168.1.30:4201 >> java.naming.factory.initial = >> org.apache.openejb.client.RemoteInitialContextFactory >> </JndiProvider> >> @@ -169,4 +171,3 @@ >> >> - [Multicast Discovery (UDP)](multicast-discovery.html) >> - [Multipoint Discovery (TCP)](multipoint-discovery.html) >> - >> >>
