Calling Enity Bean's business methods from a session bean in EJB 3.0 specif

Hello everybody,
Happy to be a member with you in this forum.
This is my first participation in this forum.
I have some problem to start with EJB 3.0 specification, I have created an entity bean with some business methods that access a mysql datbase, then i want to create a stateful session bean to provide the client an interface to consume business methods in Enity be
Please can someone you help me with an example

@Vladimir Pavlov
I did not understand what you are trying to convey...
Whenever an attribute of this bean is modified we want to access that latest value.... Is there any way to know, when the attribute is modified? Just with get/set we can not know, when it is modified... am i right?
We want to achieve this without modifying the existing source code of the EJB....
@ Ivo Simeonov
As of my knowledge, to use interceptors we need to modify the EJB source code, but we do not want to touch the source code....
All this has to be achieved dynamically when the application is deployed in the production.... is it possible???

Similar Messages

Update object returned by a business method in stateful session bean

I have a business method in stateful session Bean returning an Object "myObject getObject()". This object can be modified by the client.
Is it necessary at the end to notify the bean about the changes with some kind of business method "setObject(Object myObject)"? or
the client and the bean have the same reference to the object and it isn't necessary?
Thanks

When an EJB returns a value, it is serialised across the wire and is effectively lost to the EJB. Any changes to the returned object by the client, will have to be notified by a call on the EJB, as in your post.
Dave

Can Entity Bean with Home Business Method replace Stateless Session Bean?

Since Entity Bean can have business methods in the Home Interface, can we use Entity Bean with Home Business Methods to replace Stateless Session Bean?
I am assuming we can get better performance by doing this since the overhead of creating Component Object can be avoided as compared to stateless session beans.

Requires-new makes the container start a new transaction. Only use that flag
          at the point that you are certain that a NEW transaction should BEGIN. I
          suggest you use Required as your default for all methods in the application,
          and only change that to anything else when you are certain that you should.
          Peace,
          Cameron Purdy
          Tangosol Inc.
          << Tangosol Server: How Weblogic applications are customized >>
          << Download now from http://www.tangosol.com/download.jsp >>
          "A.J,LEE" <[email protected]> wrote in message
          news:3ba5adb2$[email protected]..
          >
          > I find it result in "dead lock"
          > when I call RequiresNew attributed CMP method in session Bean.
          > Then, Is it possible to use CMP which is set with "RequiresNew"
          transaction attribute?
          >
          > I Wonder why.
          >
          > Thanx in advance.

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)

How to call a web service from a session bean's business method???

Hi Experts,
Can anybody help in calling a web serivce frm a session bean's business method??
Hw do we do that?
I have one requirement where i want to send emails to set of users for which i have email sending web service ready.. How can i call it thru a session bean's business method???
Pls help,
Regards,
Amey

Hi Amey,
You can achieve this using the followin 2 Step implementation:
1. [Creating a Deployable Proxy|http://help.sap.com/saphelp_nw70/helpdata/EN/2d/b9766df88f4a24967dae38cb672fe1/frameset.htm]
2. [Create a Client Bean|http://help.sap.com/saphelp_nw70/helpdata/EN/45/029840cf43495195da923f32262911/frameset.htm]
Hope it helps.
Regards,
Alka.

Calling session bean's business method through web dynpro component

Hi All,
Can anybody tell me how to call a session bean's methods through a web dynpro WITHOUT java-model or web service model ??
I have following scenario:-
1. Stateless Session bean having two business methods
2. Web Dynpro component
3.Now i want to call business methods without using any model. I have got following piece of code but I dont know how to go about it.
4.Where do i have to set JNDI name for session bean? which interface will be looked for?
5. Do I have to declare public part for EJB DC? If yes, how?
//This is inside web dynpro component
InitialContext context = new InitialContext();
o = context.lookup(JNDIName);
TestSessionbeanHome homeRef = (TestSessionbeanHome) PortableRemoteObject.narrow( o,
TestSessionbeanHome.class);
TestSessionbean beanRef = homeRef.create();
<returnValue> = beanRef.<ejb method name>
Please help to get a step-by-step approach to this case.
Thanks and regards,
Amey Mogare

Hi,
If I comment out the part that is using session bean's business method, DC is building fine.
And if I uncomment, then compiler is unabl eto resolve business method(s).
And i would like to mention that my EJB + J2EE App DC is building properly, but it havent yet deployed properly as I am waiting for data-source-alias name prefix to be configured by ERP team. So will this be a reason why Web Dynpro DC is not able to resolve business methods ??
Because Web Dynpro DC is able to resolved all interfaces of Session bean and entity bean. But when it comes to business method, its not able to resolve.
Any more ideas why it is not happening?
Pls help.
Now i went through some forum posts regarding this and found that we also need to add EJB DC to Java Build Path for WebDynproDC>Properties>Java Build Path.
I did this and now it is able to resolve business methods and DTOs as well. So to summarize I did following:-
1. Added EJB DC (complete DC) as a Used DC to Web Dynpro DC with Buid-n-Deploy-n-Run time dependency
2. Added Sharing reference of J2EE application DC to Web Dynpro DC -->Properties
This reference I constructed as follows:-
<vendorname>/<name of j2ee application as appearing under display name tag in application.xml (replacing '/' with '~')>
So my Sharing Reference becomes:- <vendorname>/reqpstapscreqpstapja_reqid
3. Added EJB DC to Java Build Path in Web Dynpro DC's properties
4. Then I added following piece of code to get object of SessionBean class
InitialContext context = new InitialContext();
Object o = context.lookup("java:comp/env/ejb/SessionRequestIDBean");
SessionRequestIDHome homeRef = (SessionRequestIDHome) PortableRemoteObject.narrow(o, SessionRequestIDHome.class);
SessionRequestID beanRef = homeRef.create();
beanRef.<business method>
But After doing this I am facing another problem :-
The build fails saying it is not able find the package for DTOs. But when I see the Component Controller's code it is not showing any red or yellow marks.
Can anybody pls help me out here?
Thanks and regards,
Amey Mogare

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.

Calling a css user created method from jspx page in ADF faces

Hi all,
Can anyone help me out to solve an issue calling a css user created method from a jspx page.
Note: The css method is not the default css method. It needs to be called using 'styleClass' attribute in any tag.
Thanks
Neha

Hi,
I am not an expert in CSS so I don't know what a css method is. However, CSS can be applied to components via EL accessing a managed bean that returns the sytle text
Frank

Can we call a method in stateless session bean ?

Can we call a method in stateless session bean in onMessage method?

Hi,
The purpose of service locator is to abstract the lookup of the server side services like ejb and DSNs. It should be a normal java class but as such there is no such restriction. You can have a look at the service locator patter at the j2ee blue prints.
/Ashwani

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".

How to call another view controller's method from a view controller?

Hi,
Iam new to webdynpro . so pls clarify my doubt.
How to call another view controller's method from a view controller in the same Web Dynpro Component?
Thanks,
Krishna

Hi,
     The methods in a view are only accessible inside same view. you cannot call it outside the view or
     in any other view although its in same component.
     If you want to have a method in both views, then create the method in component controller and
     from there you can access the method any where in whole component.

Error while adding a new method to the Session Bean

Hello everyone. I'm using jdev 11g, ejb, jpa & jsf. Everything works fine. But when I try to add a custom method to the Session Bean, I'm having an error.
Here is my steps:
1) I added a new method to SessionBean.java. Something like this:
public void Hello() {
System.out.println("Hello!");
2) Then using Structure palette I exposed this method through Local interface and created data control
3) Finally, I made a command button binded to this method (just droped it from DataControls.dcx to my page)
When I start the page and click the button, I'm having the following error:
Error 500--Internal Server Error
javax.faces.el.EvaluationException: Method not found: Hello.execute(javax.faces.event.ActionEvent)
     at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:58)
     at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1227)
     at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:70)
... (I've truncated the log because there is nothing important in the missing part)

Yes, I have binding in the page def. Everything is correct there:
<methodAction id="Hello" RequiresUpdateModel="true" Action="invokeMethod"
MethodName="Hello" IsViewObjectMethod="false"
DataControl="PriceServiceLocal"
InstanceName="PriceServiceLocal.dataProvider"/>
I've droped the method from the Data Controls panel

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

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>

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 Enity Bean's business methods from a session bean in EJB 3.0 specif

Similar Messages

Maybe you are looking for