Error running "Develop a Stateless Session EJB Web Service using EJB 3.0"

Running this "how-to," the build and deploy worked fine for me, but when I ran "ant run," I got:
[echo] -----> Setting up the application client module
[oracle:genProxy] null, WSDLException: faultCode=INVALID_WSDL: The document: http://localhost:8888/ejb30ws/ejb30ws?wsdl is not a wsdl file or does not have a root element of "definitions" in the "http://schemas.xmlsoap.org/wsdl/" namespace or the "http://www.w3.org/2004/08/wsdl" namespace.

Debu,
Yes, it successfully deployed.
Here are the messages from the failed run.
BUILD SUCCESSFUL
Total time: 33 seconds
D:\Oracle_ejb3.0\demo\howtoejb30ws>ant run
Buildfile: build.xml
common:
[echo] BuildName: ejb30ws
[echo] BuildHome: D:\Oracle_ejb3.0\demo\howtoejb30ws
[echo] BuildFile: D:\Oracle_ejb3.0\demo\howtoejb30ws\build.xml
[echo] BuildJVM: 1.5
oracle-env-check:
java-env-check:
init:
[echo] -----> Initializing project properties
setup:
[echo] -----> Creating the required sub-directories
cli-setup:
[echo] -----> Setting up the application client module
[oracle:genProxy] null, WSDLException: faultCode=INVALID_WSDL: The document: http://localhost:8888/ejb
/ejb30ws?wsdl is not a wsdl file or does not have a root element of "definitions" in the "http://schem
mlsoap.org/wsdl/" namespace or the "http://www.w3.org/2004/08/wsdl" namespace.
[oracle:genProxy] WSDLException: faultCode=INVALID_WSDL: The document: http://localhost:8888/ejb30ws/e
ws?wsdl is not a wsdl file or does not have a root element of "definitions" in the "http://schemas.xml
.org/wsdl/" namespace or the "http://www.w3.org/2004/08/wsdl" namespace.
BUILD FAILED
D:\Oracle_ejb3.0\demo\howtoejb30ws\build.xml:316: oracle.j2ee.ws.common.tools.api.WsdlValidationExcept
null, WSDLException: faultCode=INVALID_WSDL: The document: http://localhost:8888/ejb30ws/ejb30ws?wsdl
not a wsdl file or does not have a root element of "definitions" in the "http://schemas.xmlsoap.org/ws
namespace or the "http://www.w3.org/2004/08/wsdl" namespace.
Total time: 3 seconds
D:\Oracle_ejb3.0\demo\howtoejb30ws>

Similar Messages

Error during deployment of stateless session EJB using EJB 3.0

having trouble deploying a stateless session bean to app server 10.1.3.1 oc4j container.
deceided to go through oracles demo: How-To Develop a Stateless Session EJB using EJB 3.0 (http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-ejb30-stateless-ejb/doc/how-to-ejb30-stateless-ejb.html).
the demo encounters the same issue. so i assume there is something wrong with the app server set up, and not my source code.
here is the deployment log:
[Jul 1, 2009 11:59:25 AM] Application Deployer for test_ws STARTS.
[Jul 1, 2009 11:59:25 AM] Copy the archive to C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\test_ws.ear
[Jul 1, 2009 11:59:25 AM] Initialize C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\test_ws.ear begins...
[Jul 1, 2009 11:59:25 AM] Unpacking test_ws.ear
[Jul 1, 2009 11:59:25 AM] Done unpacking test_ws.ear
[Jul 1, 2009 11:59:25 AM] Initialize C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\test_ws.ear ends...
[Jul 1, 2009 11:59:25 AM] Starting application : test_ws
[Jul 1, 2009 11:59:25 AM] Initializing ClassLoader(s)
[Jul 1, 2009 11:59:25 AM] Initializing EJB container
[Jul 1, 2009 11:59:25 AM] Loading connector(s)
[Jul 1, 2009 11:59:26 AM] Starting up resource adapters
[Jul 1, 2009 11:59:26 AM] Processing EJB module: ejb30ws-ejb.jar
[Jul 1, 2009 11:59:26 AM] application : test_ws is in failed state
[Jul 1, 2009 11:59:26 AM] Operation failed with error: java.lang.NoClassDefFoundError
the opmn log reveals the same error, but no more detail.
any ideas???
/stuck

I am having exactly the same issue. Was this issue resolved? If so, please share the resolution and if not can someone please suggest what could be wrong.
Thanks

Registering EJB/Stateless Session Bean Web Service in Registry

Hi verybody!
I would like to know how I can register a Web Service in a registry. The web service is implemented as a session bean.
The problem is not the actual code to register the service, but how and where can I hook this code into the application so that it is started when the application server is started.
I've read the Sun J2EE tutorial which registered the service in the moment when the context for the servlet for an ordinary web client was created. This is not what I want. I would like to register the service when starting the EJB container, without the need to give it a kick from some external interface.
Any help or ideas will be greatly welcome
Regards
PI

1. But I thought you were using a 'stateful session bean'?
2. For stateless session beans, there is no direct link between a remote reference and an instance of the bean. It is safe to hang on to the remote reference as long as you would like, of course it may go stale if the server dies. You will also find that the create() method does not actually contact the server, so doing it each usage costs very little. So, either way you should be fine.
3. As for memory leaks, make sure that you are closing all statements, result sets, etc. promptly. These are commonly the problem. Also, use hprof or some other profile tool to determine what types of data you are allocating and (with better tools) what types of data you may be holding on to references to.
Chuck

Stateless Session EJB Bean Example please

Dear Friends,
Develop a stateless session EJB bean and deploy it in WebLogic 8.1
Please proivde me a weblogic8.1 example along with the deployment steps.
Also mention the supporting softwares needed.
I have weblogic 8.1, JDK 1.5
Advance Thanks.
Rengaraj.R

Hi Rahul,
Please paste the files here if they are small in size.
IDfLoginInfo li = new DfLoginInfo(); //this is where the error occurs as when i remove this line. i dont get an error
Have you checked this as I have mentioned something regarding this in my mail?
Regards
Vicky

Stateless session EJB as Web service adds root context prefix in embedded

Hi,
In JDeveloper 10.1.3.1 production (I'm pretty sure it didn't do it in the developer preview), if I run up a stateless session bean surfaced as a web service, then the root context gets prefixed with EJB- e.g. my application context is "services", so deployed to SOA suite the url is of the form:
http://localhost:8888/services/webservice?WSDLbut if I run it up in embedded OC4J in JDeveloper, the URL is:
http://localhost:8888/EJB-services/webservice?WSDL(I'm running embedded on port 8888 too to make deploy easier)
which is causing a huge headache having to change loads of references to web services when moving between development, and deploy for test.
I've tried mucking around no-end with J2EE application properties to get rid of the EJB- prefix, to no end, any help much appreciated.
Cheers.

Thanks for the reply.
Afraid the context is just defined as services.
I've done a bit more investigation, and if I simply run/debug the application, and it gets deployed under the default current-workspace-app, then the context gets the EJB- prefix. If I run up the embedded OC4J and manually deploy the application into it, then a new application (services) is created, and the context is correct (although I've now got the application deployed automatically under current-workspace-app, and manually under services, and so both URI's above now obviously work).
This is probably a useable work-around, but still doesn't feel quite right.
Cheers.

Stateless Session EJB hangs using URLConnection but WLS doesn't clean up

Hi
We have a stateless session EJB running under WLS 5.1 with service
pack 10 on Solaris.
The bean calls a remote HTTP server using the java.net.URLConnection
class and forwards the response to the EJB client. The bean is largely
working fine but some threads hang waiting on the HTTP response. Debug
statements, which are written immediately after the response has been
read and the connection has been closed, do not appear in our log for
the hung threads. The WebLogic Console displays these threads as "in
use" and a "netstat -an" displays the tcp connections as ESTABLISHED.
However, the access logs of the remote Apache server show the HTTP
connections of the threads in question completed successfully with
HTTP code 200. The Apache server is using keep-alive connections.
Some EJB threads are still waiting for something it seems.
Has anyody else experienced this when using URLConnection from
stateless session EJBs under WLS?
The second problem is why doesn't WLS time these threads out after
trans-timeout-seconds (we're using the default of 300 seconds)? The
WLS log shows no error messages relating to this problem.
I'm grateful for any info offered.
Thanks in advance
Steve

If you suspect that WLS protocol handler is at fault (and quite often it is),
one thing to try is (if you use Sun's JVM) to use Sun's HTTP protocol handler
instead of WLS (the most common symptom is when code which makes HTTP requests
works fine outside of WebLogic and you have problems getting it to work inside
WebLogic) :
replace
URL url = new URL("http://...");
HttpURLConnection conn = (HttpURLConnection)url.openConnection();
with
URL url = new URL(null, "http://...", new sun.net.www.protocol.http.Handler());
HttpURLConnection conn = (HttpURLConnection)url.openConnection();
You will have to edit weblogic.policy to allow your code to specify protocol
handler.
Also note that transaction timeout is only checked on method boundaries, or
when your code attempts to do something with the database - it is not going to
interrupt thread which is waiting for HTTP response.
Steve Lock <[email protected]> wrote:
Hi
Thanks for the info. The remote HTTP server's access log shows that
the requests were successfully processed. Doesn't this mean that the
connection is then closed? I know the web server is using keep-alive
connections but I thought this was transparent to the client...?
Also why doesn't WLS remove the hung threads?
Steve
"Ignacio G. Dupont" <[email protected]> wrote in message news:<[email protected]>...
We have had a problem like yours with Weblogic 6.1 SP2 on Linux
The problem is sun's implementation of the HTTP connections doesn't have a
timeout, so if the other peer doesn't close the connection your threads will
be "locked" on the connection.
We have found searching the web that the Jakarta project has a package
called Jakarta commons that implements HTTP connections with an
setSoTimeout(int timeout) method so you can open the connections with your
desired timeout. You have to download the code from the CVS as the released
version doesn't support the timedout sockets yet.
When support for the JDK 1.4 version will be announced by Bea you could use
one of its new features that will allow you to pass arguments to the JVM to
specify the maximum socket connection stablising timeout and the max
inactivity on the socket too.
Hope it helps you.
Dimitri

Servicegen for stateless session EJB

I've run into some minor trouble when I tried to generate
web services for some stateless session EJBs with the
servicegen Ant method. Note that expandMethods has been
set to True. It appears that the generated web-services.xml
file contains methods from the EJB's remote interface. When
deploying the web service WLS will use the locale interface.
If the remote interface has methods not found in the local
interface WLS will refuse to deploy the web service. No big
deal, since I could just add the missing methods to the
local interface. But still, I think this is somewhat odd
and inconsistent behavior. Is there anyway to get WLS to
deploy the web services against the remote interfaces, or
is this just a bad idea?
/Björn

Further information:
According to metalink bug 3224465, this was a bug fixed in release 9.0.2.3.99 of the App Server. However, I am using 9.0.3.1 and still have the problem....

Stateless session EJBs & "idempotent"

We need to declare a method as "idempotent" to take care of failure inside a
          method call, For that to work the code inside should written in such way so
          that repeated call to the same method should not give us diffrent result.
          But why can't weblogic implement a partial rollback( Just like Oracle's save
          point rollback, where you can rollback to certain point within a
          transaction).
          Because some times it is not possible to code in such a way to get the same
          result every time(Incase of fail over)
          Thanks
          ,Stateless session EJBs
          Stateless session EJBs can have both a cluster-aware home stub and a
          replica-aware EJBObject stub. By default, WebLogic Server provides failover
          services for EJB method calls, but only if a failure occurs between method
          calls. For example, failover is automatically supported if there is a
          failure after a method completes, or if the method fails to connect to a
          server. When failures occur while an EJB method is in progress, WebLogic
          Server does not automatically failover from one server to another.
          This default behavior ensures that database updates within an EJB method are
          not "duplicated" due to a failover scenario. For example, if a client calls
          a method which increments a value in a datastore and WebLogic Server fails
          over to another server before the method completes, the datastore would be
          updated twice for the client's single method call.
          If methods are written in such a way that repeated calls to the same method
          do not cause duplicate updates, the method is said to be "idempotent." For
          idempotent methods, WebLogic Server provides the
          stateless-bean-methods-are-idempotent deployment property. If you set this
          property to "true" in weblogic-ejb-jar.xml, WebLogic Server assumes that the
          method is idempotent and will provide failover services for the EJB method,
          even if a failure occurs during a method call.


Vishal,
I wouldn't think you would have a problem doing RMI communication from a Entity
Bean - - for instance, when a WLS instance 'hosts' an EJB that communicates to
a different WLS instance that 'hosts' an EJB that communication occurs via RMI.
Chuck Nelson
Developer Relations Engineer
BEA Technical Support

Stateless Session EJB "Wait???"

I need to let a Stateless Session EJB wait until 2:00 AM before it runs. How can I do that? I don't want to use a loop since it will eat up all system computing resource.
Thanks
Kenny

Is that a way to code it? I don't want to use existing class. I need to control the EJB itself to "wait" for some time to run.
Thanks
Kenny

Stateless session EJB invoke RMI

Is it possible to invoke RMI calls from stateless session EJBs. It is my understanding
restrictions exists like opening socket, file io, .. are not permitted from EJBs.
Is there a way around.

Vishal,
I wouldn't think you would have a problem doing RMI communication from a Entity
Bean - - for instance, when a WLS instance 'hosts' an EJB that communicates to
a different WLS instance that 'hosts' an EJB that communication occurs via RMI.
Chuck Nelson
Developer Relations Engineer
BEA Technical Support

Transaction rollback in stateless session EJB 3.0

Hello everyone !
I have a stateless session EJB as per 3.0 spec.
/*Remote Interface*/
package com.nseit.ncfm2.data.ejb;
import java.sql.SQLException;
import java.util.Collection;
import javax.ejb.Remote;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionAttributeType;
import javax.naming.NamingException;
import com.nseit.ncfm2.security.Audit;
@Remote
public interface ProductionDataChangesRequestsRemote {
     @TransactionAttribute(TransactionAttributeType.REQUIRED)
     public boolean shiftCandidateDetails(String sourceNcfmId,
               String destinationNcfmId, Collection<String> specialCasesList, String shiftingRemarks, String user, Audit updtAudit) throws NamingException, SQLException;
/*Bean Class*/
package com.nseit.ncfm2.data.ejb;
import javax.ejb.Remote;
import javax.ejb.Stateless;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionAttributeType;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;
import javax.naming.NamingException;
import com.nseit.ncfm2.security.Audit;
import com.nseit.ncfm2.util.server.lookup.LookUpServerResources;
import java.sql.*;
import java.util.*;
* Session Bean implementation class ProductionDataChangesRequestsBean
@Stateless(name = "ProductionDataChangesRequestsBean", mappedName = "ProductionDataChangesRequestsEJB")
@Remote(ProductionDataChangesRequestsRemote.class)
@TransactionManagement(TransactionManagementType.CONTAINER)
public class ProductionDataChangesRequestsBean implements
          ProductionDataChangesRequestsRemote {
     * Default constructor.
     public ProductionDataChangesRequestsBean() {
          // TODO Auto-generated constructor stub
     @Override
     @TransactionAttribute(TransactionAttributeType.REQUIRED)
     public boolean shiftCandidateDetails(String sourceNcfmId,
               String destinationNcfmId, Collection<String> specialCasesList,
               String shiftingRemarks, String user, Audit updtAudit)
               throws NamingException, SQLException {
          // TODO Auto-generated method stub
          Connection conn = null;
          PreparedStatement pstmt = null;
          int updtCnt = 0;
          boolean areDetailsShifted = false;
          try {
               /* Start: update table-1 */
               updtCnt = pstmt.executeUpdate();
               /* End: update table-1 */
               /* Start: update table-2 */
               updtCnt = pstmt.executeUpdate();
               /* End: update table-2 */
               areDetailsShifted = true;
          } /*catch (SQLException e) {
               // TODO Auto-generated catch block
               System.out
                         .println("SQLException in ProductionDataChangesRequestsBean.shiftCandidateDetails(...) "
                                   + e.getMessage());
               // e.printStackTrace();
               context.setRollbackOnly();
          } */finally {
               LookUpServerResources.closeStatement(pstmt);
               LookUpServerResources.closeConnection(conn);
          return areDetailsShifted;
Currently,if the 1st table update succeeds and the 2nd table update gives an exception,a rollback is not taking place i.e records in 1st table are updated.
I want the transaction to be rolled back in case an SQLException occurs(or for that matter,any runtime exception occurs).
I tried two approaches :
i: Use of context.setRollbackOnly() in catch block for SQLException
ii:Throwing the SQLException
In both the cases, the transaction didn't roll back.
How can I achieve this :
i: Without the usage of @ApplicationException annotation(as I do not have any application exceptions)
ii: Without catching the SQLException and then calling context.setRollbackOnly()
Or what is the standard way?
Thanks !

Where is your connection object coming from?

RMAN-10006: error running SQL statement: alter session set remote_dependenc

Backups are failing with following error
RMAN-00554: initialization of internal recovery manager package failed
RMAN-12001: could not open channel default
RMAN-10008: could not create channel context
RMAN-10002: ORACLE error: ORA-00096: invalid value SIGNATURE for parameter remote_dependencies_mode, must be from among MANUAL, AUTO
RMAN-10006: error running SQL statement: alter session set remote_dependencies_mode = signature
Not able to change to signature
SQL> alter session set remote_dependencies_mode=signature;
ERROR:
ORA-00096: invalid value SIGNATURE for parameter remote_dependencies_mode, must
be from among MANUAL, AUTO
I dont see MANUAL or AUTO as valid value for this parameter (http://download.oracle.com/docs/cd/B10501_01/server.920/a96536/ch1175.htm#1023124) DB version is 9.2.0
Parameter type
String
Syntax
REMOTE_DEPENDENCIES_MODE = {TIMESTAMP | SIGNATURE}
Default value
TIMESTAMP
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
=======================================
I believe it could be because of following bug
"A PRE-PATCHED ORACLE IMAGE CAN BE INSTALLED IN MEMORY "
Refer: "https://metalink2.oracle.com/metalink/plsql/f?p=130:15:1613505143885559758::::p15_database_id,p15_docid,p15_show_header,p15_show_help,p15_black_frame,p15_font:BUG,4610411,1,1,1,helvetica"
I appreciate your effort in fixing this issue.
Edited by: user10610722 on Nov 25, 2008 4:37 PM

Hi:
It seems when you are starting RMAN it's executing some commands (one 'ALTER SESSION...'. It's seems to be a batch which has a bad value for SORT_AREA_SIZE. Find it and modify to a proper value as message shows. If you can't find start RMAN by calling directly the executable ($ORACLE_HOME/bin/rman or %ORACLE_HOME%/bin/rman.exe).

Private field in a stateless session EJB

Hi guys,
I have a question about the design of a stateless session EJB.
I would like to know :
Does it make sense to put a private field in a stateless session bean???
Imagine the following sitiation:
I have a stateless session bean.
Its job is to delegate the clients calls to some services (Java objects).
These services are held in the private field and instatiated when WebLogic invokes
the ejbCreate method.
So I would like these services (Java objects) be instantiated before the clients
invoke the bean's method for delegation - I mean, when WebLogic
decides to create beans and put it in the pool (on the server startup for example).
But what happens when the same bean once having finished its job is used by a
different client???
Are the services once instatiated available to the new client or WebLogic invokes
the ejbCreate() method and the services are instatiated one more time???(which
would be a performence killer)
I must mention that in order to make the instatiation of the services possible,
I presume I must implement the ejbCreate() method on the bean implementation class
which invokes a private method doing the instatiation.
So, do you think these design is a good design and what is its impact on the performence
of the stateless session EJB ???
Thank you.
Freddy

Rob Woollen <[email protected]> wrote:
Freddy wrote:
Hi guys,
I have a question about the design of a stateless session EJB.
I would like to know :
Does it make sense to put a private field in a stateless session bean???
Sure
Imagine the following sitiation:
I have a stateless session bean.
Its job is to delegate the clients calls to some services (Java objects).
These services are held in the private field and instatiated when WebLogicinvokes
the ejbCreate method.
So I would like these services (Java objects) be instantiated beforethe clients
invoke the bean's method for delegation - I mean, when WebLogic
decides to create beans and put it in the pool (on the server startupfor example).
But what happens when the same bean once having finished its job isused by a
different client???
Are the services once instatiated available to the new client or WebLogicinvokes
the ejbCreate() method and the services are instatiated one more time???(which
would be a performence killer)
WLS keeps the bean instances around in a pool. See
http://edocs.bea.com/wls/docs81/ejb/session.html#1118700
I must mention that in order to make the instatiation of the servicespossible,
I presume I must implement the ejbCreate() method on the bean implementationclass
which invokes a private method doing the instatiation.
So, do you think these design is a good design and what is its impacton the performence
of the stateless session EJB ???It's fine and a pretty common pattern.
-- Rob
Thank you.
Freddy
Thank you very much Rob.
Freddy

Generation Error - when trying to publish a Java web service

Hi All,
I keep getting the following Generation Error -- java.util.NoSuchElementException_ when I'm trying to create a Java Web Service using the jdeveloper wizard.
I have 2 entities and 2 stateless session beans acting as their facades. One entity has a One-One(FK) relationship with the other entity. I test out the entities and session beans using the test client and the OC4J embedded container and everything seems to work. When I try to generate a Java WebService from one of the entities I keep getting the "Generation Error". Could someone please provide me with some insight into why I'm facing this problem, because it seemed fine when I published J2EE web services previously and now this happens and I cant seem to publish web services anymore. Everytime I keep getting the same GenerationError. Thanks in advance.

Without going into any technical discussion about the code, my first question is what JDK version was used to create this which was imported into the form? Understand that Forms 10 runs on JDK 1.4.2, so if you used any newer JDK version, likely there will be problems.

Errors trying to Invoke web service using BES and SIF

Moved this up from the Integration Forum to see if I can get some visibility on it.
Description : When an invoice get's approved we need to pass on the details of the invoice and approval to the 3rd party customer.
So far I have been able to test the business event which calls the web service that writes the information to a file. However, although the file is created there is no content in the file.
So the steps up to this point
1. Create a simple web service that takes a string as an input parameter and writes this out to a file.
2. Locate the Approve Invoice event [oracle.apps.ap.event.invoice.approval] and add a new subscription that will invoke my web service.
I have a number of issues at the moment.
From the business event page I can test the event which writes a record to the wf_java_deferred queue. I have been able to call the service and create a file however that seems to have stopped working. Where do I look to see what's going wrong? Is the diagnostics the best place to start
If I go into Status Monitoring I can see the last Business Event test I did is now having errors when it tries to invoke the web service. The error I get is
Error Activity ID
Error Activity Label
Error Assigned User
Error Item Type
Error Item Key
Error User Key
Error Message          oracle.apps.fnd.wf.bes.InvokerException: Event payload is not available
Error Name
Error Notification ID
Error Result Code
Error Stack          oracle.apps.fnd.wf.bes.InvokerException: Event payload is not available at oracle.apps.fnd.wf.bes.WebServiceInvokerSubscription.onBusinessEvent(WebServiceInvokerSubscription.java:236) at
oracle.apps.fnd.wf.bes.EventDispatcher.executeSubscription(EventDispatcher.java:870) at oracle.apps.fnd.wf.bes.EventDispatcher.processSubscription(EventDispatcher.java:556) at
oracle.apps.fnd.wf.bes.EventDispatcher.dispatch(EventDispatcher.java:335) at oracle.apps.fnd.wf.bes.AgentListenerProcessorNew.processMessage(AgentListenerProcessorNew.java:373) at
oracle.apps.fnd.cp.gsc.SvcComponentProcessor.process(SvcComponentProcessor.java:659) at oracle.apps.fnd.cp.gsc.Processor.run(Processor.java:283) at java.lang.Thread.run(Thread.java:619)
Error Monitor URL
Timeout Value          0
Event Name          oracle.apps.ap.event.invoice.approval
Event Details          PLSQL:WF_STANDARD.EVENTDETAILS/WFERROR:332124
Event Message          View Event Message
Event Key          3134525_1
Event Data URL     http://hostname.co.nz:8000/OA_HTML/RF.jsp?function_id=18157&resp_id=-1&resp_appl_id=-1&security_group_id=0&lang_code=US&
params=.tut9vCLHp8BRzYkdaLWV3ekOnBGTRSUSr1RYBqw0ISKruqT5nAzoOSzIkWSQrzWO8z23dyX31GlRw75r21ich1KC4hE2KL.ZedjIDcPalm8f.akDClydWkRR3w2eGuk
Event Subscription http://hostname:8000/OA_HTML/RF.jsp?function_id=26058&resp_id=-1&resp_appl_id=-1&security_group_id=0&lang_code=US&
params=fR9VOZbtfJEdYQNb645CRU3kD39os3CZwt7XUpbOYb1RImgFkWaeDFEV0SCaVn1M
Error Type          UNEXPECTED
Error Details          PLSQL:WF_STANDARD.ErrorDetails/WFERROR:332124
Administrator Role          SYSADMIN
Subscription Details          PLSQL:WF_STANDARD.SubscriptionDetails/WFERROR:332124
Error Person ID
Error Person Username
How do I get access to the payload? I only really need 2 or 3 items at this time. Do I need to extend a seeded java function? For example in my initial tests I only want to pass across the Invoice Id so how do I get the value of this attribute out of the wf_event_t (Is this the correct object name) and into the payload that is being passed across to the service call.
Cheers
Owen

Hello Owen
I am experiencing the exact same issue as you are (missing payload) when invoking a web service and was wondering if you have resolved this issue or gotten any new useful information?
Regards,
Magnus

Error running "Develop a Stateless Session EJB Web Service using EJB 3.0"

Similar Messages

Maybe you are looking for