Why no compiler error is generated ?
When I try to store value 0xff in a byte variale with the statement :
byte b=0xff;
a compiler error is generated
but when I try to store the value 0xffffffff in b no complier error occurs.
The quetion is if the compiler can truncate bits in case of value 0xffffffff then why not in case of 0xff.
sharmaneha wrote:
but the question is why does not the compiler truncate the value for 0xff?That's 255, which is more than 127, which is the max value for a byte (they can be between -128 and 127)
Similar Messages
-
Compilation error while generating the form in linux
Hello everyone,
I am using Oracle Designer ver10.1.2.4 in windows to generate the forms with standard object library ofgwebol.olb and template form ofgwebt.fmb. form (with both .fmb and .fmx files) are generated without errors. Also when I open the forms in separately they compiles without errors. But when I copy the same .fmb file into linux enviroment and compile it using frmcmp.sh userid=user/password@database module_type=form compile_all=yes module=form_name it gives following errors.
$> frmcmp.sh userid=odin/odin@ontw10g module_ty
pe=form compile_all=yes module=LOGIN_SCHERM
Forms 10.1 (Form Compiler) Version 10.1.2.0.2 (Production)
Forms 10.1 (Form Compiler): Release - Production
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
PL/SQL Version 10.1.0.4.2 (Production)
Oracle Procedure Builder V10.1.2.0.2 - Production
Oracle Virtual Graphics System Version 10.1.2.0.0 (Production)
Oracle Multimedia Version 10.1.2.0.2 (Production)
Oracle Tools Integration Version 10.1.2.0.2 (Production)
Oracle Tools Common Area Version 10.1.2.0.2
Oracle CORE 10.1.0.4.0 Production
FRM-18108: Failed to load the following objects.
Source Module:ofgwebol.olb
Source Object: CGSO$CHAR_DO
Source Module:ofgwebol.olb
Source Object: CGSO$CHAR_DO
Source Module:ofgwebol.olb
Source Object: CGSO$BLOCK
Source Module:ofgwebol.olb
Source Object: CGSO$CANVAS
Source Module:ofgwebol.olb
Source Object: CGSO$WINDOW
Compiling function CGTE$CHECK_CONSTRAINT_VIO...
No compilation errors.
Compiling procedure CGTE$INLOGGEN_ERRORS...
No compilation errors.
L/SQL ERROR 0 at line 17, column 3
Statement ignored
PL/SQL ERROR 201 at line 36, column 3
identifier 'CGNV$.NAV_CLOSE_FORMS' must be declared
PL/SQL ERROR 0 at line 36, column 3
Statement ignored
PL/SQL ERROR 201 at line 37, column 3
identifier 'CGNV$.NAV_OPENING_WND' must be declared
PL/SQL ERROR 0 at line 37, column 3
Statement ignored
Compiling KEY-HELP trigger on form...
No compilation errors.
Compiling WHEN-WINDOW-ACTIVATED trigger on form...
Compilation error on WHEN-WINDOW-ACTIVATED trigger on form:
PL/SQL ERROR 201 at line 6, column 8
identifier 'CGNV$GET_ITEM_WINDOW' must be declared
PL/SQL ERROR 0 at line 4, column 3
Statement ignored
Compiling POST-TEXT-ITEM trigger on form...
Compilation error on POST-TEXT-ITEM trigger on form:
PL/SQL ERROR 201 at line 4, column 3
identifier 'CGNV$.STORE_WND_ITEM' must be declared
PL/SQL ERROR 0 at line 4, column 3
Statement ignored
Compiling WHEN-WINDOW-CLOSED trigger on form...
Compilation error on WHEN-WINDOW-CLOSED trigger on form:
PL/SQL ERROR 201 at line 5, column 3
identifier 'CGNV$.TERMINATE_WINDOW' must be declared
PL/SQL ERROR 0 at line 5, column 3
Statement ignored
Compiling WHEN-FORM-NAVIGATE trigger on form...
Compilation error on WHEN-FORM-NAVIGATE trigger on form:
PL/SQL ERROR 201 at line 3, column 3
identifier 'CGNV$.REMOVE_CHILD_FORM' must be declared
PL/SQL ERROR 0 at line 3, column 3
Statement ignored
Compiling KEY-EXIT trigger on form...
Compilation error on KEY-EXIT trigger on form:
PL/SQL ERROR 201 at line 5, column 3
identifier 'CGNV$.NAV_ENTER_QUERY' must be declared
PL/SQL ERROR 0 at line 5, column 3
Statement ignored
PL/SQL ERROR 201 at line 9, column 5
identifier 'CGNV$.CLOSE_ALL_WINDOWS' must be declared
PL/SQL ERROR 0 at line 9, column 5
Statement ignored
Compiling KEY-CLRFRM trigger on form...
No compilation errors.
Compiling ON-ERROR trigger on INLOGGEN data block...
No compilation errors.
Compiling KEY-PREV-ITEM trigger on AGB_ID item in INLOGGEN data block...
Compilation error on KEY-PREV-ITEM trigger on AGB_ID item in INLOGGEN data block
PL/SQL ERROR 201 at line 4, column 3
identifier 'CGNV$GO_PREV_ITEM' must be declared
PL/SQL ERROR 0 at line 4, column 3
Statement ignored
Compiling KEY-NEXT-ITEM trigger on AGB_NAAM item in INLOGGEN data block...
Compilation error on KEY-NEXT-ITEM trigger on AGB_NAAM item in INLOGGEN data blo
ck:
PL/SQL ERROR 201 at line 4, column 3
identifier 'CGNV$GO_NEXT_ITEM' must be declared
PL/SQL ERROR 0 at line 4, column 3
Statement ignored
Compilation errors have occurred.
Form not created
I think some standard library are missing in Linux environment. But I do not know the name of them and neither I can find. Please suggest the what need to be done to resolve the problem. The reason I am compiling the form in Linux is that I can run the form in windows because of corrupted installation of OC4j.
Thanking you all much in advance.
Edited by: Deepank on Dec 2, 2008 1:49 AMDeepank-
When generating forms from Designer, Designer attaches libraries - like ofgmes.pll, ofgnavl.pll, etc. You will need to copy these libraries to the same directory where your forms reside on your Linux box. To find out what libraries ate attached to your form, open it on your windows PC after generating it from Designer and you will see the attached libraries. Also, watch out for the case-sensitivity of Linux. If you have the Designer libraries on your linux box and you still get errors, try changing the case of the names of the libraries.
Hope this helps,
Dan -
Why no compile error in this code ?
strings are immutable... we can not alter it... so why the below does not create compile error ? it is an attempt to alter the string.
class test
public static void main(String args[])
String s1 = new String("amit");
s1.concat("Poddar"); // why no error ?
System.out.println(s1);
}strings are immutable... we can not alter it... so
why the below does not create compile error ? First of all, Strings are immuatable because the String class is coded that way - there willnever be a compiler error to stop you from altering a String's value (which is actually possible via reflection). This is similar to you writing your own class that has a private field and not providing any methods that can alter the field's value. Your new class would be considered immutable in the same way that Strings are considered immutable, and nobody can even attempt (except reflectively), to "alter" an instance of it, so there will never be a compiler error that is due to such an attempt.
it is an attempt to alter the string.No it isn't. The following is a quote from the Javadoc for String.concat:
"If the length of the argument string is 0, then this String object is returned. Otherwise, a new String object is created, representing a character sequence that is the concatenation of the character sequence represented by this String object and the character sequence represented by the argument string." -
Why not compile error on "incompatible interface cast"?
simeple code here
class IncompInterfaceTest {
void doTest() {
ClassB b = new ClassB();
InterfaceA a = (InterfaceA)b;
interface InterfaceA{}
class ClassB{}
javac issues "ClassCastException" on runtime rather than compile
error.
as i know incompatible type casting may be caught at runtime and
compiler shows the error.
but why compiler doesn't do it's job for interfaces? it's just so
clear to be compile error to me.
ps. in a case ClassB is final class, compiler issues a error.
(a thread I started in google groups)
http://groups.google.co.kr/group/comp.lang.java.programmer/browse_thread/thread/c9c12a8864672436?hl=ko#sun9h0st wrote:
thanks for reply.
I think i might know something wrong about class, object concept, so I wish you tell me more about it.
As I though the code below means
ClassB b = new ClassC();'b' can be an Object of ClassB as a subclass of ClassC.
'b' IS an Object of ClassC.b is not an object.
b is a variable that can point to an instance of ClassB or to an instance of any subclass of ClassB.
>
so
b instanceof ClassB == true // as it can be
b instanceof ClassC == true // as it is
If b is not null, the first line will always be true.
If b points to a ClassC or a subclass, the second one will be true.
It means actual Object(something behind 'b' pointing, i don't know what i call it) is from ClassC to me. (somewhat like c pointer,
'b' is a bowl that called Object and actuall instance is refered by 'b')No idea what you're saying here.
if b IS an Object of ClassB
shouldn't "b instanceof ClassC" is false?If we have C extends B, then...
B b1 = new B();
B b2 = new C();
b1 instanceof B // true
b1 instanceof C // false
b2 instanceof B // true
b2 instanceof C // true
I Think compiler should be known that instance 'b' hold. No, it doesn't, and it's good that it doesn't, as it keeps the language simpler and more consistent.
Also, b doesn't hold an instance. It holds a reference to an instance. -
J2EE deploytool compile error in generated code.
I write and compile all the code for EJB.
Created .EAR and .WAR files needed for deploy. But when the deploy application tries to generated and compile stub code there is a compilation problem.
Anyone knows how can I solve this? or this is a problem of the deploy app, Is there another one?
I'm using J2EE SDK 1.3 beta version.
THANKS...It's not an Exception. Are compile errors of the generated code.
When you make "Deploy..." from "Tools" menu item of the "Application Deployment Tool", it make some task including source generation and its compilation, so, this compilation have errors. -
Fpga compile error Process "Generate Programming File" failed
When I tried to compile any fpga vi. It always end up with this kind of error:
WARNING:Bitgen:26 - Bitgen only supports DRC but not bitstream generation on
this device. This condition can occur if there are problems obtaining a
license to run bitgen or if the design targets a device which is Early
Access.
Process "Generate Programming File" failed
Even when i tried the example vi given by NI.
However when i select the FPGA target pxi-7831R, it succeed. Other fpga targets like pxi7853R pxie7965R or Pxie7953R don't work well.
PS: i use labview 2011 NI-RIO 4.0 and xilinx tools 13.4Hello,
The key will of course be to isolate differences between your machines.
I wonder if the following more specific language setting could be the lingering problem. LabVIEW is a non-unicode program, and there is a language setting in Windows (at least XP) specifically for non-unicode programs. Try the following (or it's Win2K equivalent) if you haven't already:
0. Open "Control Panel"
1. Open the "Regional and Language Options"
2. On the Advanced tab, choose English (United States) from the drop-down menu under the top section "Language for non-Unicode Programs"
- This language setting is different from the setting on the "Regional Options" tab.
Any other differences you can isolate would be potentially insightful - if you have the same software versions installed in the same order on both machines, we may be looking for something a bit subtle, such as the suspected language setting.
Best Regards,
JLS
Best,
JLS
Sixclear -
Compile Errors when Generating Conditional Tag Help File
Ok, here is a recap of everything I have done. I started over from scratch. Unzipped the Help File into C:\Users\edwinwood\Documents\My RoboHelp Projects\Adobe RoboHelp 9 folder. Went to the properties SSOL Help Development folder and unchecked read only. Opened RoboHelp 9 as an administrator, went to File->Open and opened the help file. The first thing that pops up is a message stating this is a help file made with an older version of RoboHelp(v8) and must be upgraded(v9). I hit ok. The next pop-up is this “Unable to connect to the project $/SSOL HelpDevelopment@:ROBOSOURCE in version control. Would you like to browse for it?” I hit yes and the next pop-up just asks do you want to discontinue connection attempts in the future. I hit no. After that is usually where the files that are write protected pop-up but they didn’t this time. After about 5 minutes It will say upgrade complete. I shut down RoboHelp go into the language folder copy the robohhre.lng and paste it into the root folder. Like I said this file has nothing in it. I reopen RoboHelp as an administrator and open the project again. I then go to View->Pods->Single Source Layouts. Double click the Tag1 Remove Hickory Tech and then click save and generate. At the very end of the compile process I still get Template Errors...
Applying WebHelp 5.50 Template...
Template Error: can not resolve macro: WH_LNG_LoadingData
...Template Error: can not resolve macro: WH_LNG_MergeError1
Template Error: can not resolve macro: WH_LNG_MergeError2
Template Error: can not resolve macro: WH_LNG_JS_alert_ProjectLoadingFail
...Template Error: can not resolve macro: WH_LNG_PreTooltip in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtopic.js
Template Error: can not resolve macro: WH_LNG_NextTooltip in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtopic.js
Template Error: can not resolve macro: WH_LNG_Show_Navigation_Component in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtopic.js
Template Error: can not resolve macro: WH_LNG_Hide_Navigation_Component in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtopic.js
Template Error: can not resolve macro: WH_LNG_Show_Navigation_Component in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtopic.js
Template Error: can not resolve macro: WH_LNG_Hide_Navigation_Component in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtopic.js
Template Error: can not resolve macro: WH_LNG_SyncTocTooltip in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtopic.js
.....Template Error: can not resolve macro: WH_LNG_IndexSelectTopicTitle
Template Error: can not resolve macro: WH_LNG_IndexSelectTopicLabel
.....Template Error: can not resolve macro: WH_LNG_LoadingContentsData
Template Error: can not resolve macro: WH_LNG_Book
Template Error: can not resolve macro: WH_LNG_Page
Template Error: can not resolve macro: WH_LNG_Remote_Page
....Template Error: can not resolve macro: WH_LNG_IndexBtnText
....Template Error: can not resolve macro: WH_LNG_SearchPrompt in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whfform.htm
Template Error: can not resolve macro: WH_LNG_SearchPrompt in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whfform.htm
Template Error: can not resolve macro: WH_LNG_SearchPrompt in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whfform.htm
Template Error: can not resolve macro: WH_LNG_FtsMaxResult
Template Error: can not resolve macro: WH_LNG_FtsBtnText
.....Template Error: can not resolve macro: WH_LNG_JS_alert_ErrorInLoading
....Template Error: can not resolve macro: WH_LNG_About in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whskin_banner.htm
Template Error: can not resolve macro: WH_LNG_Author in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whskin_banner.htm
Template Error: can not resolve macro: WH_LNG_PoweredBy in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whskin_banner.htm
Template Error: can not resolve macro: WH_LNG_GeneratedBy in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whskin_banner.htm
Template Error: can not resolve macro: WH_LNG_SearchPrompt in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtbar.js
Template Error: can not resolve macro: WH_LNG_ToolBarSearchBtnText in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtbar.js
Template Error: can not resolve macro: WH_LNG_Show_Navigation_Component in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtbar.js
Template Error: can not resolve macro: WH_LNG_Hide_Navigation_Component in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtbar.js
Template Error: can not resolve macro: WH_LNG_Hide_Navigation_Component in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtbar.js
Template Error: can not resolve macro: WH_LNG_SyncTocTooltip in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtbar.js
Template Error: can not resolve macro: WH_LNG_ContentCategoryList in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtbar.js
Template Error: can not resolve macro: WH_LNG_NextTooltip in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtbar.js
Template Error: can not resolve macro: WH_LNG_PreTooltip in C:\SSOL Tag1 Remove HickoryTech\WebHelp\whtbar.js
Finished applying Template in 40 sec(s)Ok, replaced the 0k .lng file with one that actually has something in it and I am down to one error.
Template Error: can not resolve macro: WH_LNG_ContentCategoryList
If anyone could help me with this one I would be much obliged -
I have a actionscript3 file,like follows:
package com.adobe.air.logging
import flash.filesystem.File;
import flash.filesystem.FileMode;
import flash.filesystem.FileStream;
import mx.core.mx_internal;
import mx.logging.targets.LineFormattedTarget;
public class FileTarget extends LineFormattedTarget // 50 Line
mx_internal override function internalLog(message:String):void // 73 Line
Then I use Adobe Flex Compiler (mxmlc) Version 4.5.0 build 20967 to compile it,but it raise following error:
C:\FileTarget.as(50): col: 34 Error: The definition of base class LineFormattedTarget was not found.
public class FileTarget extends LineFormattedTarget
^
C:\FileTarget.as(73): col: 33 Error: Method marked override must override another method.
mx_internal override function internalLog(message:String):void
I have import LineFormattedTarget,why raise above two errors? How to correct it. Source code is better.
ThanksIt would seem that the compiler can't find the mx.* packages. Check that the Flex SDK is in your classpath.
-
Why Internet Script Error is generating while importing .SWF file in Robohelp 5?
Hi!
I am using Robohelp version 5. I am trying a import a .SWF generated using Adobe Captivate into a file. I am getting the following error message. Can any one let me know what needs to be done?
Thanks in advance,
LathaHi,
I pasted the following code (This code was given in one of the discussions) in the true code to fix the error that is poping up while viewing the .chm file.
<p><object type ="application/x-shockwave-flash"id="object1" data ="../Menucheckmark.swf" style ="border:none; "width= "400" height ="300">
<param name = "movie" value ="../Menucheckmark.swf"/>
<param name = "quality" value ="high"/>
Loading multimedia control.... </object></p>
I changed the swf file name and pasted in the true code. After generating the file, the true code changes as shown below:
<p><object type="application/x-shockwave-flash"
id="object1"
data="../RTDC.swf"
style= "border:none;"width: "851";
height:"718";
<param name="movie" value="../RTDC.swf" />
<param name="quality" value="high" />
loading multimedia control.... </object></p>
But still I am getting the error message. Can anyone help me on this?
Thanks,
Latha -
Reports compilation errors (6i to 9i)
Hello,
When migrating a report from Oracle 6i to Oracle 9i, I get a number of errors.
Here are 2 sample functions and the associated errors at compile time:
function AfterReports return boolean is
begin
/* Delete referenced files */
update lot
set ref_file = null;
ref_filenum = null;
where co = :p_co
and (lot.surveyor = :p_surveyor or :p_surveyor is null)
and ref_filenum = :p_project;
/* Flag the project to indicate that work order as been printed */
update thproject
set prtwrkord = 'Y'
where co = :p_co
and nvl(prtwrkord,'N') = 'N'
and project = :p_project;
return (TRUE);
end;
When trying to compile this function under Reports Oracle 9i, I get the following errors:
Error 201 at line 4, column 11
identifier 'LOT' must be declared
Error 0 at line 4, column 4
SQL statement ignored
Error 201 at line 12, column 9
identifier 'TBPROJECT' must be declared
Error 0 at line 12, column 2
SQL Statement ignored.
=====
function BeforeReport return boolean is
trouver BOOLEAN;
CURSOR CURS is select c c.co
from company c, userco u
where c.co = u.co
and u.userid = user;
begin
open curs;
fetch curs into :p.co
trouver := curs%FOUND;
close curs;
return (trouver);
end;
Error 201 at line 4, column 12
identifier 'COMPANY' must be declared
Error 0 at line 3, column 20
SQL Statement ignored.
=====
1) How can I go about resolving these compilation errors and generate the corresponding *.REP file ?
PaoloAt first glance it seems to me that you are missing a comma between ref_file and ref_filenum as below
/* Delete referenced files */
update lot
set ref_file = null;
ref_filenum = null;
where co = :p_co
and (lot.surveyor = :p_surveyor or :p_surveyor is null)
and ref_filenum = :p_project;
should be:
/* Delete referenced files */
update lot
set ref_file = null,
ref_filenum = null;
where co = :p_co
and (lot.surveyor = :p_surveyor or :p_surveyor is null)
and ref_filenum = :p_project;
HTH -
Compilation errors in webutil.pll
Hi all,
I am trying to compile webutil.pll
But compilation errors are generated in all the packages
whose name start with JAVA_
what could be the reason?
And How can i solve this?
Forms Version- 9i
Webutil 106
Regards
Indu
Message was edited by:
InduDear Francois,
I am getting following error message while compiling webutil.pll
Compilation errors on JAVA_SYSTEM:
PL/SQL ERROR 306 at line 18, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 18, column 5
Statement ignored
PL/SQL ERROR 306 at line 20, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 20, column 5
Statement ignored
PL/SQL ERROR 306 at line 23, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 23, column 5
Statement ignored
PL/SQL ERROR 306 at line 30, column 12
wrong number or types of arguments in call to 'CALL_LONG_METHOD'
PL/SQL ERROR 0 at line 30, column 5
Statement ignored
PL/SQL ERROR 306 at line 38, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 38, column 5
Statement ignored
PL/SQL ERROR 306 at line 39, column 12
wrong number or types of arguments in call to 'CALL_INT_METHOD'
PL/SQL ERROR 0 at line 39, column 5
Statement ignored
PL/SQL ERROR 306 at line 48, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 48, column 5
Statement ignored
PL/SQL ERROR 306 at line 57, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 57, column 5
Statement ignored
PL/SQL ERROR 306 at line 68, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 68, column 5
Statement ignored
PL/SQL ERROR 306 at line 77, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 77, column 5
Statement ignored
PL/SQL ERROR 306 at line 88, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 88, column 5
Statement ignored
PL/SQL ERROR 306 at line 95, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 95, column 5
Statement ignored
PL/SQL ERROR 306 at line 104, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 104, column 5
Statement ignored
PL/SQL ERROR 306 at line 113, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 113, column 5
Statement ignored
PL/SQL ERROR 306 at line 122, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 122, column 5
Statement ignored
PL/SQL ERROR 306 at line 129, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 129, column 5
Statement ignored
PL/SQL ERROR 306 at line 136, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 136, column 5
Statement ignored
PL/SQL ERROR 306 at line 145, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 145, column 5
Statement ignored
PL/SQL ERROR 306 at line 152, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 152, column 5
Statement ignored
PL/SQL ERROR 306 at line 160, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 160, column 5
Statement ignored
PL/SQL ERROR 306 at line 161, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 161, column 5
Statement ignored
PL/SQL ERROR 306 at line 169, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 169, column 5
Statement ignored
PL/SQL ERROR 306 at line 170, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 170, column 5
Statement ignored
PL/SQL ERROR 306 at line 178, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 178, column 5
Statement ignored
PL/SQL ERROR 306 at line 179, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 179, column 5
Statement ignored
PL/SQL ERROR 306 at line 187, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 187, column 5
Statement ignored
PL/SQL ERROR 306 at line 188, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 188, column 5
Statement ignored
PL/SQL ERROR 306 at line 196, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 196, column 5
Statement ignored
PL/SQL ERROR 306 at line 197, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 197, column 5
Statement ignored
PL/SQL ERROR 306 at line 205, column 12
wrong number or types of arguments in call to 'CALL_INT_METHOD'
PL/SQL ERROR 0 at line 205, column 5
Statement ignored
PL/SQL ERROR 306 at line 213, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 213, column 5
Statement ignored
PL/SQL ERROR 306 at line 225, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 225, column 5
Statement ignored
PL/SQL ERROR 306 at line 233, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 233, column 5
Statement ignored
PL/SQL ERROR 306 at line 243, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 243, column 5
Statement ignored
PL/SQL ERROR 306 at line 252, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 252, column 5
Statement ignored
PL/SQL ERROR 306 at line 253, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 253, column 5
Statement ignored
PL/SQL ERROR 306 at line 261, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 261, column 5
Statement ignored
PL/SQL ERROR 306 at line 269, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 269, column 5
Statement ignored
PL/SQL ERROR 306 at line 277, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 277, column 5
Statement ignored
PL/SQL ERROR 306 at line 283, column 10
wrong number or types of arguments in call to 'GET_OBJECT_FIELD'
PL/SQL ERROR 0 at line 283, column 3
Statement ignored
PL/SQL ERROR 306 at line 286, column 11
wrong number or types of arguments in call to 'GET_OBJECT_FIELD'
PL/SQL ERROR 0 at line 286, column 3
Statement ignored
PL/SQL ERROR 306 at line 289, column 10
wrong number or types of arguments in call to 'GET_OBJECT_FIELD'
PL/SQL ERROR 0 at line 289, column 3
Statement ignored
Compilation errors on JAVA_FILE:
PL/SQL ERROR 306 at line 15, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 15, column 5
Statement ignored
PL/SQL ERROR 306 at line 17, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 306 at line 17, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 0 at line 17, column 5
Statement ignored
PL/SQL ERROR 306 at line 25, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 25, column 5
Statement ignored
PL/SQL ERROR 306 at line 26, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 306 at line 26, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 0 at line 26, column 5
Statement ignored
PL/SQL ERROR 306 at line 35, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 306 at line 35, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 0 at line 35, column 5
Statement ignored
PL/SQL ERROR 306 at line 46, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 306 at line 46, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 0 at line 46, column 5
Statement ignored
PL/SQL ERROR 306 at line 54, column 12
wrong number or types of arguments in call to 'CALL_INT_METHOD'
PL/SQL ERROR 0 at line 54, column 5
Statement ignored
PL/SQL ERROR 306 at line 63, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 63, column 5
Statement ignored
PL/SQL ERROR 306 at line 64, column 12
wrong number or types of arguments in call to 'CALL_INT_METHOD'
PL/SQL ERROR 0 at line 64, column 5
Statement ignored
PL/SQL ERROR 306 at line 73, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 73, column 5
Statement ignored
PL/SQL ERROR 306 at line 74, column 12
wrong number or types of arguments in call to 'CALL_INT_METHOD'
PL/SQL ERROR 0 at line 74, column 5
Statement ignored
PL/SQL ERROR 306 at line 83, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 83, column 5
Statement ignored
PL/SQL ERROR 306 at line 84, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 84, column 5
Statement ignored
PL/SQL ERROR 306 at line 92, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 92, column 5
Statement ignored
PL/SQL ERROR 306 at line 100, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 100, column 5
Statement ignored
PL/SQL ERROR 306 at line 108, column 12
wrong number or types of arguments in call to 'CALL_LONG_METHOD'
PL/SQL ERROR 0 at line 108, column 5
Statement ignored
PL/SQL ERROR 306 at line 116, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 116, column 5
Statement ignored
PL/SQL ERROR 306 at line 124, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 124, column 5
Statement ignored
PL/SQL ERROR 306 at line 132, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 132, column 5
Statement ignored
PL/SQL ERROR 306 at line 140, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 140, column 5
Statement ignored
PL/SQL ERROR 306 at line 148, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 148, column 5
Statement ignored
PL/SQL ERROR 306 at line 157, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 157, column 5
Statement ignored
PL/SQL ERROR 306 at line 158, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 158, column 5
Statement ignored
PL/SQL ERROR 306 at line 166, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 166, column 5
Statement ignored
PL/SQL ERROR 306 at line 174, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 174, column 5
Statement ignored
PL/SQL ERROR 306 at line 182, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 182, column 5
Statement ignored
PL/SQL ERROR 306 at line 190, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 190, column 5
Statement ignored
PL/SQL ERROR 306 at line 198, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 198, column 5
Statement ignored
PL/SQL ERROR 306 at line 209, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 209, column 5
Statement ignored
PL/SQL ERROR 306 at line 221, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 221, column 5
Statement ignored
PL/SQL ERROR 306 at line 222, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 222, column 5
Statement ignored
PL/SQL ERROR 306 at line 230, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 230, column 5
Statement ignored
PL/SQL ERROR 306 at line 238, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 238, column 5
Statement ignored
PL/SQL ERROR 306 at line 246, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 246, column 5
Statement ignored
PL/SQL ERROR 306 at line 254, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 254, column 5
Statement ignored
PL/SQL ERROR 306 at line 262, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 262, column 5
Statement ignored
PL/SQL ERROR 306 at line 270, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 270, column 5
Statement ignored
PL/SQL ERROR 306 at line 278, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 278, column 5
Statement ignored
PL/SQL ERROR 306 at line 286, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 286, column 5
Statement ignored
PL/SQL ERROR 306 at line 294, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 294, column 5
Statement ignored
PL/SQL ERROR 306 at line 302, column 12
wrong number or types of arguments in call to 'CALL_LONG_METHOD'
PL/SQL ERROR 0 at line 302, column 5
Statement ignored
PL/SQL ERROR 306 at line 311, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 311, column 5
Statement ignored
PL/SQL ERROR 306 at line 312, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 312, column 5
Statement ignored
PL/SQL ERROR 306 at line 321, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 321, column 5
Statement ignored
PL/SQL ERROR 306 at line 322, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 322, column 5
Statement ignored
PL/SQL ERROR 306 at line 330, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 330, column 5
Statement ignored
PL/SQL ERROR 306 at line 337, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 337, column 5
Statement ignored
PL/SQL ERROR 306 at line 345, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 345, column 5
Statement ignored
PL/SQL ERROR 306 at line 353, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 353, column 5
Statement ignored
PL/SQL ERROR 306 at line 362, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 362, column 5
Statement ignored
PL/SQL ERROR 306 at line 363, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 363, column 5
Statement ignored
PL/SQL ERROR 306 at line 373, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 373, column 5
Statement ignored
PL/SQL ERROR 306 at line 381, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 381, column 5
Statement ignored
PL/SQL ERROR 306 at line 389, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 389, column 5
Statement ignored
PL/SQL ERROR 306 at line 397, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 397, column 5
Statement ignored
PL/SQL ERROR 306 at line 409, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 409, column 5
Statement ignored
PL/SQL ERROR 306 at line 417, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 417, column 5
Statement ignored
PL/SQL ERROR 306 at line 427, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 427, column 5
Statement ignored
PL/SQL ERROR 306 at line 435, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 435, column 5
Statement ignored
PL/SQL ERROR 306 at line 443, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 443, column 5
Statement ignored
PL/SQL ERROR 306 at line 449, column 20
wrong number or types of arguments in call to 'GET_CHAR_FIELD'
PL/SQL ERROR 0 at line 449, column 3
Statement ignored
PL/SQL ERROR 306 at line 452, column 16
wrong number or types of arguments in call to 'GET_STRING_FIELD'
PL/SQL ERROR 0 at line 452, column 3
Statement ignored
PL/SQL ERROR 306 at line 455, column 24
wrong number or types of arguments in call to 'GET_CHAR_FIELD'
PL/SQL ERROR 0 at line 455, column 3
Statement ignored
PL/SQL ERROR 306 at line 458, column 20
wrong number or types of arguments in call to 'GET_STRING_FIELD'
PL/SQL ERROR 0 at line 458, column 3
Statement ignored
Compilation errors on JAVA_EXCEPTION:
PL/SQL ERROR 306 at line 15, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 306 at line 15, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 0 at line 15, column 5
Statement ignored
PL/SQL ERROR 306 at line 23, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 23, column 5
Statement ignored
PL/SQL ERROR 306 at line 24, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 306 at line 24, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 0 at line 24, column 5
Statement ignored
PL/SQL ERROR 306 at line 34, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 34, column 5
Statement ignored
PL/SQL ERROR 306 at line 35, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 306 at line 35, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 0 at line 35, column 5
Statement ignored
PL/SQL ERROR 306 at line 42, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 306 at line 42, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 0 at line 42, column 5
Statement ignored
PL/SQL ERROR 306 at line 51, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 51, column 5
Statement ignored
PL/SQL ERROR 306 at line 52, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 52, column 5
Statement ignored
PL/SQL ERROR 306 at line 61, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 61, column 5
Statement ignored
PL/SQL ERROR 306 at line 62, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 62, column 5
Statement ignored
PL/SQL ERROR 306 at line 70, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 70, column 5
Statement ignored
PL/SQL ERROR 306 at line 78, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 78, column 5
Statement ignored
PL/SQL ERROR 306 at line 86, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 86, column 5
Statement ignored
PL/SQL ERROR 306 at line 95, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 95, column 5
Statement ignored
PL/SQL ERROR 306 at line 96, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 96, column 5
Statement ignored
PL/SQL ERROR 306 at line 104, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 104, column 5
Statement ignored
PL/SQL ERROR 306 at line 112, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 112, column 5
Statement ignored
PL/SQL ERROR 306 at line 120, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 120, column 5
Statement ignored
PL/SQL ERROR 306 at line 128, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 128, column 5
Statement ignored
PL/SQL ERROR 306 at line 137, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 137, column 5
Statement ignored
PL/SQL ERROR 306 at line 138, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 138, column 5
Statement ignored
PL/SQL ERROR 306 at line 146, column 12
wrong number or types of arguments in call to 'CALL_INT_METHOD'
PL/SQL ERROR 0 at line 146, column 5
Statement ignored
PL/SQL ERROR 306 at line 154, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 154, column 5
Statement ignored
PL/SQL ERROR 306 at line 166, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 166, column 5
Statement ignored
PL/SQL ERROR 306 at line 174, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 174, column 5
Statement ignored
PL/SQL ERROR 306 at line 184, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 184, column 5
Statement ignored
PL/SQL ERROR 306 at line 193, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 193, column 5
Statement ignored
PL/SQL ERROR 306 at line 194, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 194, column 5
Statement ignored
PL/SQL ERROR 306 at line 202, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 202, column 5
Statement ignored
PL/SQL ERROR 306 at line 210, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 210, column 5
Statement ignored
Compilation errors on JAVA_APPSERV_WRITER:
PL/SQL ERROR 306 at line 13, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 306 at line 13, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 0 at line 13, column 5
Statement ignored
PL/SQL ERROR 306 at line 23, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 23, column 5
Statement ignored
PL/SQL ERROR 306 at line 33, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 33, column 5
Statement ignored
PL/SQL ERROR 306 at line 43, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 43, column 5
Statement ignored
PL/SQL ERROR 306 at line 51, column 12
wrong number or types of arguments in call to 'CALL_INT_METHOD'
PL/SQL ERROR 0 at line 51, column 5
Statement ignored
PL/SQL ERROR 306 at line 59, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 59, column 5
Statement ignored
PL/SQL ERROR 306 at line 69, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 69, column 5
Statement ignored
PL/SQL ERROR 306 at line 77, column 12
wrong number or types of arguments in call to 'CALL_INT_METHOD'
PL/SQL ERROR 0 at line 77, column 5
Statement ignored
PL/SQL ERROR 306 at line 85, column 12
wrong number or types of arguments in call to 'CALL_OBJECT_METHOD'
PL/SQL ERROR 0 at line 85, column 5
Statement ignored
PL/SQL ERROR 306 at line 97, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 97, column 5
Statement ignored
PL/SQL ERROR 306 at line 105, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 105, column 5
Statement ignored
PL/SQL ERROR 306 at line 115, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 115, column 5
Statement ignored
PL/SQL ERROR 306 at line 124, column 5
wrong number or types of arguments in call to 'ADD_OBJECT_ARG'
PL/SQL ERROR 0 at line 124, column 5
Statement ignored
PL/SQL ERROR 306 at line 125, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 125, column 5
Statement ignored
PL/SQL ERROR 306 at line 133, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 133, column 5
Statement ignored
PL/SQL ERROR 306 at line 141, column 5
wrong number or types of arguments in call to 'CALL_VOID_METHOD'
PL/SQL ERROR 0 at line 141, column 5
Statement ignored
PL/SQL ERROR 306 at line 149, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 149, column 5
Statement ignored
Compilation errors on JAVA_APPSERV_READER:
PL/SQL ERROR 306 at line 13, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 306 at line 13, column 13
wrong number or types of arguments in call to 'NEW_OBJECT'
PL/SQL ERROR 0 at line 13, column 5
Statement ignored
PL/SQL ERROR 306 at line 20, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 20, column 5
Statement ignored
PL/SQL ERROR 306 at line 32, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 32, column 5
Statement ignored
PL/SQL ERROR 306 at line 40, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 40, column 5
Statement ignored
PL/SQL ERROR 306 at line 48, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 48, column 5
Statement ignored
PL/SQL ERROR 306 at line 56, column 12
wrong number or types of arguments in call to 'CALL_INT_METHOD'
PL/SQL ERROR 0 at line 56, column 5
Statement ignored
PL/SQL ERROR 306 at line 64, column 12
wrong number or types of arguments in call to 'CALL_INT_METHOD'
PL/SQL ERROR 0 at line 64, column 5
Statement ignored
PL/SQL ERROR 306 at line 72, column 12
wrong number or types of arguments in call to 'CALL_INT_METHOD'
PL/SQL ERROR 0 at line 72, column 5
Statement ignored
PL/SQL ERROR 306 at line 80, column 12
wrong number or types of arguments in call to 'CALL_STRING_METHOD'
PL/SQL ERROR 0 at line 80, column 5
Statement ignored
PL/SQL ERROR 306 at line 90, column 12
wrong number or types of arguments in call to 'CALL_BOOLEAN_METHOD'
PL/SQL ERROR 0 at line 90, column 5
Statement ignored
Failed to generate library.
FRM-30312: Failed to compile the library.
Regards
Indu -
this procedure always generate compilation error listed below, I don't understand, anyone has a clue?? Thanks!!!
LINE/COL ERROR
3/18 PLS-00103: Encountered the symbol "(" when expecting one of the
following:
:= . ) , @ % default character
The symbol ":=" was substituted for "(" to continue.
create or replace procedure test1234 (
v_project projects.id%TYPE,
v_yesno char(1)) as
cursor c_table is
select table_name from user_tab_columns
where column_name = 'PRO_ID'
and table_name not like '%_DEL'
and table_name not like '%_REP'
and table_name not like 'USER_%'
and table_name not like '%_OLD'
and table_name not like '%_TEST'
and table_name not like 'DAVID%'
and table_name not like '%_BAK';
v_table varchar(30);
child_table varchar(30);
parent_table varchar(30);
v_count number(15);
l_count number(15);
child_count number(15);
tbl_count number(15);
beginYou must n ot specify the length of the string in the declaration.
Thats why line 3 has to be:
v_yesno char) asHTH
Jens -
Do java programms after giving compilation error generates .class file?
Do java programms after giving compilation error generates the .class file?
Do any outer class may have the private as access modifier?
If someone asks you that -do any program in java after giving a compilation error gives the .class file -do any class except(inner class)
be defined as private or static or protected or abc or xxx Now type the
following program
private class test
public static void main(String s[])
System.out.println("Hello!How are You!!");
-Compile it.... You must have
received this error test.java:1:The type type can't be private. Package members are always accessible within the current package. private class
test ^ 1 error
Here please notify that compiler has given the
error not the warning therfore .class file should not be created but now type
>dir *.class
___________ and you will see that the
test.class file existing in the directory nevertheless this .class file
is executable. if you will type __________________ >java test
it will
wish you Hello! and suerly asks you that How are You!! ________________!
You can test it with the following as acces modifiers and the progrm will run Ofcourse it will give you compilation error.
protected
xxx
abc
xyz
private
Do you have any justification?Hmm,
I've been working with different versions of jdk since, if I'm not mistaken, jdk1.0.6 and never was able to get *.class with compilation errors. It was true for Windows*, Linux, and Solaris*.
About the 'private'/'protected' modifier for the type (class) - it makes perfect sence not to allow it there: why would anyone want to create a type if no one can access it? There should be a reason for restricting your types - let's say, any inner class can be private/protected.
For ex., you shouldn't have compile problems with this:
class Test
public static void main(String s[])
System.out.println("Hello!How are You!!");
private class ToTest{}
Sorry, but I don't really know where you can read up on that. -
Why do I get the JSP compilation error?
Why do I get the JSP compilation error?
Envionment:
AIX,WLS 5.1 sp10,.........
Thu Jun 07 11:54:41 CDT 2001:<I> <ServletContext-dcms> Generated java
file: /usr/local/weblogic/test-weblogic/weblogic/myserver/dcms
web/app/tmp_war/jsp_servlet/_report/_walmart_95_prod_95_proof_95_report.java
Thu Jun 07 11:54:42 CDT 2001:<E> <ServletContext-dcms> Compilation of
/usr/local/weblogic/test-weblogic/weblogic/myserver/dcms_web/a
pp/_tmp_war/jsp_servlet/_report/_walmart_95_prod_95_proof_95_report.java
failed: Exception in thread "main" java.lang.NoClassDefFoun
dError: sun/tools/javac/Main
java.io.IOException: Compiler failed
executable.exec([Ljava.lang.String;[javac, -classpath,
/usr/java_dev2/jre/sh/../lib/rt.jar:/usr
/java_dev2/jre/sh/../lib/i18n.jar:/usr/java_dev2/jre/sh/../classes:./classes/boot:./eval/cloudscape/lib/cloudscape.jar:./anderson_co
mmon/3rd_party_jars/jt400.jar:/usr/lpp/db2_07_01/java/db2java.zip::./lib/weblogic510sp8boot.jar:./license:./classes:./lib/weblogicau
x.jar:./myserver/serverclasses:./anderson_common/3rd_party_jars/jt400.jar:/usr/lpp/db2_07_01/java/db2java.zip::./classes/dcms/com.ib
m.mq.iiop.jar:./classes/dcms/com.ibm.mq.jar:./classes/dcms/com.ibm.mqbind.jar:./classes/dcms/com.ibm.mqjms.jar:./classes/dcms/com_au
th.jar:./classes/dcms/com_auth_server.jar:./classes/dcms/com_io.jar:./classes/dcms/com_jms.jar:./classes/dcms/com_jndi.jar:./classes
/dcms/com_system.jar:./classes/dcms/com_system_server.jar:./classes/dcms/com_util.jar:./classes/dcms/dcms_common.jar:./classes/dcms/
dcms_common_server.jar:./classes/dcms/dcms_dl_render_server.jar:./classes/dcms/dcms_finalresting_server.jar:./classes/dcms/dcms_fulf
illment.jar:./classes/dcms/dcms_fulfillment_server.jar:./classes/dcms/dcms_fulfillment_walmart_server.jar:./classes/dcms/dcms_lookup
_server.jar:./classes/dcms/dcms_media_server.jar:./classes/dcms/dcms_order.jar:./classes/dcms/dcms_order_server.jar:./classes/dcms/d
cms_order_session.jar:./classes/dcms/dcms_product.jar:./classes/dcms/dcms_product_server.jar:./classes/dcms/dcms_render_client.jar:.
/classes/dcms/dcms_render_server.jar:./classes/dcms/dcms_talent_server.jar:./classes/dcms/dcms_talent.jar:./classes/dcms/dcms_walmar
t.jar:./classes/dcms/dcms_walmart_server.jar:./classes/dcms/dcms_jms.jar:./classes/dcms/xreport_pro.jar:./classes/dcms/xtools.jar:./
classes/dcms/jms.jar:./classes/dcms/dcms_sql.jar:./classes/dcms/dcms_product_sql.jar::/usr/local/weblogic/test-weblogic/weblogic/mys
erver/tmp_deployments/ejbjar-4971.jar:/usr/local/weblogic/test-weblogic/weblogic/lib/persistence/WebLogic_RDBMS.jar:/usr/local/weblo
gic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4970.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployme
nts/ejbjar-4969.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4968.jar:/usr/local/weblogic/test-web
logic/weblogic/myserver/tmp_deployments/ejbjar-4967.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4
966.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4965.jar:/usr/local/weblogic/test-weblogic/weblog
ic/myserver/tmp_deployments/ejbjar-4964.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4963.jar:/usr
/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4962.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/
tmp_deployments/ejbjar-4961.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4960.jar:/usr/local/weblo
gic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4959.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployme
nts/ejbjar-4958.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4957.jar:/usr/local/weblogic/test-web
logic/weblogic/myserver/tmp_deployments/ejbjar-4956.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4
955.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4954.jar:/usr/local/weblogic/test-weblogic/weblog
ic/myserver/tmp_deployments/ejbjar-4953.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4952.jar:/usr
/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4951.jar:/usr/local/weblogic/test-weblogic/weblogic/./myserve
r/dcms_web/app/WEB-INF/classes:/usr/local/test-weblogic/weblogic/myserver/dcms_web/app/WEB-INF/classes:/usr/local/weblogic/test-webl
ogic/weblogic/./myserver/dcms_web/app/_tmp_war:/usr/local/weblogic/test-weblogic/weblogic/myserver/dcms_web/app/_tmp_war,
-d, /usr/l
ocal/weblogic/test-weblogic/weblogic/myserver/dcms_web/app/_tmp_war,
/usr/local/weblogic/test-weblogic/weblogic/myserver/dcms_web/ap
p/_tmp_war/jsp_servlet/_report/_walmart_95_prod_95_proof_95_report.java])
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:396)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:202)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:284)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:174)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:164)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:99)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java(Compiled
Code))
at com.web.CommonWebUtils.forward(CommonWebUtils.java(Compiled
Code))
at com.web.PageNavServlet.service(PageNavServlet.java:76)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
----------------------Caught exception while forwarding to page
/report/walmart_prod_proof_report.jsp------------------------
----------------------Exception java.io.IOException: Compiler failed
executable.exec([Ljava.lang.String;[javac, -classpath, /usr/jav
a_dev2/jre/sh/../lib/rt.jar:/usr/java_dev2/jre/sh/../lib/i18n.jar:/usr/java_dev2/jre/sh/../classes:./classes/boot:./eval/cloudscape/
lib/cloudscape.jar:./anderson_common/3rd_party_jars/jt400.jar:/usr/lpp/db2_07_01/java/db2java.zip::./lib/weblogic510sp8boot.jar:./li
cense:./classes:./lib/weblogicaux.jar:./myserver/serverclasses:./anderson_common/3rd_party_jars/jt400.jar:/usr/lpp/db2_07_01/java/db
2java.zip::./classes/dcms/com.ibm.mq.iiop.jar:./classes/dcms/com.ibm.mq.jar:./classes/dcms/com.ibm.mqbind.jar:./classes/dcms/com.ibm
.mqjms.jar:./classes/dcms/com_auth.jar:./classes/dcms/com_auth_server.jar:./classes/dcms/com_io.jar:./classes/dcms/com_jms.jar:./cla
sses/dcms/com_jndi.jar:./classes/dcms/com_system.jar:./classes/dcms/com_system_server.jar:./classes/dcms/com_util.jar:./classes/dcms
/dcms_common.jar:./classes/dcms/dcms_common_server.jar:./classes/dcms/dcms_dl_render_server.jar:./classes/dcms/dcms_finalresting_ser
ver.jar:./classes/dcms/dcms_fulfillment.jar:./classes/dcms/dcms_fulfillment_server.jar:./classes/dcms/dcms_fulfillment_walmart_serve
r.jar:./classes/dcms/dcms_lookup_server.jar:./classes/dcms/dcms_med
rder_server.jar:./classes/dcms/dcms_order_session.jar:./classes/dcm
es/dcms/dcms_render_client.jar:./classes/dcms/dcms_render_server.jar:./classes/dcms/dcms_talent_server.jar:./classes/dcms/dcms_talen
t.jar:./classes/dcms/dcms_walmart.jar:./classes/dcms/dcms_walmart_server.jar:./classes/dcms/dcms_jms.jar:./classes/dcms/xreport_pro.
jar:./classes/dcms/xtools.jar:./classes/dcms/jms.jar:./classes/dcms/dcms_sql.jar:./classes/dcms/dcms_product_sql.jar::/usr/local/web
logic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4971.jar:/usr/local/weblogic/test-weblogic/weblogic/lib/persistence/Web
Logic_RDBMS.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4970.jar:/usr/local/weblogic/test-weblogi
c/weblogic/myserver/tmp_deployments/ejbjar-4969.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4968.
jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4967.jar:/usr/local/weblogic/test-weblogic/weblogic/m
yserver/tmp_deployments/ejbjar-4966.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4965.jar:/usr/loc
al/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4964.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_
deployments/ejbjar-4963.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4962.jar:/usr/local/weblogic/
test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4961.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/
ejbjar-4960.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4959.jar:/usr/local/weblogic/test-weblogi
c/weblogic/myserver/tmp_deployments/ejbjar-4958.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4957.
jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4956.jar:/usr/local/weblogic/test-weblogic/weblogic/m
yserver/tmp_deployments/ejbjar-4955.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4954.jar:/usr/loc
al/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4953.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_
deployments/ejbjar-4952.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4951.jar:/usr/local/weblogic/
test-weblogic/weblogic/./myserver/dcms_web/app/WEB-INF/classes:/usr/local/test-weblogic/weblogic/myserver/dcms_web/app/WEB-INF/class
es:/usr/local/weblogic/test-weblogic/weblogic/./myserver/dcms_web/app/_tmp_war:/usr/local/weblogic/test-weblogic/weblogic/myserver/d
cms_web/app/_tmp_war, -d,
/usr/local/weblogic/test-weblogic/weblogic/myserver/dcms_web/app/_tmp_war,
/usr/local/weblogic/test-weblog
ic/weblogic/myserver/dcms_web/app/_tmp_war/jsp_servlet/_report/_walmart_95_prod_95_proof_95_report.java])------------------------
Hi, im getting the same thing,
Been tryin to download it for days but keeps saying "Invalid signature"
I even went into ADD REMOVE PROGRAMS hit Apple software update and change and then repair but this did not work.
Help much appreciated. Thanks -
Compilation Error for import classes not found in generated Proxy Class
Hi,
We are generating java classes for the COM dll using JCOM com2java compiler.
We are getting a compilation error for import class not found when compiling the
generated Proxy java source code. It can't find the com.bea.jcom.Dispatch class that
the generated Proxy java source code extends. It also can't find com.bea.jcom.Variant
or com.bea.jcom.Param. These are interfaces or data types or classes used by COM
library.
I added weblogic.jar to my class path and the only Dispatch class i found inside
the weblogic.jar is com.linar.jintegra.Dispatch;
We have com objects for which we want to develop an EJB client to interface with
the COM object using JCOM with Native Mode disabled.
Any help on the compilation error..I tried changing the extends for Dispatch to com.linar.jintegra.Dispatch
but the other errors are still there.
To begin with, I think the generated code should not refer to any of the COM data
types.
Any help please.
Thank you in advance,
Regards,
Rahul Srivastava
[email protected]Hi,
I resolved the other errors by changing all references from com.bea.jcom.Variant
etc to com.linar.jintegra.class name..all were present under the com.linar.jintegra
package.
Thank you all anyways,
Regards,
rahul
"Rahul Srivastava" <[email protected]> wrote:
>
Hi,
We are generating java classes for the COM dll using JCOM com2java compiler.
We are getting a compilation error for import class not found when compiling
the
generated Proxy java source code. It can't find the com.bea.jcom.Dispatch
class that
the generated Proxy java source code extends. It also can't find com.bea.jcom.Variant
or com.bea.jcom.Param. These are interfaces or data types or classes used
by COM
library.
I added weblogic.jar to my class path and the only Dispatch class i found
inside
the weblogic.jar is com.linar.jintegra.Dispatch;
We have com objects for which we want to develop an EJB client to interface
with
the COM object using JCOM with Native Mode disabled.
Any help on the compilation error..I tried changing the extends for Dispatch
to com.linar.jintegra.Dispatch
but the other errors are still there.
To begin with, I think the generated code should not refer to any of the
COM data
types.
Any help please.
Thank you in advance,
Regards,
Rahul Srivastava
[email protected]
Maybe you are looking for
-
Problem combining selection tools in Photoshop CC 2014
When I make a selection using the Quick Selection Tool in Photoshop CC and then switch to the Lasso Tool to refine the selection, it just adds to what I already had selected. If I do the same thing in CC 2014, as soon as I click on the photo with th
-
How to map the form fields with zoho crm module?
I am integrating a web app with Zoho CRM,I created a form in .aspx and put some fields on it like first name,last name,email etc.Now i want to map these fields with the zoho crm contacts module,so that when i submit this form it will save the data th
-
I have been able to upload videos to vimeo from FCPX in the past. However, now FC gives me a message that my password is incorrect. This is despite the fact that my password allows me to sign into the Vimeo website. I have reset my vimeo password, re
-
Shared tenchologies files failed in reinstall of adobe photoshop elements 10
My Adobe Elements 10 both photoshop and premiere suddenly stopped opening up, or would open to menu page then disappear.I deactovated to uninstall photoshop and tried to install it again. it failed saying the shared technologies files failed. Now I c
-
A black triangle come up in i photo when I try to edit a picture from my library. I don't know what it means or how to get rid of it? Thanks for any help.