Problems accessing fields in a CMP entity bean from a session bean

Hello everybody,
I'm getting the next problem: when I try to access a field in a CMP entity bean that I have instantiated from a session bean (trhoug entitybean.getNameOfField), I get the error "the entity bean does not exist in the database".
This entity bean is accessing a table in an external database (not the DB of the WAS), but I know that it's getting the correct data from the table, since I check the entitybean.size() and the entitybean.findByPrimaryKey(), and I get the right information. For some reason, the only thing that it doesn't work in the entity bean are the getter/setter methods (I created them automatically after having created the entity fields).
I access the entity bean through its local interface...
I know it's really difficult to give an answer with so few details, but... does anybody think I forgot something important to configure??
Thank very much in advance!!
Isidro

getter and setter methods for cmp-fields are abstract.
getter and setter methods for cmr-fields are abstract.
"John Lee" <[email protected]> wrote:
>
Hi:
Which method in a CMP Entity bean should be abstract? just only SetXXX
and
GetXXX?
Thanks!
John Lee

Similar Messages

Do JNDI look up for entity beans from a session bean in different jars

I have a problem doing entity beans JNDI look up from a session bean which is deployed
as a separate package (session.jar) from the entity beans (entity.jar)
I believe if both session bean and entity beans are deployed into one jar and
I specify ejb-local-reference-description for session bean, it should work. However,
due to some reason, they have to be in separated packages but still in the same
container. Then question how to do JNDI lookup given entity beans only have local
interfaces?
FYI.
1 both session.jar and entity.jar are self-contained. i.e., no deployment error.
each JNDI name can be viewed from JNDI tree
2. weblogic-ejb-jar.xml for session.jar
<weblogic-ejb-jar>
<description><![CDATA[Generated by XDoclet]]></description>
<weblogic-enterprise-bean>
<ejb-name>PetstoreLogic</ejb-name>
<stateless-session-descriptor>
</stateless-session-descriptor>
<reference-descriptor>
</reference-descriptor>
<jndi-name>PetstoreLogic</jndi-name>
<local-jndi-name>PetstoreLogicLocal</local-jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
3. weblogic-ejb-jar.xml (code snip) for entity.jar
<weblogic-enterprise-bean>
<ejb-name>Account</ejb-name>
<entity-descriptor>
<persistence>
<persistence-type>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-type>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
</persistence-use>
</persistence>
</entity-descriptor>
<reference-descriptor>
</reference-descriptor>
<local-jndi-name>net.sourceforge.cpetstore/AccountLocalHome</local-jndi-name>
</weblogic-enterprise-bean>
4. if I do
accountLocalHome = (AccountLocalHome) ic.lookup("net/sourceforge/cpetstore/AccountLocalHome");
get error like:
javax.naming.LinkException: . Root exception is javax.naming.NameNotFoundException:
While trying to look up /app/ejb/net.sourceforge.cpetstore-entity.jar#Account/local-home
in /app/ejb/cpetstore-ejb.jar#PetstoreLogic.; remaining name '/app/ejb/net/sourceforge/cpetstore-entity/jar#Account/local-home'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:869)
     at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:150)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)

In weblogic-ejb-jar.xml use jndi-name instead of local-jndi-name in reference-descriptor
element.
"Qiming He" <[email protected]> wrote:
>
I have a problem doing entity beans JNDI look up from a session bean
which is deployed
as a separate package (session.jar) from the entity beans (entity.jar)
I believe if both session bean and entity beans are deployed into one
jar and
I specify ejb-local-reference-description for session bean, it should
work. However,
due to some reason, they have to be in separated packages but still in
the same
container. Then question how to do JNDI lookup given entity beans only
have local
interfaces?
FYI.
1 both session.jar and entity.jar are self-contained. i.e., no deployment
error.
each JNDI name can be viewed from JNDI tree
2. weblogic-ejb-jar.xml for session.jar
<weblogic-ejb-jar>
<description><![CDATA[Generated by XDoclet]]></description>
<weblogic-enterprise-bean>
<ejb-name>PetstoreLogic</ejb-name>
<stateless-session-descriptor>
</stateless-session-descriptor>
<reference-descriptor>
</reference-descriptor>
<jndi-name>PetstoreLogic</jndi-name>
<local-jndi-name>PetstoreLogicLocal</local-jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
3. weblogic-ejb-jar.xml (code snip) for entity.jar
<weblogic-enterprise-bean>
<ejb-name>Account</ejb-name>
<entity-descriptor>
<persistence>
<persistence-type>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-type>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
</persistence-use>
</persistence>
</entity-descriptor>
<reference-descriptor>
</reference-descriptor>
<local-jndi-name>net.sourceforge.cpetstore/AccountLocalHome</local-jndi-name>
</weblogic-enterprise-bean>
4. if I do
accountLocalHome = (AccountLocalHome) ic.lookup("net/sourceforge/cpetstore/AccountLocalHome");
get error like:
javax.naming.LinkException: . Root exception is javax.naming.NameNotFoundException:
While trying to look up /app/ejb/net.sourceforge.cpetstore-entity.jar#Account/local-home
in /app/ejb/cpetstore-ejb.jar#PetstoreLogic.; remaining name '/app/ejb/net/sourceforge/cpetstore-entity/jar#Account/local-home'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:869)
     at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:150)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)

Using a CMP Entity Bean local stub as a field of another CMP Entity Bean

Hello,
Is it possible to implement a field of a CMP Entity bean as another CMP Entity bean and how is it done?
I've seen a pseudo code for this in Ed Roman's Mastering EJBs, second edition, but I can't seem to get it to work (pages: 330 - 1:1 using CMP and 339 - fake M:N using CMP).
I'm using SUN ONE Application Sever 7. Is this server capable of this?
I'm trying to implement a fake M:N relationship using 3 beans: 2 for each side of the relationship and one as the "bridge" table.
For example, the two beans on each side of the relationship are SubscriberBean, SubscriptionBean and the "bridge: bean is SubscriberSubscriptionBean. The SubscriberSubscriptionBean has two fields: SubscriberLocal stub and SubscriptionLocal stub.
Please let me know if you need more information to answer this question.
Thanks.
Nikola

Im sorry but i dont know about the example you are talking about. I kinda learn
all those techniques from forums, articles and tutorials because book often suffer from
not having the information im mostly looking for.
As far as i understand you, you want to implement a bridge been, which is representing a row in a join table. So that if one side of the relation is deleted the join-table entry (your bridge-CMP-Bean) is cascaded. Right?
First of all the simple part: (My approach)
- The joint table is foreign keys only - without a relation description. -
In this case you dont have to implement a bridge bean. Because it just wouldnt represent anything of sense.
Lets think of an entity/table USER whith the columns name (PRIMARY KEY), and prename.
Our second entity/table is ADDRESS with the columns road (PRIMARY KEY) and housenr.
The join table is simply: USER_ADDRESS with fk_name (FOREIGN KEY) and fk_road (FOREIGN KEY) both on CASCADE DELETE. So if the address is deleted the mapping entry is deleted, too same for the user part:
USER -> USER_ADDRESS <- ADDRESS.
Our entity Beans are called User and Address in class-names JNDI-names and names.
Now we want to create the CMR mapping so we can access the addresses of a user from the user bean directly. The methods on the user side are:
public abstract Collection getAddresses();
and
public abstract void setAddresses(Collection new_addresses);
the xdoclet comments on the User side are (for the getter only)
* @ejb.interface-method
* @ejb.relation
*                name = "User-has-Addresses"
*                role-name = "User-Addresses"
*                target-ejb = "Address"
*                target-multiple = "true"
* @sunone.relation
*                column="USER_ADDRESS.fk_name"
*                target="USER_ADDRESS.fk_road"
public abstract Collection getAddresses();
for the other side of the relation we define in the Address-Entity
public abstract Collection getUsers();
and
public void setUsers(Collection users);
the xdoclet comments on the Address side are (for the getter only)
* @ejb.interface-method
* @ejb.relation
*                name = "User-has-Addresses"
*                role-name = "Address-User"
*                target-ejb = "User"
*                target-multiple = "true"
* @sunone.relation
*                target="USER_ADDRESS.fk_road"
*                column="USER_ADDRESS.fk_name"
As we dont want the user or address to be deleted if the other side of the relation is deleted we dont specify cascade-delete="yes" in the ejb.relation namespace.
The sun-cmp-mappings.xml should now look like this:
(For the User - side)

<cmr-field-mapping>
<cmr-field-name>addresses</cmr-field-name>
<column-pair>
<column-name>USER_ADDRESS.fk_name</column-name>
<column-name>USER_ADDRESS.fk_road</column-name>
</column-pair>
</cmr-field-mapping>
and similar on the Address-Side:
<cmr-field-mapping>
<cmr-field-name>users</cmr-field-name>
<column-pair>
<column-name>USER_ADDRESS.fk_road</column-name>
<column-name>USER_ADDRESS.fk_name>/column-name>
</column-pair>
</cmr-field-mapping>
Dont forget that all elements in the Collection must be of the right Interface-type.
First of all the harder part:
Now what you might want is when the relation has some information specified like user live at address and is tenant or facility manager.
The, in the first step you will have to implement the UserAddressRelation entity which will have to CMR fields of the 1:N type.(Just as you wish)
Lets think of the example above extended by the relation type. Our relation bean is named UserAddressRelation.
Now User has the methods as above but the classes in the Collection must now be of the UserAddressRelationLocal/Remote interface and not AddressLocal/Remote-interface.
You will have to change the xdoclet comment to:
* @ejb.interface-method
* @ejb.relation
*                name = "User-has-Addresses"
*                role-name = "User-Address"
*                target-ejb = "UserAddressRelation"
*                target-multiple = "true"
* @sunone.relation
*                target="USER_ADDRESS.fk_name"
*                column="USER.name"
So we now dont reference the other side bean directly. We reference the relation EntityBean. Do the similar changes on the other side.
In particular you will have to specify 4 CMR mappings now:
1. User to UserAddressRelation 1:N
2. UserAddressRelation N:1
3. Address to UserAddressRelation 1:N
4. UserAddressRelation N:1
Which i dont want to explain in detail now because its kinda all the same as above.
Now you cann access the Addresses of a user in the way.
UserLocal.getAddresses(); <- !you get the mappings!
UserLocal.getAddresses().item(0).getAddress() <- you get the address (this is dirty coding just for understanding)
UserLocal.getAddresses().item(0).getUserRole() <. you get the role of the user at this address.
Hope this helped you. You are welcome to ask any detailed question.

How to get access via RMI from a session bean to a remote session bean?

I have 2 J2EE applications in two different Sun Application Servers (8.0 PE). I would like to get access from one Session Bean "SB1" into Application A to Session Bean "BrickFacade" within Application B.
My Java Code from "SB1":
         Context ic = new InitialContext();
         Object o = ic.lookup("java:comp/env/ejb/BrickFacade");
         BrickFacadeHome brickFacadeHome2 = (BrickFacadeHome) PortableRemoteObject.narrow(o, BrickFacadeHome.class);
         brickFacade = brickFacadeHome2.create();
         Collection col = brickFacade.doSomething();
         ...I configured the remote App.server in sun-ejb-jar.xml. I found the syntax within documentation (http://docs.sun.com/source/817-6087/dgjndi.html#wp24622) but I'm not sure if I this is the right usage.
     <ejb-ref>
        <ejb-ref-name>ejb/BrickFacade</ejb-ref-name>
        <jndi-name>corbaname:iiop://161.90.176.213:3700#webclient/BrickFacade</jndi-name>
      </ejb-ref>The context lookup throws the exception:
"IOP00110603: (BAD_PARAM) Bad host address in -ORBInitDef"
and
Invalid URL or IOR: corbaloc:iiop://161.90.176.213:3700
javax.naming.ConfigurationException: Invalid URL or IOR: corbaloc:iiop://161.90.176.213:3700 [Root exception is org.omg.CORBA.BAD_PARAM:   vmcid: SUN minor code: 603 completed: No]
Could anyone help me? Many thanks!
Stacktrace:
"IOP00110603: (BAD_PARAM) Bad host address in -ORBInitDef"
org.omg.CORBA.BAD_PARAM: vmcid: SUN minor code: 603 completed: No
     at com.sun.corba.ee.impl.logging.NamingSystemException.insBadAddress(NamingSystemException.java:148)
     at com.sun.corba.ee.impl.logging.NamingSystemException.insBadAddress(NamingSystemException.java:166)
     at com.sun.corba.ee.impl.naming.namingutil.CorbalocURL.badAddress(CorbalocURL.java:104)
     at com.sun.corba.ee.impl.naming.namingutil.CorbalocURL.handleColon(CorbalocURL.java:140)
     at com.sun.corba.ee.impl.naming.namingutil.CorbalocURL.handleIIOPColon(CorbalocURL.java:115)
     at com.sun.corba.ee.impl.naming.namingutil.CorbalocURL.<init>(CorbalocURL.java:67)
     at com.sun.corba.ee.impl.naming.namingutil.INSURLHandler.parseURL(INSURLHandler.java:41)
     at com.sun.corba.ee.impl.resolver.INSURLOperationImpl.operate(INSURLOperationImpl.java:103)
     at com.sun.corba.ee.impl.orb.ORBImpl.string_to_object(ORBImpl.java:774)
     at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:338)
     at com.sun.jndi.cosnaming.CNCtx.initUsingCorbanameUrl(CNCtx.java:321)
     at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:247)
     at com.sun.jndi.cosnaming.CNCtx.createUsingURL(CNCtx.java:85)
     at com.sun.jndi.url.iiop.iiopURLContextFactory.getUsingURLIgnoreRest(iiopURLContextFactory.java:56)
     at com.sun.jndi.url.iiop.iiopURLContext.getRootURLContext(iiopURLContext.java:44)
     at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:182)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.java:702)
     at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:108)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at de.emilberlinerstudios.va.ejb.testrh.sb.TestRemoteEjbBean.getBrickFacade(TestRemoteEjbBean.java:108)
     at de.emilberlinerstudios.va.ejb.testrh.sb.TestRemoteEjbBean.startTest(TestRemoteEjbBean.java:79)
     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:324)
     at com.sun.enterprise.security.SecurityUtil$2.run(SecurityUtil.java:146)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.security.application.EJBSecurityManager.doAsPrivileged(EJBSecurityManager.java:930)
     at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:151)
     at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:128)
     at $Proxy7.startTest(Unknown Source)
     at de.emilberlinerstudios.va.ejb.testrh.sb._TestRemoteEjb_Stub.startTest(Unknown Source)
     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:324)
     at com.sun.forte4j.j2ee.ejbtest.webtest.InvocableMethod$MethodIM.invoke(InvocableMethod.java:231)
     at com.sun.forte4j.j2ee.ejbtest.webtest.EjbInvoker.getInvocationResults(EjbInvoker.java:96)
     at com.sun.forte4j.j2ee.ejbtest.webtest.DispatchHelper.getForward(DispatchHelper.java:189)
     at org.apache.jsp.dispatch_jsp._jspService(dispatch_jsp.java:75)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:102)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:282)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:263)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:210)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     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:324)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:214)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:168)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:272)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:114)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:936)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
     at java.lang.Thread.run(Thread.java:534)
|#]
[#|2006-10-02T13:52:55.390+0200|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.out|_ThreadID=11;|2006-10-02 13:52:55 [8080-Processor4] INFO .va.ejb.testrh.sb.TestRemoteEjbBean - RemoteException when getting BrickFacade. Message:Invalid URL or IOR: corbaloc:iiop://161.90.176.213:3700
javax.naming.ConfigurationException: Invalid URL or IOR: corbaloc:iiop://161.90.176.213:3700 [Root exception is org.omg.CORBA.BAD_PARAM:   vmcid: SUN minor code: 603 completed: No]
     at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:367)
     at com.sun.jndi.cosnaming.CNCtx.initUsingCorbanameUrl(CNCtx.java:321)
     at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:247)
     at com.sun.jndi.cosnaming.CNCtx.createUsingURL(CNCtx.java:85)
     at com.sun.jndi.url.iiop.iiopURLContextFactory.getUsingURLIgnoreRest(iiopURLContextFactory.java:56)
     at com.sun.jndi.url.iiop.iiopURLContext.getRootURLContext(iiopURLContext.java:44)
     at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:182)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.java:702)
     at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:108)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at de.emilberlinerstudios.va.ejb.testrh.sb.TestRemoteEjbBean.getBrickFacade(TestRemoteEjbBean.java:108)
     at de.emilberlinerstudios.va.ejb.testrh.sb.TestRemoteEjbBean.startTest(TestRemoteEjbBean.java:79)
     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:324)
     at com.sun.enterprise.security.SecurityUtil$2.run(SecurityUtil.java:146)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.security.application.EJBSecurityManager.doAsPrivileged(EJBSecurityManager.java:930)
     at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:151)
     at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:128)
     at $Proxy7.startTest(Unknown Source)
     at de.emilberlinerstudios.va.ejb.testrh.sb._TestRemoteEjb_Stub.startTest(Unknown Source)
     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:324)
     at com.sun.forte4j.j2ee.ejbtest.webtest.InvocableMethod$MethodIM.invoke(InvocableMethod.java:231)
     at com.sun.forte4j.j2ee.ejbtest.webtest.EjbInvoker.getInvocationResults(EjbInvoker.java:96)
     at com.sun.forte4j.j2ee.ejbtest.webtest.DispatchHelper.getForward(DispatchHelper.java:189)
     at org.apache.jsp.dispatch_jsp._jspService(dispatch_jsp.java:75)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:102)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:282)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:263)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:210)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     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:324)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:214)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:168)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:272)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:114)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:936)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
     at java.lang.Thread.run(Thread.java:534)
Caused by: org.omg.CORBA.BAD_PARAM: vmcid: SUN minor code: 603 completed: No
     at com.sun.corba.ee.impl.logging.NamingSystemException.insBadAddress(NamingSystemException.java:148)
     at com.sun.corba.ee.impl.logging.NamingSystemException.insBadAddress(NamingSystemException.java:166)
     at com.sun.corba.ee.impl.naming.namingutil.CorbalocURL.badAddress(CorbalocURL.java:104)
     at com.sun.corba.ee.impl.naming.namingutil.CorbalocURL.handleColon(CorbalocURL.java:140)
     at com.sun.corba.ee.impl.naming.namingutil.CorbalocURL.handleIIOPColon(CorbalocURL.java:115)
     at com.sun.corba.ee.impl.naming.namingutil.CorbalocURL.<init>(CorbalocURL.java:67)
     at com.sun.corba.ee.impl.naming.namingutil.INSURLHandler.parseURL(INSURLHandler.java:41)
     at com.sun.corba.ee.impl.resolver.INSURLOperationImpl.operate(INSURLOperationImpl.java:103)
     at com.sun.corba.ee.impl.orb.ORBImpl.string_to_object(ORBImpl.java:774)
     at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.j|#]

Problem solved:
configuration in jndi-name was wrong:
<jndi-name>corbaname:iiop:161.90.176.213:3700#ejb/BrickFacade</jndi-name>

A question about entity manager in stateless session bean.

JSR 220 ejbcore, page 47 : stateless session bean: All business object references of the same interface type for the same stateless session bean have the "same object identity", which is assigned by the container.
So, if we have two session beans in client code...
@EJB Cart cart1;
@EJB Cart cart2;
then cart1.equals(cart2)==true
If we declare entity manager in stateless session bean:
@PersistenceContext( unitName="ds" ,type=PersistenceContextType.TRANSACTION)
private EntityManager em;If cart1 and cart2 are the same reference, do we have any problem when using the same reference(maybe the same em? ) to get data from db?

If cart1 and cart2 are the same reference, do we have
any problem when using the same reference(maybe the
same em? ) to get data from db?No. In EJB, there is a distinction between the EJB reference and the bean instance.
Each time you make an invocation on an EJB reference for a stateless session bean,
the container can choose any instance of that bean's bean class to process the
invocation. That's true whether you invoke the same reference multiple times or
two difference references to the same bean.
Each bean instance is guaranteed to be single-threaded.

Error while calling a Web Service from a Session Bean

I am trying to call a Web Service from a Session Bean using an Axis client, but I am getting the next exception:
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
     java.rmi.RemoteException: org/apache/axis/client/Service
     at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.wrapException(Util.java:364)
     at javax.rmi.CORBA.Util.wrapException(Util.java:277)
     at com.ing.mx.seguros.siniestros.litigios.ejb._SisaServiceRemote_Stub.invocarWebSericeProveedorLegal(Unknown Source)
     at com.ing.mx.seguros.siniestros.litigios.proxy.SisaWsProxy.solicitarApoyoLegal(SisaWsProxy.java:132)
     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:324)
     at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:402)
     at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:309)
     at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:333)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
     at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:481)
     at org.apache.axis.server.AxisServer.invoke(AxisServer.java:323)
     at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:854)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:339)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
     at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
     at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
     at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:158)
     at com.iplanet.ias.web.WebContainer.service(WebContainer.java:850)Thanks for any help provided.
Does any one have insights about it?

Hi Swapna,
from your screenshot it seems that you actually try to call the service in your Data Source Expression field. You should set path to the WSDL file here actually - this could be either URL to SAP or to filesystem, as Anton suggested (this could be faster). Have you created endpoint binding for your service in transaction SOAMANAGER? If yes, then simply download the corresponding WSDL with binding or copy the URL which leads to it. But also test whether you are able to retrieve the WSDL without logging into SAP (close all browser windows and then open a new one otherwise session ID from other browser windows can be reused).
If you have to give username and password, then setup anonymous alias in transaction SICF, for example.
Pleas, check my previous post on the same subject here: Re: BCM7 IVR : SOAP request for client identification in CRM .
Maybe it could help.
Regards,
Dawood.

Web Service from stateful Session Bean deleted after server restart

Hi,
i created a stateful session bean and from this a web service.
I am able to deploy it and it works really fine.
My problem is: after a server restart the web service is gone and i
have to deploy it again.
I have some other web services (but these are web services from stateless session beans)
but they "survive" the server restart.
I don't want to deploy the web service after every server restart, did I forget something or
is it a general problem of stateful session beans or web services?
Thanks in advance
Jens

Hello Björn,
I am not quite sure what your problem is but did you have a look at these articles:
http://help.sap.com/saphelp_nw04/helpdata/en/4d/993441c73cef23e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/be/2e2c4142aef623e10000000a155106/frameset.htm
I hope they can give you some idea.
Regads
Vyara

Parsing XML from a session bean

Hi,
I am trying to use a Sax parser for parsing xml received from a back end
legacy system. The code is executed from a Session bean.
Debugging learned me that the parse() method on the parser hangs the
container without any error or exception trace. The code works fine outside
a container.
All help will be highly appreciated.
Kurt

I found out that the InputStream implementation used parsing source inside
the container is different
then from the one outside (other type of VM of course!). The Weblogic
implementation blocks at the end of
the stream, while the normal SUN JDK 1.3 returns. This is not a bug, the bug
I found is in my proxy that allows
the connection to the backend. This proxy allows HTTP connections, and I
parse the XML received over HTTP.
Regards,
Kurt
"Todd Karakashian" <[email protected]> wrote in message
news:[email protected]..
That's seems odd. Perhaps there is something going on in your document
handler code that triggers a hang in the environment of the server.
When you see the hang, instruct the VM to give you a thread dump (type
control-<break> on Windows, <control>-\ (backslash) on UNIX in the
window in which the server is running; the results are dumped to
stderr). That will show what every thread in the server is doing. If you
email or post the thread dump, I will take a look at it and see if I can
see what is going on. Also, let us know which platform, VM, parser, and
WebLogic version you are using.
Regards,
-Todd
Kurt Quirijnen wrote:
Hi,
I am trying to use a Sax parser for parsing xml received from a back end
legacy system. The code is executed from a Session bean.
Debugging learned me that the parse() method on the parser hangs the
container without any error or exception trace. The code works fine
outside
a container.
All help will be highly appreciated.
Kurt--
Todd Karakashian
BEA Systems, Inc.
[email protected]

Calling an RPG (AS400) program from a Session Bean

Hi, does anyone know if there is a kind of connector that makes possbile to call an RPG program in an AS400 host from a session bean, allowing the application server (i.e. : JBoss or WAS or WLB) to maintain the transaction ?
Thanks,
Klaus Koenig
Italy

Yes, it is called "AS/400 Toolbox for Java".

Error when returning Vector from EJB Session Bean

I am testing the EJB functionality within JDeveloper(9.0.3). I simply expanded on the tutorial that is in the documentation (departments and employees). I created a method in the stateless session bean that retrieves a Collection of employees for a department, then converts it to a Vector. When I try to return the Vector from the session bean to a sample client, I get an error indicating that the Object is NOT serializable. I know that Vector IS serializable. Why do I get this error? (The error displays on the client message log, NOT the OC4J message log). I tried dumping the Vector to System.out.println - this works fine, so I l know I'm getting data.
Here is the stack trace and errors that display:
com.evermind.server.rmi.OrionRemoteException: Error (de-)serializing object: EmployeeLocal_EntityBeanWrapper4
     java.lang.Object com.evermind.server.ejb.EJBUtils.cloneSerialize(java.lang.Object, com.evermind.server.ejb.AbstractEJBHome)
          EJBUtils.java:404
     java.lang.Object com.evermind.server.ejb.EJBUtils.cloneObject(java.lang.Object, com.evermind.server.ejb.AbstractEJBHome)
          EJBUtils.java:377
     java.lang.Object com.evermind.server.ejb.EJBUtils.cloneOneObjectInstance(java.lang.Object, com.evermind.server.ejb.AbstractEJBHome)
          EJBUtils.java:419
     java.lang.Object com.evermind.server.ejb.EJBUtils.cloneArrayList(java.util.ArrayList, com.evermind.server.ejb.AbstractEJBHome)
          EJBUtils.java:599
     java.lang.Object com.evermind.server.ejb.EJBUtils.cloneObject(java.lang.Object, com.evermind.server.ejb.AbstractEJBHome)
          EJBUtils.java:357
     java.util.Collection hrApp_StatelessSessionBeanWrapper2.getEmployeesByDepartment(java.lang.Long)
          hrApp_StatelessSessionBeanWrapper2.java:323
     java.lang.Object java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[])
          native code
     void com.evermind.server.rmi.RMICallHandler.run(java.lang.Thread)
          RMICallHandler.java:119
     void com.evermind.server.rmi.RMICallHandler.run()
          RMICallHandler.java:48
     void EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run()
          PooledExecutor.java:803
     void java.lang.Thread.run()
          Thread.java:484
at connection to localhost/127.0.0.1 as admin
     void com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(java.lang.Throwable)
          RMIConnection.java:1558
     java.lang.Object com.evermind.server.rmi.RMIConnection.invokeMethod(com.evermind.server.rmi.RMIContext, long, long, java.lang.reflect.Method, java.lang.Object[])
          RMIConnection.java:1511
     java.lang.Object com.evermind.server.rmi.RemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
          RemoteInvocationHandler.java:53
     java.lang.Object com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
          RecoverableRemoteInvocationHandler.java:22
     java.lang.Object com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
          StatelessSessionRemoteInvocationHandler.java:50
     java.util.Collection __Proxy1.getEmployeesByDepartment(java.lang.Long)
     javax.swing.table.DefaultTableModel hr.hrAppClientFrame.getTableModel()
          hrAppClientFrame.java:150
     void hr.hrAppClientFrame.jbInit()
          hrAppClientFrame.java:122
     void hr.hrAppClientFrame.<init>()
          hrAppClientFrame.java:58
     void hr.hrAppClientFrame.main(java.lang.String[])
          hrAppClientFrame.java:141
     Nested exception is:
java.io.NotSerializableException: EmployeeLocal_EntityBeanWrapper4
     void java.io.ObjectOutputStream.outputObject(java.lang.Object)
          ObjectOutputStream.java:1148
     void java.io.ObjectOutputStream.writeObject(java.lang.Object)
          ObjectOutputStream.java:366
     java.lang.Object com.evermind.server.ejb.EJBUtils.cloneSerialize(java.lang.Object, com.evermind.server.ejb.AbstractEJBHome)
          EJBUtils.java:390
     java.lang.Object com.evermind.server.ejb.EJBUtils.cloneObject(java.lang.Object, com.evermind.server.ejb.AbstractEJBHome)
          EJBUtils.java:377
     java.lang.Object com.evermind.server.ejb.EJBUtils.cloneOneObjectInstance(java.lang.Object, com.evermind.server.ejb.AbstractEJBHome)
          EJBUtils.java:419
     java.lang.Object com.evermind.server.ejb.EJBUtils.cloneArrayList(java.util.ArrayList, com.evermind.server.ejb.AbstractEJBHome)
          EJBUtils.java:599
     java.lang.Object com.evermind.server.ejb.EJBUtils.cloneObject(java.lang.Object, com.evermind.server.ejb.AbstractEJBHome)
          EJBUtils.java:357
     java.util.Collection hrApp_StatelessSessionBeanWrapper2.getEmployeesByDepartment(java.lang.Long)
          hrApp_StatelessSessionBeanWrapper2.java:323
     java.lang.Object java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[])
          native code
     void com.evermind.server.rmi.RMICallHandler.run(java.lang.Thread)
          RMICallHandler.java:119
     void com.evermind.server.rmi.RMICallHandler.run()
          RMICallHandler.java:48
     void EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run()
          PooledExecutor.java:803
     void java.lang.Thread.run()
          Thread.java:484
at connection to localhost/127.0.0.1
     void com.evermind.server.rmi.OrionRemoteException.receive(java.net.InetAddress, java.lang.String)
          OrionRemoteException.java:130
     void com.evermind.server.rmi.RMIConnection.handleMethodInvocationResponse()
          RMIConnection.java:1673
     void com.evermind.server.rmi.RMIConnection.run(java.lang.Thread)
          RMIConnection.java:532
     void com.evermind.server.rmi.RMIConnection.run()
          RMIConnection.java:275
     void EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run()
          PooledExecutor.java:797
     void java.lang.Thread.run()
          Thread.java:484
Any ideas?
Thanks

I would suggest opening a case with [email protected] FWIW, I recall seeing
          something like this in WLS 6.0. I believe it is fixed in WLS 6.1
          -- Rob
          Chris Dupuy wrote:
          > Btw, this occurs when I create an stateful session bean that ends up
          > throwing an exception and setRollbackOnly() is called. From that point
          > forward, my logs fill with this message.
          >
          > Chris
          >
          > "Chris Dupuy" <[email protected]> wrote in message
          > news:[email protected]..
          > > anyone know what this means, and what you can do about it?
          > >
          > >
          > > <Error> <ConnectionManager> <atossd03> <cbeyondServer> <ExecuteThread:
          > '14'
          > > for queue: 'd
          > > efault'> <> <> <000000> <Closing:
          > 'weblogic.rjvm.t3.T3JVMConnection@488831'
          > > because of: 'Server received a message over an uniniti
          > > alized connection: 'JVMMessage from: 'null' to:
          > >
          > '5825313123619479267S:10.6.6.40:[8000,8000,8001,8001,8000,8001,-1]:cbeyond:c
          > > beyond
          > > Server' cmd: 'CMD_REQUEST', QOS: '101', responseId: '2', invokableId: '1',
          > > flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev o
          > > ffset: '204'''>
          > >
          > >
          > >

Problem when trying to delete CMP entity bean

Hi,
When I try to remove a CMP entity bean, I have this error :
re09.projet_ejb.syndic.AdminException: Exception thrown from bean; nested exception is: javax.ejb.EJBException: nested exception is: com.sun.jdo.api.persistence.support.JDOUnsupportedOptionException: JDO76207: Update of a primary key field is not allowed.It's only happening when I try to remove a bean which has a relation with another bean. The relation type is One to Many. I tried to search on this forum to find an answer but I found nothing that could help me.
Message was edited by:
Starship
Sry I just found the mistake, the cascade delete was not on the right place :s
Message was edited by:
Starship

Got it sorted so I thought I would share the solution here: The problem wasnt related to LR 5.2 but was to do with Mac OS X 10.8.5 AKA Mountain Lion. I had also noticed that I was having an issue around deleting anything on my MAC. When I tried to delete a file from anywhere I was asked to submit my password. The message I got was finder wants to make a change please submit password. I checked through the mountain Lion forums and found a solution here; https://discussions.apple.com/message/20499360#20499360%2320499360
I implemented it and the problem has dissappeared.

JNDI Naming Problem accessing Session Bean from Message Driven Bean

Hi,
     I am facing a very strange problem in JNDI look up accessing a Session Bean from a Message Driven Bean. I have a session fa�ade bean(Remote Bean) which is being called from Struts Action class getting the home reference from the ServiceLocator (I have implemented ServiceLocator pattern to obtain JNDI reference for all EJBs). When I am calling the session fa�ade EJB from the Struts Action class everything is working fine.
     But when I am trying to call the same EJB from my Message Driven Bean, I am getting a JNDI exception (NameNotFoundException - No Object bound to name �java:comp/env/ejb/EJBJNDIName�). I am trying to get the remote reference from the same ServiceLocator which is successfully providing me a reference while calling from the struts action class. But the same ServiceLocator is not able to provide me a reference while calling from the Message Driven Bean. If I use the JNDI name directly like �EJBJNDIName� in the lookup it is working fine. The lookup for the name is working fine and I am able to call the Session Fa�ade bean with that reference.
     I am really not sure what exactly the problem is. If I have any problem in the ServiceLocator, it should have given me the same error while calling from Struts Action class. But it is working fine with the full name �java:comp/env/ejb/EJBJNDIName� calling from the struts action class. I am not sure whether Message Driven Bean has something to do with it. Why I am not able to get a reference of the EJB with the full name? Please Help.
Thanks
Amit

Hi Bhagya,
Thanks for your response. I think from EJB container we can call Local EJBs with the full JNDI name. The session facade bean which is being called is a remote bean. From the session facade bean I am calling a local stateless session bean for database access. I am getting the reference of the local EJB from my session facade bean with full JNDI name "java:comp/env/ejb/EJBJNDIName". It is working fine with out any problem. My servicelocator is able to provide me the reference of the local EJB from the session facade remote bean with Full JNDI name. I am only having this problem calling from the MDB. I am really not sure whether what is causing it?
Thanks
Amit

Problem with getting Entity Beans refreshed within Session bean methods

I hav following code in session and entity beans:
Session bean pseudo code: (PrimaryKey is primary key class for the entity
bean referred here, and MySessionHome is the home interfac class for this
session bean).
public class MySession implements SessionBean {
// This method is present in remote interface class as well.
public void methodA(PrimaryKey pk) {
// code to find entity bean by primary key specified.
update the entity bean, and mark it as isModified.
public void methodB(PrimaryKey pk) {
// code to find entity bean by primary key specified.
do something.
public void methodC() {
MySessionHome sessHome = code to lookup sessionhome from JNDI.
MySessionRI sess = sessHome.create(); // MySessionRI is the remote
interface class for MySession
PrimaryKey pk = new PrimaryKey(params);
sess.methodA(); // LINE ABC1
sess.methodB(); // LINE ABC2
all the entity and session bean methods have required as the TX attribute.
In methodB() on LINE ABC2, the entity bean obtained by findByPrimaryKey does
not reflect the changes made in call to methodA() on LINE ABC1.
Now if I change the LINE ABC1 and LINE ABC2 to
methodA(); // LINE ABC1
methodB(); // LINE ABC2
in this case the entity bean obtained in methodB() has the changes made in
methodA().
Any idea why this is happening?

Hi ad13217 and thanks for reply.
I'm sorry but my code is like this:
javax.naming.Context ctx=new javax.naming.InitialContext();
arguments was an error on copy, but it doesn't work.
Thanks
Fil

How to achieve Entity Bean methods ONLY by calling them from a Session Bean

Hi,
I used a session bean as a business facade to a entity bean.
In the session bean I achieve the entity bean with a jndiContext.lookup("java:comp/env/ejbEntityBean").
Now I am looking for a solution that it is only possible to call the entity bean methods or the whole entity bean from the corresponding session bean.
In other words: "How can I forbid the access to the entity bean, if the calling object is not the corresponding session bean?"
--->
I only found a way the regulate the access to the entity bean methods by declaring a security-role.
But the existence of the security-role at runtime depends on the calling user-authorizations!
Is there a way to set the entity-security-role within the session bean context?
Best Regards
Steffen

Hi Srikanth Reddy.T,
sorry, I am not looking for a special tag <entity-security-role>.
I am looking for a way to specifiy that my session bean "has" the special security-role (in my case "WebZaehlerEjbRole") of my entity bean "in my case "WebZaehlerEjbRole") that is necessary to call the methods (findAlleEntries, findByWindowId,...) of my entity-bean.
Here is the relevant part of my ejb-jar.ml:
     <assembly-descriptor>
          <security-role>
               <role-name>WebZaehlerEjbRole</role-name>
          </security-role>
          <method-permission>
               <description>method-permission</description>
               <role-name>WebZaehlerEjbRole</role-name>
               <method>
                    <ejb-name>WebZaehlerBean</ejb-name>
                    <method-name>findAllEntries</method-name>
                    <method-params/>
               </method>
               <method>
                    <ejb-name>WebZaehlerBean</ejb-name>
                    <method-name>findByWindowId</method-name>
                    <method-params>
                         <method-param>java.lang.Long</method-param>
                    </method-params>
               </method>
Regards,
Steffen

Problem with connecting from Netweaver Session Bean to SAP R/3

Hi,
i just want a connection to RFC in SAP R/3 and with help of sap ("Proxy generation" etc) and wizard in NWDS i get the rfc. Now i want to connect and use it (like in handbook) but: Every time i create and use jcoclient.connect() system gets an error like:
"Class File Editor
Source not found
The jar file jrfc.jar has no source attachment."
I have add all files that are used to "Used DCs" or bind library into projekt as "Third party library", but the error is still there.
Any idea? Do i have to make something else? Some failure made?
thx
Here is text for connection:
Created on 26.06.2008
To change the template for this generated file go to
Window>Preferences>Java>Code Generation>Code and Comments
package com.XXXXXXXXXXXXXXXXX;
import com.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX;
import com.sap.aii.proxy.framework.core.ApplicationFaultException;
import com.sap.aii.proxy.framework.core.SystemFaultException;
import com.sap.mw.jco.JCO;
@author XXXXX
To change the template for this generated type comment go to
Window>Preferences>Java>Code Generation>Code and Comments
public class MyMainClass extends Object
     public static void main(String[] args)
          throws ApplicationFaultException, SystemFaultException
          JCO.Client jcoclient =
               JCO.createClient(
                    "XXX", //Client
                    "XXX", //User
                    "XXX", //Password
                    "XXX", //Language
                    "XXX", //Server
                    "XXX", //System
                    "XXX"); //Group
          jcoclient.connect();
          jcoclient.disconnect();
Edited by: Torsten on Aug 27, 2008 10:43 AM
Where can we download SAP NW7.0 (2004s) as Java Trial for testing? We only find ABAP Trial... Link? thx

So we tested some things that are described in the SDN or by SAP with Connectors.
We tested JCO version 2.0.12, 2.1.18 and 3.0 in J2EE Projects in netweaver and in Eclipse (Standalone).
For version 2.0.12 there is a failure that this version is not compatible with the other things in netweaver.
This version is for standalone and integrated sytems.
For version 2.1.18 is only described as standalone and so failure happened in netweaver that other classes are coruppted or missed. The internal test in "content administrator" (Ping and Test) do not work and had the same error.
For version 3.0 (that displace the other two versions) there is many to do in settings and coding that we do not have tested yet because project is not that small to write it for JCO 3.0 only for testing. When we only displaced files in netweaver the server do not start any more.
So:
Is there a way to call R/3 from session bean and 1. create an JCO client or 2. add a client to the "standard" pool of netweaver to use it?
Any ideas? help? links?
Project have to be complete in september...
Our combi is SAP Netweaver 2004 SP21 on Windows XP SP2 / Server 2003 Standard SP1 with JVM 1.4.2_16... need of any more info?
thx

Problems accessing fields in a CMP entity bean from a session bean

Similar Messages

Maybe you are looking for