Problem while developing stasteless session bean

Hi All,
I am learning Ejb,i developed a simple hello world application using statelesssession bean in weblogic server8.1.And i packed it in a jar file named slb.jar.
Then i am trying to create stub and skeleton using following command,but i am getting this error.can anybody please help me.
C:\nkmb\ejb\HelloEjb>java weblogic.ejbc slb.jar
<Jun 22, 2006 9:55:35 AM EDT> <Warning> <EJB> <BEA-010212> <The EJB 'HelloBean(J
ar: slb.jar)' contains at least one method without an explicit transaction attri
bute setting. The default transaction attribute of Supports will be used for the
following methods: remote[hello()] >
C:\nkmb\ejb\HelloEjb\ejbcgen\examples\HelloBean_gbyfgg_Impl.java:11: cannot a
ccess java.io.Serializable
bad class file: C:\Program Files\Java\jre1.5.0_06\lib\rt.jar(java/io/Serializabl
e.class)
class file has wrong version 49.0, should be 48.0
Please remove or make sure it appears in the correct subdirectory of the classpa
th.
public final class HelloBean_gbyfgg_Impl
^
1 error
Exec failed .. exiting
can anybody help me to getting out of this problem.
thanks inadvance,
nkmb

http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_solution&answerpage=solution&page=wlw/S-28139.htm

Similar Messages

Problem While calling a session bean (J2EE)

Hi!!
Please see my client-side code..where I am calling a session bean (J2EE Server)
It's correct or not?????
InitialContext ctx = new InitialContext();
Object objref = ctx.lookup("SecDbSecRoleJndi");
SecBusSecRoleHome home =(SecBusSecRoleHome)PortableRemoteObject.narrow(objref,SecBusSecRoleHome.class);
SecBusSecRoleRemote remote =(SecBusSecRoleRemote)PortableRemoteObject.narrow(home.create(),SecBusSecRoleRemote.class);
Here I am getting the error at 3rd line
java.lang.ClassCastException
at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:296)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:137)
at TestServlet.init(TestServlet.java:22)
Please do the favor to me..reply me back.
Bhumika

Hello,
Hope you are bale to sole the problem by this time. Iam using the follwing code and its working fine for me. i'm using the weblogic application server.
<%@ page import="javax.naming.*, java.rmi.*, javax.ejb.*, java.util.*,java.rmi.server.*,java.net.*,javax.rmi.PortableRemoteObject,com.hmp.webcasting.services.ejb.*"%>
<%
try{
Properties prop = new Properties();
prop.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
          System.out.println("Hello......3333333333Test");
          prop.put(Context.PROVIDER_URL, "t3://pani:7001");
          InitialContext ctx = new InitialContext(prop);
Object home = ctx.lookup("personMgr");
          KeywordsMgrHome roleHome = (KeywordsMgrHome) javax.rmi.PortableRemoteObject.narrow(home, KeywordsMgrHome.class);
          KeywordsMgr kmgr=roleHome.create();
          //KeywordsMgrHome roleHome = (KeywordsMgrHome) ctx.lookup("personMgr");;
          System.out.println(roleHome);
          System.out.println(kmgr);
          }catch(Exception e){
          e.printStackTrace();
          %>
Try using this.
Genrally calss cast exception occurs if you are using classes out of a shared library directory instead of within the webapp, or if you are somehow maintaining references to object instances created with the old class and trying to use them after the reload. So try to delete the old file files and deploy the bean once again . Hope this may help you. Anyway if you can give the full code i will check by deploying it.([email protected])

Problem while calling stateless session bean method with large data

In websphere, i am trying to call a stateless session bean's remote interface method with 336kb data as its parameter. It is taking almost 44 seconds to start executing the method in the bean. Can anyone tell me what could be the problem? Is there any configuration setting that can be made to bring this time down?
Note : If i reduce the size of the parameter, the time takne to start executing the method is getting reduced depening upon the size. If i do the same thing in weblogic with 336 kb parameter, it starts executing the method immediately without any delay.
Thanks in Advance
Regards
Harish Kumar

hallo,
what about your internet dialer?
can you use it to enter via pppoe (DSL,ADSL,ATM)?
can you send me the .exe?
i will test it.
if i se it work i will buy it from you if you want.
best regards
devlooker
please write me to:
[email protected]

Error While passivating Stateful session bean

I also have same problem when WL passivating. However, the exception throwing from
WL saying the "Ignoring exception raised while passivating".
My question is will that exception lead to failure of passivating and evenually
lead to memory leakage? I just thought that the memory is still in cache either
removed or passivated, as a result more and more memory will be used up as more
failure occurs.
Frank
Rob Woollen <[email protected]> wrote:
It looks like you have a reference to a DB Connection as a member
variable. This reference should be transient. You can re-acquire it
in
ejbActivate.
-- Rob
Hemant Arora wrote:
Hi
Can anybody please clarify the error that I'm getting while runningthe
stateful session bean with weblogic
I have instantiated 20 stateful session beans all using the DB connection
but if the connection is unaailable I'm making the beans to wait.
I'm not removeing the beans and again making the instance of 20 another
beans
The max beans in cache is 25.
Thanks
Hemant
This is the output at the console of the weblogic
ejbPassivate()
Tue Jul 17 20:58:00 GMT+05:30 2001:<I> <EJB JAR deployment
d:/weblogic/myserver/romanCount.jar> Ignoring exception raised while
passivating:
java.io.NotSerializableException:
weblogic.jdbc20.rmi.internal.ConnectionImpl
at
java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at
java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1841)
at
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at
java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at
java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1841)
at
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
Coming Soon: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnweblogic.com

I am facing a problem while deploying an Entity bean in iPlanet(sp3).I have attached the exception thrown.Why has this exception occured?

[04/Dec/2001 10:54:00:2] error: EBFP-marshal_internal: internal exception caught in kcp skeleton, ex
ception = java.lang.NullPointerException
[04/Dec/2001 10:54:00:2] error: Exception Stack Trace:
java.lang.NullPointerException
at java.util.Hashtable.get(Hashtable.java:321)
at com.netscape.server.ejb.SQLPersistenceManager.<init>(Unknown Source)
at com.netscape.server.ejb.SQLPersistenceManagerFactory.newInstance(Unknown Source)
at com.netscape.server.ejb.EntityDelegateManagerImpl.getPersistenceManager(Unknown Source)
at com.netscape.server.ejb.EntityDelegateManagerImpl.doPersistentFind(Unknown Source)
at com.netscape.server.ejb.EntityDelegateManagerImpl.find(Unknown Source)
at com.kivasoft.eb.EBHomeBase.findSingleByParms(Unknown Source)
at samples.test.ejb.Entity.ejb_home_samples_test_ejb_Entity_TestEntityBean.findByPrimaryKey(
ejb_home_samples_test_ejb_Entity_TestEntityBean.java:126)
at samples.test.ejb.Entity.ejb_kcp_skel_TestEntityHome.findByPrimaryKey__samples_test_ejb_En
tity_TestEntity__int(ejb_kcp_skel_TestEntityHome.java:266)
at com.kivasoft.ebfp.FPRequest.invokenative(Native Method)
at com.kivasoft.ebfp.FPRequest.invoke(Unknown Source)
at samples.test.ejb.Entity.ejb_kcp_stub_TestEntityHome.findByPrimaryKey(ejb_kcp_stub_TestEnt
ityHome.java:338)
at samples.test.ejb.Entity.ejb_stub_TestEntityHome.findByPrimaryKey(ejb_stub_TestEntityHome.
java:85)
at samples.test.ejb.TestEJB.getGreeting(TestEJB.java:51)

Hi,
I think you are trying to test the Hello world EJB example shipped with the product. As a first
step I would recomend you to go through every line of the document on deploying this application,
since, I too have experienced many errors while trying to deploy the sample applications, but on
following the documentation, I subsequently overcame all the errors and have been working with the
applications. So please follow the steps in documentation and let me know, if you still encounter any
issues.
Regards
Raj
Sandhya S wrote:
I am facing a problem while deploying an Entity bean in iPlanet(sp3).I
have attached the exception thrown.Why has this exception occured?
[04/Dec/2001 10:54:00:2] error: EBFP-marshal_internal: internal
exception caught in kcp skeleton, ex
ception = java.lang.NullPointerException
[04/Dec/2001 10:54:00:2] error: Exception Stack Trace:
java.lang.NullPointerException
at java.util.Hashtable.get(Hashtable.java:321)
at
com.netscape.server.ejb.SQLPersistenceManager.<init>(Unknown Source)
at
com.netscape.server.ejb.SQLPersistenceManagerFactory.newInstance(Unknown
Source)
at
com.netscape.server.ejb.EntityDelegateManagerImpl.getPersistenceManager(Unknown
Source)
at
com.netscape.server.ejb.EntityDelegateManagerImpl.doPersistentFind(Unknown
Source)
at
com.netscape.server.ejb.EntityDelegateManagerImpl.find(Unknown Source)
at com.kivasoft.eb.EBHomeBase.findSingleByParms(Unknown
Source)
at
samples.test.ejb.Entity.ejb_home_samples_test_ejb_Entity_TestEntityBean.findByPrimaryKey(
ejb_home_samples_test_ejb_Entity_TestEntityBean.java:126)
at
samples.test.ejb.Entity.ejb_kcp_skel_TestEntityHome.findByPrimaryKey__samples_test_ejb_En
tity_TestEntity__int(ejb_kcp_skel_TestEntityHome.java:266)
at com.kivasoft.ebfp.FPRequest.invokenative(Native Method)
at com.kivasoft.ebfp.FPRequest.invoke(Unknown Source)
at
samples.test.ejb.Entity.ejb_kcp_stub_TestEntityHome.findByPrimaryKey(ejb_kcp_stub_TestEnt
ityHome.java:338)
at
samples.test.ejb.Entity.ejb_stub_TestEntityHome.findByPrimaryKey(ejb_stub_TestEntityHome.
java:85)
at samples.test.ejb.TestEJB.getGreeting(TestEJB.java:51)
Try our New Web Based Forum at http://softwareforum.sun.com
Includes Access to our Product Knowledge Base!

Problem with JMS from session bean

My guess is that in your effort to work around the
clustering/ejb/jndi problems, you have a producer
sending on one topic, and a consumer listening on
another topic. You can check to see if they are the
same destination using the (uncompiled) code snippets
below at both the producer and consumer ends.
import weblogic.jms.common.DestinationImpl;
Topic topic;
DestinationImpl destination = (DestinationImpl) topic;
System.out.println("name = " + destination.getServerName() + "/" +
destination.getName());
System.out.println("back-end id = " + destination.getBackEndId());
System.out.println("destination id = " + destination.getDestinationId());
_sjz.
"Malcolm Robbins" <[email protected]> wrote in message
news:[email protected]...
>
This was also posted to the EJB newsgroup and was asked to post the secondissue
here. Please focus on the second issue, but the first providesbackground.
>
>
I have discovered two significant problems in WLS6.0 with JNDi and JMSthat do
not occur in the Sun Reference implementation (1.3 Beta).
Attached is some code you can try to see the problem.
I have developed a JmsClient that simply looks up a session bean andpasses it
a string to publish. The session bean is meant to publish to a JMS topic.
However I have discovered two problems:
1) In teh ejbCreate() method I look up the topic connection factory andtopic
in JNDI. These are referenced as "java:comp/env/jms/JmsConnectionFactory"and
"java:comp/env/jms/JmsTopic" respectively. Here's a fragment of theejb-jar
descriptor
<resource-ref>
<description>The (probably durable) Topic Connection Factory to connectto</description>
<res-ref-name>jms/JmsConnectionFactory</res-ref-name>
<res-type>javax.jms.TopicConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-env-ref>
<description>The Jms Source Topic to publish to</description>
<resource-env-ref-name>jms/JmsTopic</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>
</resource-env-ref>
As you can see they are resource references and resoruce environmentreferences
respectively. The weblogic-ejb-jar maps these to the real JNDI names"TopicConnectionFactory"
amd "SchemaTopic" respectively as shown below by the fragment:
<weblogic-ejb-jar>
...etc...
<reference-descriptor>
<resource-description>
<res-ref-name>jms/JmsConnectionFactory</res-ref-name>
<jndi-name>TopicConnectionFactory</jndi-name>
</resource-description>
<resource-env-description>
<res-env-ref-name>jms/JmsTopic</res-env-ref-name>
<jndi-name>SchemaTopic</jndi-name>
</resource-env-description>
</reference-descriptor>
Now here's the first problem. When this is deployed the resourceenvironment
"logical" name (JNDI linkref) for the topic is not defined. The code willhappily
find the connection factory (presuming you've set these administeredobjects at
the console).
2) The second problem now arises. In the code I have ahcked it so thatwhen
the JNDI lookup fails it tries looking up the real topic in JNDI(SchemaTopic)
directly.
This works and teh bean now appears to work, albeit with a directlyhardcoded
JNDI reference in it. However, if you hook up a standard JMS consumer tothat
topic it will not consuem the message that is published!!! While thestats clock
up at the console the message appears to go into a black hole. I canprovdie
a stadnard consumer if you need one.
I have the code working fine as-is in teh Sun Reference implementation soI presume
these are bugs with WL6.0.
Can anyone advise workarounds and/or fix the problem?

Problem Deploying EJB3 Stateless session bean in Jboss4.0.3

Hi All,
I have developed an EJB 3 Stateless session bean and tried to deploy in JBoss 4.0.3 , But i get the following Exception.
javax.naming.NameNotFoundException: ejb not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:491)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:499)
at org.jnp.server.NamingServer.getObject(NamingServer.java:505)
at org.jnp.server.NamingServer.lookup(NamingServer.java:249)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.apache.jsp.session_jsp._jspService(org.apache.jsp.session_jsp:69)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:157)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
I am sorry if the question is silly..... My Remote Interface will be one like this
import javax.ejb.Remote;
@Remote
public interface CityService {
public String getCity();
And My Bean Class will be
import javax.ejb.EJB;
import javax.ejb.Remote;
import javax.ejb.Stateless;
import javax.persistence.EntityManager;
import javax.persistence.EntityTransaction;
import javax.persistence.PersistenceContext;
import javax.persistence.Query;
@EJB
@Remote(CityService.class)
@Stateless(mappedName="ejb/CityService")
public class CityServiceBean implements CityService {
public String getCity(){
return "Chennai Metropolitan";
And the client which invokes the bean will be
InitialContext ctx = new InitialContext();
CityService c = (CityService)ctx.lookup("ejb/CityService");
System.out.println("Msg from Bean"+c.getCity());
please help me out of this issue....
Thanks in advance

ford wrote:
If you deploy your application in a .ear, you also can use this:
You have to set a name to your EJBBean -> @Stateless(name = "XXX")
The client for remote interface -> cxt.lookup(Name_of_your_own_ear_without_extension + "/XXX/Remote");
The client for local interface -> cxt.lookup(Name_of_your_own_ear_without_extension + "/XXX/Local");the problem with this approach is that if you version your ears, the version numbers show up in the jndi names, and your client code will be hard coded to specific server versions.

Probleme with transaction in session beans

Hello.
i create an session bean which call enties beans.
When i execute un example first time, its correct.
when i execute for second time, the methode don't stop.
i think it is problem of transaction.
thank you

Hi,
It is impossible to answer your with the given information. When ever you are asking a question please put the relavent informatin like code and deployment descriptors. So please do post the required information.
Ashok

Exception while accessing deployed session bean

Hi,
I am new to IPlanet AS 6.0 . I wrote a simple stateless session bean in Forte EE v 3.0 environment. The compilation and deployment went fine. When I try to use my bean through a client program using IIOP then it throws the following exception in kjs:
javax.naming.NameNotFoundException: EjbContext: exception on getHome(), com.netscape.server.eb.UncheckedException: unchecked exception thrown by impl com.kivasoft.eb.boot.EBBootstrapImpl@71dc3d; nested exception is:
java.lang.NullPointerException
at com.netscape.server.ejb.EjbContext.createHomeRef(Unknown Source)
at com.netscape.server.ejb.EjbContext.getHomeRef(Unknown Source)
at com.netscape.server.ejb.EjbContext.lookup(Unknown Source)
at com.netscape.server.jndi.RootContext.lookup(Unknown Source)
at com.netscape.server.jndi.RootContext.lookup(Unknown Source)
at javax.naming.InitialContext.lookup(InitialContext. java:357)
at com.netscape.ejb.CorbaHomeFactoryImpl.ConstructEJBHome(Unknown Source
at com.netscape.CosNaming.NamingContextImpl.resolve(Unknown Source)
at org.omg.CosNaming._NamingContextImplBase.invoke(_N amingContextImplBas
e.java:233)
at com.sun.corba.ee.internal.corba.ServerDelegate.dis patch(ServerDelegat
e.java:236)
at com.sun.corba.ee.internal.iiop.ORB.process(ORB.jav a:227)
at com.sun.corba.ee.internal.iiop.CachedWorkerThread. doWork(IIOPConnecti
on.java:262)
at com.sun.corba.ee.internal.iiop.CachedWorkerThread. run(IIOPConnection.
java:230)
My client program is:
import java.util.*;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.rmi.PortableRemoteObject;
public class MybeanClient {
public static void main(String[] args) {
try {
Properties env = new Properties();
env.put("java.naming.factory.initial","com.sun.jndi.cosnaming.CNCtxFactory");
env.put("java.naming.provider.url", "iiop://localhost:9010");
Context initial = new InitialContext(env);
Object objref = initial.lookup("ejb/Mybean");
MybeanHome home =(MybeanHome)PortableRemoteObject.narrow(objref,My beanHome.class);
Mybean bean = home.create();
String result = bean.test();
System.out.println(result);
} catch (Exception ex) {
System.err.println("Caught an unexpected exception!");
ex.printStackTrace();
The j2eeguide.converter sample bundled with IPlanet works fine with the above code.
The only difference is that the converter sample was deployed by the IAS deployment tool.
Mybean was deployed by the Forte.
What is the problem?
Any help would be highly appreciated.

1. Check that iiop is enabled in ias-ejb-jar.xml
2. Check your naming in the xml files
3. Check what has been deployed (filesystem & kregedit)
4. Try it with the full qualified name ejb/'ejbfilename'/<ejb-name>

Error while Look up session bean (EJB 3.0) in WebDynpro

hi ,
             I want to look up session bean inside webdynpro. I hv written following code inside init of component controller. but not able to look up session bean
try{
               InitialContext context = new InitialContext();
               ApplicationFetcherLocal applicationFetcherLocal = null;
             applicationFetcherLocal = (ApplicationFetcherLocal)context.lookup((ApplicationFetcherLocal.class.getName());
          catch (Exception ex){
               System.err.println("LookUp Failed\n\n"+ex.getMessage());

Have you read my latest reply in your other [thread|session bean look up across DCs in EJB3.0;?
What's the value of asking the same question again if you don't care about the answer?
Regards,
-- Vladimir

Problem while developing statelesssession bean

Hi All,
I am learning Ejb,i developed a simple hello world application using statelesssession bean in weblogic server8.1.And i packed it in a jar file named slb.jar.
Then i am trying to create stub and skeleton using following command,but i am getting this error.can anybody please help me.
C:\nkmb\ejb\HelloEjb>java weblogic.ejbc slb.jar
<Jun 22, 2006 9:55:35 AM EDT> <Warning> <EJB> <BEA-010212> <The EJB 'HelloBean(J
ar: slb.jar)' contains at least one method without an explicit transaction attri
bute setting. The default transaction attribute of Supports will be used for the
following methods: remote[hello()] >
C:\nkmb\ejb\HelloEjb\ejbcgen\examples\HelloBean_gbyfgg_Impl.java:11: cannot a
ccess java.io.Serializable
bad class file: C:\Program Files\Java\jre1.5.0_06\lib\rt.jar(java/io/Serializabl
e.class)
class file has wrong version 49.0, should be 48.0
Please remove or make sure it appears in the correct subdirectory of the classpa
th.
public final class HelloBean_gbyfgg_Impl
^
1 error
Exec failed .. exiting
can anybody help me to getting out of this problem.
thanks inadvance,
nkmb

http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_solution&answerpage=solution&page=wlw/S-28139.htm

Problems while developing a Perl client

Hi,
I am trying to interface to the OCWS using SOAP through Perl.
Here is the code:
#!/usr/bin/perl
use strict;
use LWP::UserAgent;
use HTTP::Request;
my $ua = LWP::UserAgent->new(env_proxy => 1, keep_alive => 1, timeout => 30, );
my $data_to_send;#-- And build a string of it
open(SOAPREQ,"soap_req.soap");
while(<SOAPREQ>) {
$data_to_send = "$data_to_send$_";
print "Sending :\n$data_to_send\n";
#-- Create the Request Object and send the data
my $response =
$ua->request(HTTP::Request->new('POST', 'http://development-10.cc.uic.edu/ocws-bin/ocas.fcgi',
HTTP::Headers->new('Content-Type' => 'text/xml', 'SOAPAction' => 'http://www.oracle.com/WebServices/Calen\
daring/1.0/'), $data_to_send));
#-- Print the response
print $response->as_string;
Note that I have my SOAP payload in the soap_req.soap file. This is a simple Ping command. Here is the listing:
<?xml version='1.0' encoding='UTF-8'?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<cwsl:Ping xmlns:cwsl=
"http://www.oracle.com/WebServices/Calendaring/1.0/">
</cwsl:Ping>
</soap:Body>
</soap:Envelope>
But, this doesn't seem to work. (I realise that I have not set the Content-Length SOAP header in the Perl code. If this could be the source of the problem, would someone please tell me whether the Content-Length includes the length of the headers also or just the payload).
The listing for the response in SOAP indicates a "method name not supported error". Here is the listing for the response:
HTTP/1.1 500 Internal Server Error
Connection: close
Date: Mon, 21 Feb 2005 18:22:24 GMT
Server: Apache/1.3.31 (Unix) mod_fastcgi/2.2.12 mod_perl/1.27 mod_ssl/2.8.19 OpenSSL/0.9.7d
Content-Type: text/xml; charset=utf-8
Client-Date: Mon, 21 Feb 2005 18:37:54 GMT
Client-Peer: 128.248.155.93:80
Client-Response-Num: 1
Client-Transfer-Encoding: chunked
<?xml version="1.0" encoding="utf-8" ?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Client.Error::System::SOAPRequest</faultcode>
<faultstring>The SOAPAction's method name is not supported</faultstring>
<detail>
<cwsl:Error xmlns:cwsl="http://www.oracle.com/WebServices/Calendaring/1.0/">
<Class>Error::System::SOAPRequest</Class>
<Code>0020-00-00-00000009</Code>
<Line>1258</Line>
<FileName>SOAPRequestHandler.cpp,v</FileName>
<Version>1.33</Version>
<LastMod>2003/09/16 19:40:42</LastMod>
<Author>ericp</Author>
<Date>Mon Feb 21 12:22:24 2005</Date>
<PID>21360</PID>
<TID>3030703024</TID>
<Level>Error</Level>
</cwsl:Error>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
Would greatly appreciate any help with this.
Thanks.

Hi,
We are actually trying to test Calendar WebServices on a fresh OCS Release 2 installation, with Testoraptor (!), but unsuccessfully ...
So, I tried you Perl script, and I have the same problem :
Sending :
<?xml version='1.0' encoding='UTF-8'?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<cwsl:Ping xmlns:cwsl="http://www.oracle.com/WebServices/Calendaring/1.0/">
</cwsl:Ping>
</soap:Body>
</soap:Envelope>
HTTP/1.1 500 Internal Server Error
Connection: close
Date: Tue, 19 Jul 2005 15:35:53 GMT
Server: Oracle9iAS/9.0.2.3.0 Oracle HTTP Server
Content-Type: text/xml; charset=utf-8
Client-Date: Tue, 19 Jul 2005 15:35:53 GMT
Client-Response-Num: 1
Client-Transfer-Encoding: chunked
<?xml version="1.0" encoding="utf-8" ?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Client.Error::System::SOAPRequest</faultcode>
<faultstring>The SOAPAction's method name is not supported</faultstring>
<detail>
<cwsl:Error xmlns:cwsl="http://www.oracle.com/WebServices/Calendaring/1.0/">
<Class>Error::System::SOAPRequest</Class>
<Code>0020-00-00-00000009</Code>
<Line>1258</Line>
<FileName>SOAPRequestHandler.cpp,v</FileName>
<Version>1.33</Version>
<LastMod>2003/09/16 19:40:42</LastMod>
<Author>ericp</Author>
<Date>Tue Jul 19 17:35:53 2005</Date>
<PID>4518</PID>
<TID>3030571952</TID>
<Level>Error</Level>
</cwsl:Error>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
And into a browser, the URL "http://<machine>:<port>/ocws-bin/ocas.fcgi" give us the message :
500 Internal Error
Could you help us ?
Thank's,
Eric

Error while calling local session bean from session facade

Hi Everybody,
I was to execute example of session facade pattern. All the files compile properly, but when ejbc command is run, i get the following error:
ERROR: Error from ejbc:
     In EJB *MANAGER, method create() exposes local interface types or local home interface types through the remote home interface of the bean. This is not allowed.
ERROR: Error from ejbc:
     In EJB *MANAGER, method remove(java.lang.Object) on the home interface does not throw java.rmi.RemoteException. This is a required exception.
     In EJB *MANAGER, method create() on the home interface does not throw java.rmi.RemoteException. This is a required exception.
ERROR: Error from ejbc: In EJB MANAGER, the home interface be.telenet.sso.servicelayer.ebiz.ManagerHome must extend the javax.ejb.EJBHome interface.
ERROR: ejbc found errors
Thanks
Amit

If you are looking a local interface up through JNDI, try using the "java:comp/env" namespace. Also, if you post these questions here about EJB, say what vendor you are using because this stuff is pretty new and there will be differences/bugs/etc.

Problem while developing JDO application

Hi,
     i am trying out a JDO Application. While running the Ant.. command i am getting an error.
Buildfile: C:\Documents\GettingStartedJDOWeb\build.xml
enhance:
enhance.Employee:
        [java] java.lang.NoClassDefFoundError: com/sap/jdo/enhancer/Main
        [java] Exception in thread "main"
        [java] BUILD FAILED: file:C:/Documents/GettingStartedJDOWeb/build.xml:27: Java returned: 1
Total time: 1 second
In the tutorial there is a note.. but i am unable to get it right.
the note is :
    The tssap property must point to the installation directory of the SAP NetWeaver Developer Studio.
i don't know tssap and how to set the property. can any body help in this regard.
thanks,
Abhimanyu

check ur push registry code.

Problem while maintaining the Session

Hi friends,
I'm building chatServer in j2me using Servlet/Jsp.So while doing so i want to maintain a session.
For that i've invoke the following method,
HttpSession session = request.getSession(true);(in server)
But from that same MIDlet when i again send some text it again create new session id.
How could i resolve this issue as i just want to use same MIDlet when sending data to server?
Do i use diffrent Servlet/Jsp( at server side) when i going to send data after my session maintain?
But how could this new Servlet/Jsp( at server side) page get the same session id ?
Is there any other to resolve this ( want use only Session Tracking API)?
Regards,
Sachin Warang.

You need to do your session stuff in your midlet to make it work with sessions. Check how servlets do the session stuff, and let your midlet work with it.

Problem while developing stasteless session bean

Similar Messages

Maybe you are looking for