Own ZCX Exception Class, how to translate

Hi,
i've written my own ZCX_XYZ exception class. On the tabstrip "Texts" i've entered some texts, but how can i translate those texts? When i'm going to Goto/Translations i'm just getting empty object list...

Thanks for investigating again. Using SE63_OTR i'm getting the message that this is obsolet and i have to use SE63.
To make things more clearer i made some screenshots.
<a href="http://666kb.com/i/atri3x4ib1uryogzr.png">Class with Attributes</a>
So i have a class ZCX_FTP, the superclass is CX_DYNAMIC_CHECK, and i have an attribut which was generated automatically with the same name of the class.
The texts are as follows:
<a href="http://666kb.com/i/atri6gk1z8qn3ff9j.png">Defined Text</a>
So now i'm going to SE63 (BTW are these texts otr short texts or long ones?), entered the ID and pressed Edit:
<a href="http://666kb.com/i/atri82j1b5x02q7ev.png">SE63 with ID</a>
I'm getting Object does not exists....
Logging on with different language might be a workaround with de/en, but i have some difficulties navigating inswedish, greek, france and half a dozen more languages. On the other hand, i do not want to hand over the source texts to those who translates the texts. I'm really lost in this and cant find online help/documentation dealing with this.

Similar Messages

Each exception class in its own file????

Hi, I am still quite new to java, and I don't fully understand exceptions. Could you please tell me if for each exception class you require do you have to have a a seperate file. e.g. I'm creating my own array exceptions classes.
The following is the structure:
** The base array exceptions class
public class arrayException extends Exception {
public arrayException () { super(); }
public arrayException (String s) { super(s); }
** The outofboundsArrayException
public class outofboundsArrayException extends arrayException {
public outofboundsArrayException ()
{ super("Number entered is out of bounds"); }
public outofboundsArrayException (String s)
{ super(s); }
** The fullArrayExceptiom
public class fullArrayException extends arrayException {
public fullArrayException ()
{ super("The array is full"); }
public fullArrayException (String s)
{ super(s); }
So will the three classes above need their own file.
I wanted to also know what the super does. I thought when the exception was raised, the text message in the super method is outputted, but i've tested that and it doesn't output (e.g. the error message "The array is full" doesn't output). The only thing that outputs is what you put in the catch part.
Thank You very Much!

Could you please tell me if
for each exception class you require do you have to
have a a seperate file.Yes. Exception classes are like any other public class in Java, in that it must be in its own file with the standard naming conventions.
I wanted to also know what the super does. I thought
when the exception was raised, the text message in
the super method is outputted, but i've tested that
and it doesn't outputsuper([0,]...[n]) calls a constructor in the superclass of your current class matching the signature super([0,]...[n]). In this particular case, the Exception's message property is being set by the parent constructor. If you were to leave out super([0,]...[n]), the default no-arg constructor of the superclass would be invoked, and the message would not be set.
Use the getMessage() method of the Exception class to return the message value in later references to your object.

How to Maintain Translation of texts of Exception Class

Hi Experts,
I have an exception class ZCX_CHECK . I have maintained a text in the text tab of the exception class
like No components Exists in Package &PACKAGE_NAME&
PACKAGE_NAME is the Attribute . How do I maintain Translation of the TEXT. When I navigate like Goto->Translation , it is saying Empty Object list.
When I maintain text elements and give text-001 in the text tab of the exception class , the ouptu is coming as text-001 in the Report .
How do I amintain translation , or how can I integrate a message class with an exception class .I know where to metion messsage class . But how do I use it inside exception class

Let me rephrase this: When entering a text in your Exception class it will be automatically part of the OTR. You can check this by looking this up in SOTR_EDIT.Press the binoculars button (Find), and search on package (development class).
Now via SE63: Translation->ABAP Objects->Short texts
open node OT on pop-up and double click on Subnode.Enter a * on screen for Object name and press F4. Now enter collection (package / development) class. Select the text to be translated.
BTW: Via SOTR_EDIT you can retrieve the logical key (field concept) which is needed for translation. Select the GUID (logical key / concept) from SOTR_EDIT.

Creating own Exception class

In my past paper it says...
Show how to create your own Exception class that derives from class Exception. The class should provide a default constructor which allows a "My Error message" message to be set, and a second constructor which has as an argument the error message. 4-MARKS
Does this look right..?
public class MyExcep extends Exception
     public MyExcep()
          super("My Error Message");
     public MyExcep(String message)
          super(message);
}

Yes. Do I get 4 marks now? or is it Four Marks?

How to enhance exception class based on CX_ROOT

I have created an exception class based on CX_ROOT (or CX_STATIC_CHECK, CX_DYNAMIC_CHECK). Now, I need to enhance its "constructor" method with my own parameters. How can I do this? Currently system does not allow this. But, I have seen many other exception classes enhanced the way I want? Any idea?
Any pointers will be helpful.
Regards, Neetu

Hello Neetu
Two steps are required to get additional IMPORTING parameters in the CONSTRUCTOR method of your exception class:
(1) Create exception IDs (tabstrip Texts )
Example: ID=ZCX_SDN_CLASS, text=Invalid data type for field &FIELD& on screen &SCREEN& &REPORT&
(2) Add corresponding instance attributes (read-only) to your exception class
Examples: attributes FIELD, SCREEN, REPORT
Now the CONSTRUCTOR has the additional IMPORTING parameters FIELD, SCREEN and REPORT.
If you raise your exception class using id=ZCX_SDN_CLASS then the wildcards (e.g. &FIELD& in the text) will be replaced by IMPORTING parameter FIELD.
Regards
Uwe

How to use user defined exception class

Hi all
I just need som help with creating a user defined exception class.
Im writing a small/simple text editor.
My exception class looks like this:
public class myExcp extends Throwable
     private String message;
     public myExcep(String message)
          this.message = message;
     public void display()
          System.out.println(message);
I would like to use it when a user tries to open a exe-file instead of a txt file.
Here is some code from the editor:
if (e.getSource() == open)
saveOld();
if (fc.showOpenDialog(null)== JFileChooser.APPROVE_OPTION)
readFile(fc.getSelectedFile().getAbsolutePath());
saveas.setEnabled(true);
So, should I use exception here or at the readFile method?
readfile:
private void readFile(String fileName)
try
String tmp = fileName.substring(fileName.length() -4, fileName.length());
if (!tmp.equals(".exe"))
FileReader r = new FileReader(fileName);
textarea.read(r, null);
r.close();
currentFile = fileName;
label.setText(currentFile);
changed = false;
catch (IOException e)
JOptionPane.showMessageDialog (this, "Cannot find the file " + fileName);
Where and how do I use my exception class.
Do I need to create an instance? Where?
Should the exception class extend Exception instead?
Thank you in advance /

Extend Exception, not Throwable. It's a checked exception that way.
Follow the Sun coding standards and make that exception class name start with a capital letter.
When you extend Exception, override all four ctors.
What's that display method you added? Isn't getMessage() good enough?
You need to create a new instance just before you throw the exception, of course.
Sounds like a terrible design, by the way. Exceptions shouldn't be used like "go to" for app logic. They should signal unrecoverable conditions. You can easily recover from the situation you've described simply by displaying a pop-up that tells the user to open only text-readable file types. I think that's a better solution.
%

How I build my own libraries of classes/methods in java ?

How I build my own libraries of classes/methods in java ? how then I refer a functionX() (i mean method) in LibraryX ? can you give a short/brief example of a library with a class with a method and a main method of normal class calling this method (of external's added library's) ?

Just another cross poster.
[http://www.java-forums.org/new-java/12389-how-i-build-my-own-libraries-classes-methods-java.html]
db
edit And [http://forums.java.net/jive/thread.jspa?messageID=305387]
Edited by: Darryl.Burke

Making Own Exception Class

Hi all,
I m trying to make a new exception class which will be called when when any sort of exception occurs.After throwing that class how can i call other exception in that class eg. if in a class if sqlexception occurs & i m throwing myclass so how can i catch sqlexception in myclass.

if in a class if sqlexception occurs & i m throwing myclass so how can i catch sqlexception in myclass.
you can throw your class object only when you catch the original exception. so pass the oroginal exception object in the constructor of your exception class.
hope you get what i mean.
- Azodious

N00b query: Why would anyone ever want to define their own Exception class?

I've been reading thru my Java textbook for the past couple hours.
Exceptions are a wonderful thing. I already found several instances where I could've implemented try/cacth in my earlier programs.
Anyway, getting back to the point. My question is, can someone give me a realistic situation/example where a custom Expcetion class is REQUIRED? (the key word here is "required"!)
I can see why someone would want to have his own Exception class..... e.getMessage() as custom error messages are SO DAMN COOL!!!!!! :P
hehe
But seriously, if you are making intermidiate/advanced Java programs, would you ever REQUIRE to make your own Exception class? Afterall, even a custom made Exception class always "extends" from a pre-defined Java class, right?
Let me make this a bit more clear... public class CustomException extends IOException{ }Now, if I am making a try/catch statement, I can simply say
try{
throw new CustomException;
catch (IOException e) { }
Now as you can see, the CustomException was caught by the catch claus, because IOException is the superclass of CustomException. So, in other words, the whole CustomException thingy didnt do anything useful.
I know I know, I am so naive. Enlighten me >.<

Sure. Say you want to have a system where you want to include a custom error code which maps to some internationalized error messages. You would create an Exception subclass with a field to hold that value separate from the normal "default" message. Then you could throw that exception in all your code. Other code can catch it as a plain Exception if they want and use the "default" message, which is okay if they don't really care about the error code.
I don't think you are ever "required" to make your own exceptions. I have done so, but I don't often. It depends. See, there are plenty of Exception subclasses in the standard packages, and most of them cover many of the things you need. So more often if I'm throwing an exception, I'll be using the already existing ones, like IllegalArgumentException or IOException (whatever is relevant to the code).
Yes, you can do what you did below with CustomException. However the reason you might do that is cuz you really want to do this:
try {
   // call some code that may throw IOException from some standard IO package
   // or may throw CustomException from some of my methods...
} catch (CustomException ce) {
   // handle cusotm exception
} catch (IOException ioe) {
   // handle IO exception
}Cuz you may want to differentiate between your exceptions vs. IOExceptions that might be thrown from some java.io class.
Usually when you use an exception class it's a named class that relates to some condition. It may hold additional information besides the standard message, but I think most of the time it's just the class name which describes the problem. And if there isn't one that describes the problem that you're code might encounter, then create a subclass.

How to create message based exception class?

Hi Guys,
I try to create exception class at Workbech (se24), for example ZCX_TEST. At header information everything is default, but radiobutton "Exception class" is set and checkbox "With message class" is set. After this I enter text for my exceptions, for example TEXT, I assign it to SAP message (for example, class 00, message number 002). I'm going to tabstrip "Attributes" and public constant with name "TEST" should appear with assigned associated type SOTR_CONC and initial value with ID (normal behavior), but attribute "TEST" is created without type and value. It is not possible to use such exception. Where I am wrong?
Regards,
Evgeni

Hmmm. It looks that it works fine with such definitions. Sorry for disturbs.

Create a Exception Class

hi all ,,
can any one tell me how to create a exception class in ABAP OOPS concept ??
if possible can give link also for document

HI Jayakumar,
Please go thru this document
Exceptions are represented by objects that are instances of exception classes. Defining an exception is, therefore, the same as creating an exception class.
All exception classes must inherit from the common superclass CX_ROOT and one of its subordinate classes:
CX_STATIC_CHECK
CX_DYNAMIC_CHECK
CX_NO_CHECK
. The assignment of exception classes to one of these three paths of the inheritance hierarchy determines the way in which the associated exceptions are propagated. There is a record of predefined exception classes CX_SY_... whose exceptions are raised in error situations in the runtime environment. These classes all inherit from CX_DYNAMIC_CHECK or CX_NO_CHECK but not from CX_STATIC_CHECK (see hierarchy in the ABAP keyword documentation).
All exception classes must begin with the prefix CX_. They are usually defined globally with the Class Builder of the ABAP Workbench. Local exception classes can, however, also be defined.
Individual (abstract) exception classes that are used as the superclass of further exception classes can be defined. The exceptions of the subordinate classes can be handled together using a superclass.
Exception classes have the following features:
Constructor
The constructor must have a predefined structure and a specific interface. With global classes, the Class Builder generates the correct constructor and sets it to an unchangeable status. The constructor has two IMPORTING parameters:
TEXTID of the SOTR_CONC type
This parameter can be used to determine which of your exception texts the exception will use.
PREVIOUS of the CX_ROOT type
This parameter can be used to assign the PREVIOUS attribute a previous exception.
Methods
In exception classes, you can define your own methods. The following two predefined methods are inherited from the root class CX_ROOT:
GET_TEXT
Sends back the exception texts of a class (controlled by the TEXTID attribute) as a string.
GET_SOURCE_POSITION
Returns the program name, the name of a possible include program, and the line number of the statement that raised the exception.
Attributes
The attributes of exception classes are used to transport additional information on an error situation to the handler. The main piece of information is, however, always the fact that an exception of a particular class has occurred. The following attributes are inherited from CX_ROOT:
TEXTID
Used to specify the exception of a class more precisely by using several exception texts. Is evaluated in the GET_TEXT method.
PREVIOUS
If an exception is mapped to another exception, a reference to the original exception can be defined in this attribute via the EXPORTING addition of the RAISE EXCEPTION statement and by means of the constructor IMPORTING PARAMETER with the same name. This can result in a chain of exception objects. In the event of a runtime error, the exception texts of all the exceptions in the chain are output. Mapping an exception to another exception is only beneficial if the context in which the original exception occurred is important for characterizing the error situation.
KERNEL_ERRID
The name of the associated runtime error is stored in this attribute if the exception was raised by the runtime environment, for example, COMPUTE_INT_ZERODIVIDE with a division by zero. If the exception is not handled, precisely this runtime error occurs.
Parameters cannot be transferred to the constructor for this attribute. If the exception is raised with RAISE EXCEPTION, the attribute is set to initial.
Global Exception Classes
Global exception classes are defined and managed in the Class Builder. If the correct naming convention (prefix CX_) and the class type Exception Class is chosen when a new class is created, the Class Builder automatically becomes the Exception Builder.
The Exception Builder offers precisely the functionality required to define exception classes and generates independently-defined components that must not be changed. When classes are created, the category of the exception must be specified, in other words, whether it is to inherit from CX_STATIC_CHECK, CX_DYNAMIC_CHECK, or CX_NOCHECK.
Tab Pages of the Exception Builder
The Exception Builder has the tab pages Properties, Attributes, Methods, and Texts.
The properties do not normally need to be changed.
Except for the four inherited attributes mentioned above, further public attributes can be generated by the Exception Builder. The contents of these attributes specify the exception more clearly and manage the exception texts.
All of the methods are inherited from CX_ROOT. New methods cannot be added. The instance constructor is generated automatically. It ensures that, when an exception is raised, the attributes have the right values. It also transfers the text of the superclass for an exception class whose exception text is not specified explicitly.
The instance constructor is generated on the basis of the attributes, which are set up on the basis of the exception texts. Changing the attributes in superclasses can, therefore, invalidate the constructors of subordinate classes. The constructors of subordinate classes can be regenerated under Utilities ® CleanUp ® Constructor.
Texts are a special feature of exception classes and the Exception Builder. For further information, refer to Exception Texts.
Local Exception Classes
Local exception classes can be defined for specific exceptions that only occur within one single ABAP program. The condition for a local exception class is that it inherits from one of the three classes CX_STATIC_CHECK, CX_DYNAMIC_CHECK, or CX_NO_CHECK, or from their subordinate classes. An individual constructor and individual attributes can be created. Individual methods should not be created, however, and the methods of superclasses should not be redefined.
Examples of Local Exception Classes
report DEMO_LOCAL_EXCEPTION_1.
class CX_LOCAL_EXCEPTION definition
                        inheriting from CX_STATIC_CHECK.
endclass.
start-of-selection.
    try.
      raise exception type CX_LOCAL_EXCEPTION.
    catch CX_LOCAL_EXCEPTION.
      message 'Local Exception!' type 'I'.
endtry.
This example shows a minimal local exception class, which is simply the local representation of one of the three direct subordinate classes of CX_ROOT. It can be used in the program.
report DEMO_LOCAL_EXCEPTION_2.
class CX_LOCAL_EXCEPTION definition
                        inheriting from CX_STATIC_CHECK.
public section.
    data LOCAL_TEXT type STRING.
    methods CONSTRUCTOR importing TEXT type STRING.
endclass.
class CX_LOCAL_EXCEPTION implementation.
method CONSTRUCTOR.
    SUPER->CONSTRUCTOR( ).
    LOCAL_TEXT = TEXT.
endmethod.
endclass.
data OREF type ref to CX_LOCAL_EXCEPTION.
start-of-selection.
    try.
      raise exception type CX_LOCAL_EXCEPTION
                      exporting TEXT = `Local Exception`.
    catch CX_LOCAL_EXCEPTION into OREF.
      message OREF->LOCAL_TEXT type 'I'.
endtry.
In this example, the exception class from the previous example is extended to include an individual attribute and constructor. The IMPORTING parameter of the constructor must be supplied when the exception is raised (it is required here). The attribute can be evaluated in the handler of the exception.
report DEMO_LOCAL_EXCEPTION_3.
class CX_LOCAL_EXCEPTION definition
      inheriting from CX_SY_ARITHMETIC_ERROR.
public section.
    methods CONSTRUCTOR importing SITUATION type STRING.
endclass.
class CX_LOCAL_EXCEPTION implementation.
method CONSTRUCTOR.
    SUPER->CONSTRUCTOR( OPERATION = SITUATION ).
endmethod.
endclass.
data OREF type ref to CX_LOCAL_EXCEPTION.
data TEXT type STRING.
start-of-selection.
    try.
      raise exception type CX_LOCAL_EXCEPTION
            exporting SITUATION = `START-OF-SELECTION`.
    catch CX_LOCAL_EXCEPTION into OREF.
      TEXT = OREF->GET_TEXT( ).
      message TEXT type 'I'.
endtry.
In this example, an exception class is derived from one of the predefined exception classes for error situations in the runtime environment. An individual constructor is defined with an individual IMPORTING parameter that supplies the superclass constructor with this parameter. When the exception is handled, the exception text, as defined in the superclass, is read with GET_TEXT.

How to translate text elements in forms from type : pdf

does anybody know how to translate text elements
in pdf from english to other languages.
i tried the tran. se63 and filled in the desired language,
but there was no effect on the output ,
thanks,
ami

call this funcation. crate_text.
CALL FUNCTION 'CREATE_TEXT'
         EXPORTING
           FID               =
           FLANGUAGE         =
           FNAME             =
           FOBJECT           =
         SAVE_DIRECT       = 'X'
         FFORMAT           = '*'
         TABLES
           FLINES            =
       EXCEPTIONS
         NO_INIT           = 1
         NO_SAVE           = 2
         OTHERS            = 3
       IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
       ENDIF.

Exception class help

Hi,
i create exception class like it write in the sap help and when i want to send the exception with parameters to the ABOVE METHODS i don't susses i just get the message without the parameter ?
there is simple guideline how o transfer the exception with parameters?
br
Ricardo

HI Uwe,
Thanks,
This is my sample code:
This is the first method on the tree:
the method name is create .
INSERT (lt_table_name) FROM <ls_obj>.
    IF sy-subrc <> 0.
      RAISE EXCEPTION TYPE /cx_db_db_error
        EXPORTING
          textid     = cx_db_error=>create_failed
          table_name = lt_table_name.
    ENDIF.
this method call to the above method - create .
TRY.
        CALL METHOD lo_obj_create->create
          CHANGING
            is_bound_object = ls_obj_user.
      CATCH cx_db_error INTO lo_exc.
        "Create user failed. Throw an exception.
        RAISE EXCEPTION TYPE cx_db_error
          EXPORTING
            textid     = cx_db_error=>create_user_error
            previous   = lo_exc.
        result = lo_exc->get_text( ).
    ENDTRY.
here in result i just get the massage without the table name that i export in the first method ,what i miss here ?
Best Regards
Ricardo

BPEL 2.0 throws some of the faults as exceptions.. how do i handle them

hi All
I am using Jdev 11.1.1.6
There is something weird happening while i am trying to handle faults in BPEL 2.0..
Scenario: I am simply transfering data from one table to another and there is mismatch of the length in two tables i.e. target table have column with 30 length and source system is sending data of 40 length..
so i am expecting a BPEL Binding Fault for the same
but I am getting an exception from BPEL 2.0 for the same.. and it is not thrown as a fault to catch block.. Project gets Rolledback without throwing Fault to catch Block..
then i tried same with BPEL 1.1 and it gave me fault as expected in catch block which i could handle by sending fault notifications..
but BPEL 2.0 does not give me option of sending notifications as i do not get fault in Catch block..
Issue: How do i handle the fault in BPEL 2.0 when its throwing it as exception?????
Below is the trace i get from my instance with BPEL 2.0 and BPEL 1.1..
Getting Exception From BPEL 2.0 as below_: After throwing the exception process gets rolledback but instance is always in running mode
Non Recoverable System Fault :
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'merge' failed due to: DBWriteInteractionSpec Execute Failed Exception. merge failed. Descriptor name: [MergeItemDBAdapterV1.Item]. Caused by java.sql.BatchUpdateException: ORA-12899: value too large for column "ITEM"."ITEMNAME" (actual: 40, maximum: 30) . Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-12899" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
Exception i am getting in Invoke Activity but No Fault
<fault>
<exception class="com.collaxa.cube.engine.EngineException">
JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "520,633", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "520633" for process "BPELProcess2" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'merge' failed due to: DBWriteInteractionSpec Execute Failed Exception. merge failed. Descriptor name: [MergeItemDBAdapterV1.Item]. Caused by java.sql.BatchUpdateException: ORA-12899: value too large for column "ITEM"."ITEMNAME" (actual: 40, maximum: 30) . Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-12899" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. " . Consult the system administrator regarding this error.
<stack>
<f>com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive#107</f>
<f>com.collaxa.cube.ws.WSInvocationManager.invoke#352</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1070</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#584</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#132</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>
<f>com.collaxa.cube.engine.CubeEngine.performActivity#2687</f>
<f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1190</f>
<f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>
<f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#76</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#218</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4609</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4540</f>
<f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>
<f>...</f>
</stack>
</exception>
<root class="oracle.fabric.common.FabricInvocationException">
BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'merge' failed due to: DBWriteInteractionSpec Execute Failed Exception. merge failed. Descriptor name: [MergeItemDBAdapterV1.Item]. Caused by java.sql.BatchUpdateException: ORA-12899: value too large for column "ITEM"."ITEMNAME" (actual: 40, maximum: 30) . Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-12899" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
<stack>
<f>oracle.integration.platform.blocks.adapter.fw.jca.cci.EndpointInteractionException.getFabricInvocationException#75</f>
<f>oracle.integration.platform.blocks.adapter.AdapterReference.getFabricInvocationException#307</f>
<f>oracle.integration.platform.blocks.adapter.AdapterReference.post#293</f>
<f>oracle.integration.platform.blocks.mesh.AsynchronousMessageHandler.doPost#142</f>
<f>oracle.integration.platform.blocks.mesh.MessageRouter.post#197</f>
<f>oracle.integration.platform.blocks.mesh.MeshImpl.post#215</f>
<f>sun.reflect.GeneratedMethodAccessor1455.invoke</f>
<f>sun.reflect.DelegatingMethodAccessorImpl.invoke#25</f>
<f>java.lang.reflect.Method.invoke#597</f>
<f>org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection#307</f>
<f>org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint#182</f>
<f>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed#149</f>
<f>oracle.integration.platform.metrics.PhaseEventAspect.invoke#71</f>
<f>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed#171</f>
<f>org.springframework.aop.framework.JdkDynamicAopProxy.invoke#204</f>
<f>$Proxy315.post</f>
<f>...</f>
</stack>
</root>
</fault>
Getting Exception as well as Fault from BPEL 1.1 as below_
->Here i am getting exception as above
Non Recoverable System Fault :
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'merge' failed due to: DBWriteInteractionSpec Execute Failed Exception. merge failed. Descriptor name: [MergeItemDBAdapterV1.Item]. Caused by java.sql.BatchUpdateException: ORA-12899: value too large for column "ITEM"."ITEMNAME" (actual: 40, maximum: 30) . Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-12899" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
->and here is the fault thrown by BPEL 1.1
Non Recoverable System Fault :
<bpelFault><faultType>0</faultType><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'merge' failed due to: DBWriteInteractionSpec Execute Failed Exception. merge failed. Descriptor name: [MergeItemDBAdapterV1.Item]. Caused by java.sql.BatchUpdateException: ORA-12899: value too large for column "ITEM"."ITEMNAME" (actual: 40, maximum: 30) . Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-12899" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name="detail"><detail>ORA-12899: value too large for column "ITEM"."ITEMNAME" (actual: 40, maximum: 30) </detail></part><part name="code"><code>12899</code></part></bindingFault></bpelFault>
Fault i am getting in Invoke Activity
<fault>
<bpelFault>
<faultType>0</faultType>
<bindingFault>
<part name="summary">
<summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'merge' failed due to: DBWriteInteractionSpec Execute Failed Exception. merge failed. Descriptor name: [MergeItemDBAdapterV1.Item]. Caused by java.sql.BatchUpdateException: ORA-12899: value too large for column "ITEM"."ITEMNAME" (actual: 40, maximum: 30) . Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-12899" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary>
</part>
<part name="detail">
<detail>ORA-12899: value too large for column "ITEM"."ITEMNAME" (actual: 40, maximum: 30) </detail>
</part>
<part name="code">
<code>12899</code>
</part>
</bindingFault>
</bpelFault>
</fault>
Please suggest..

I sorted out what is happening..
When My Target DB is Empty and Merge operation is executed , Fault is thrown and catch block was able to catch it
And When My Target DB is having Values, It is thrown as Exception.. i.e. no fault to Catch block :(
Someone have any idea, hoe this can be resolved???
Edited by: 910947 on Aug 31, 2012 1:43 AM

Can we extend the Throwable class instead of Exception Class??

Hi all..
Can we extend the Throwable class instead of Exception Class while creating our own custom Exception?If not Why?
Please give your valuble advices..
Ramesh.

I don't want to hijack the thread here, but in a conversational tone...on a related note.. I've thought about this too a bit and wondered if there are some recommended practices about catching and handling Throwable in certain applications. Like the other day I was debugging a web application that was triggering a 500. The only way I could find the problem in an error stack was to write code to catch Throwable, log the stack, and then re-throw it. I considered it "debug" code, and once I solved the problem I took the code out because, my understanding is, we don't want to be handling runtime problems... or do we? Should I have a catch clause for Throwable in my servlet and then pass the message to ServletException?
So along with the OP question, are there separate defined occasions when we should or should not handle Throwable? Or does it just all depend on circumstance?

Own ZCX Exception Class, how to translate

Similar Messages

Maybe you are looking for