XSD compilation problem

Hi good afternoon..
here i am compiling one XSD file but when i am doing..i facing following error..
after this error ...
I have already set the all the PATH, CLASSPATH..
E:\XMLprog>scomp -out purchaseorder.jar purchaseorder.xsd
Time to build schema type system: 0.705 seconds
Time to generate code: 0.157 seconds
java.io.IOException: Cannot run program "E:\XMLprog\javac": CreateProcess error=2, The system cannot find the file specified
java.io.IOException: CreateProcess error=2, The system cannot find the file specified
java.io.IOException: Cannot run program "E:\XMLprog\javac": CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at org.apache.xmlbeans.impl.tool.CodeGenUtil.externalCompile(CodeGenUtil.java:231)
at org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:1126)
at org.apache.xmlbeans.impl.tool.SchemaCompiler.main(SchemaCompiler.java:368)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(Unknown Source)
at java.lang.ProcessImpl.start(Unknown Source)
... 6 more
BUILD FAILED

As it is showing error like:
The system cannot find the file specifiedCheck for the following:
1) purchaseorder.xsd is in the directory E:\XMLprog
2) If purchaseorder.xsd includes any other .xsd files,
    all included files should also be at
        same directory E:\XMLprog
        or at the location specified in schemaLocation attribute in purchaseorder.xsd
Thanks,
Tejas

Similar Messages

  • XSD Resolution problem - Unable to load Translation schemas

    Hi,
    I've run into a very strange kind of problem (not to say some are less strange then others). Let me explain the context of the situation.
    I've got a BPEL process calling two plsql packages on ORA database, one Java web service running on the same weblogic server and couple of other services (eg. notification services, jdbc select/insert, etc.). There is no problem with the last listed, but definitely something wrong with the web service and the plsql callouts.
    When I deploy the BPEL process and execute it, the first two instances always fail. The same happens when I restart the server, the errors are repeated after a certain period as well (for example over night). The process always fails EXACTLY TWICE, before running normally. Every other instance executed after the two initial failures runs WITHOUT the following error.
    I mentioned there are two plsql callouts in the process, earlier the first instance failed on the second one and the second instance failed on the first. Now, it mostly fails on the second callout. I've made no significant changes in the code. Perhaps the strangest thing about this is that it fails when invoking the plsql package but the error concerns xsd definitions of the web service that plays no role at this stage.
    All my services are correctly deployed, I deleted all interface definitions from MDS repository and redeployed SOA bundle again before installing each service.
    I think it has something to do with generated xsd definitions by the java web service (it's the http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 and http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 from following stack trace), but I can't figure out what exactly is wrong with them.
    Anybody come accross a similar error? Thanks for tips, I've run out of ideas.      
    Error Message: {http://schemas.oracle.com/bpel/extension}bindingFault
    Fault ID     default/S50001KontrolaSouboruBS!1.0*soa_be986963-f9d9-412d-b692-43804a35b3ee/KontrolaSouboru/830023-BpInv18-BpSeq8.12-2
    Fault Time     14-Feb-2012 11:11:16
    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 'LogFile' failed due to: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec due to: XSD Resolution problem. XSD Resolution problem. Unable to load Translation schemas from for http://xmlns.oracle.com/pcbpel/adapter/db/TST_IP/LOG_FILE/LOG_FILE/ due to: Different schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and oramds:/apps/LCRInterface/DataObjects/Common/V1/Common.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and http://localhost:8001/soa-infra/services/default/S50035NotifikaceChybyBS/apps/LCRInterface/DataObjects/Common/V1/Common.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and oramds:/apps/LCRInterface/DataObjects/Common/V1/DataTypes.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and http://localhost:8001/soa-infra/services/default/S50035NotifikaceChybyBS/apps/LCRInterface/DataObjects/Common/V1/DataTypes.xsd elementFormDefault values are differentGlobal element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 7] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 82] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:7] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:82] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 9] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 36] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:9] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:36] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}SaveFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 19] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 21] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:19] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:21] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 11] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 51] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:11] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:51] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 5] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 66] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:5] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:66] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 13] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 112] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:13] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:112] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 15] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 127] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:15] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:127] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}RenameFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 17] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 97] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:17] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:97] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 115] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 52] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:117] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:54] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}RenameFileDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 175] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 98] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:177] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:100] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 153] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 128] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:155] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:130] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 64] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 83] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:66] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:85] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}SaveFileDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 93] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 22] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:95] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:24] Please make sure all used XML schemas are imported/included correctly. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. ". 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>Different schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and oramds:/apps/LCRInterface/DataObjects/Common/V1/Common.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and http://localhost:8001/soa-infra/services/default/S50035NotifikaceChybyBS/apps/LCRInterface/DataObjects/Common/V1/Common.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and oramds:/apps/LCRInterface/DataObjects/Common/V1/DataTypes.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and http://localhost:8001/soa-infra/services/default/S50035NotifikaceChybyBS/apps/LCRInterface/DataObjects/Common/V1/DataTypes.xsd elementFormDefault values are differentGlobal element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 7] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 82] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:7] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:82] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 9] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 36] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:9] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:36] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}SaveFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 19] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 21] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:19] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:21] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 11] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 51] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:11] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:51] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 5] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 66] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:5] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:66] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 13] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 112] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:13] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:112] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 15] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 127] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:15] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:127] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}RenameFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 17] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 97] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:17] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:97] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 115] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 52] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:117] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:54] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}RenameFileDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 175] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 98] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:177] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:100] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 153] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 128] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:155] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:130] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 64] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 83] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:66] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:85] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}SaveFileDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 93] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 22] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:95] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:24] </detail></part><part name="code"><code>null</code></part></bindingFault></bpelFault>

    I had similar issue, when i deployed composite using Jdeveloper. The problem was with my adf-config.xml pointing to dev server and all my references in my composite.xml referring to test server.
    I changed property of 'oracle.mds.persistence.stores.db.DBMetadataStore' in adf-config.xml to test server. After adf-config.xml change in Jdev my compilation went smooth.
    Note: If above changes doesn't work, try restarting JDeveloper, sometimes the changes in adf-config.xml is not getting effect immediately.
    Regards,
    Ziaur Rahuman S
    Edited by: Ziaur Rahuman on Feb 13, 2013 10:58 PM

  • Re: [iPlanet-JATO] sp3 jsp compiler problem

    Weiguo,
    First, Matt is correct, the regular expression tool is perfect for general text
    substitution situations, and as a completely independent tool its use is not
    restricted to migration situations (or file types for that matter).
    Second, I sympathize with the unfortunate trouble you are experiencing due to
    Jasper's (perhaps more strict) compilation, but in what way did the iMT
    automated translation contribute to these inconsistencies that you cited?
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    The iMT does not generate any OnClick or onClick clauses per se. In a
    translation situation, the only way "OnClick" would have been introduced was if
    it had been part of the pre-existing project's "extraHTML" (which was written
    by the original customer and just passed through unchanged by the iMT) or if it
    was added manually by the post-migration developer.
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be
    similar to the OnClick situation described above?
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    Again, the content tag would never have been generated by the iMT. There was no
    equivalent in the NetDynamics world, so any content tags in your code must have
    been introduced by your developers manually. Its a shame that jasper is so
    particular, but the iMT could not help you out here even if we wanted to. The
    constants that are used by the iMT are defined in
    com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can see, the
    only situation of a closing tag with any space in it is
    public static final String CLOSE_EMPTY_ELEMENT = " />";
    But that should not cause the type of problem you are referring to.
    Mike
    ----- Original Message -----
    From: Matthew Stevens
    Sent: Thursday, September 06, 2001 10:16 AM
    Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
    Weiguo,
    Others will chime in for sure...I would highly recommend the Regex Tool from
    the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
    posted to the group (even recently) on directions and advantages of creating
    your own RULES (rules file) in XML for arbitary batch processing of source.
    matt
    -----Original Message-----
    From: weiguo.wang@b...
    [mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174144234026000079108238073194105057099246073154180137239239223019162">weiguo.wang@b...</a>]
    Sent: Thursday, September 06, 2001 12:25 PM
    Subject: [iPlanet-JATO] sp3 jsp compiler problem
    Matt/Mike/Todd,
    We are trying to migrate to sp3 right now, but have had a lot of
    issues with the new jasper compiler.
    The following workaround has been employed to solve the issues:
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    As I see it, we have two options to go about solving this problem:
    1. Write a script which will iterate through all the jsp files and
    call jspc on them. Fix the errors manually when jspc fails. Jspc will
    flag the line number where an error occurs.
    2. Write a utility which scans the jsp files and fix the errors when
    they are encountered. We should define what's an error and how to
    correct it. It's best if we combine this with solution 1 since we
    might miss an error condition.
    Actually, there might be another option, which is seeking help from
    you guys since you have better understanding of JATO and iAS. Can you
    do anything to help us?
    We would be happy to hear your thoughts.
    At last, I would like to suggest modifying the moko tool so that
    these rules are enforced and the generated JSPs work with the new
    compiler. This is for the benefit of any new migration projects.
    Thanks a lot.
    Weiguo
    [email protected]
    Choose from 1000s of job listings!
    [email protected]
    [Non-text portions of this message have been removed]

    Thanks a lot Matt and Mike for your prompt replies.
    I agree completely that iMT doesn't introduce the inconsistencies.
    About the three cases I mentioned, the third one happens only in
    manually created JSPs. So it has nothing to do with iMT. The first
    two are mainly due to the existing HTML code, as you rightly pointed
    out.
    The reason I made the suggestion is since we know that case 1 and 2
    won't pass the japser compiler in sp3, we have to do something about
    it. The best place to do this, in my mind, is iMT. Of course, there
    might be some twists that make it impossible or difficult to do this
    kind of case manipulation or attribute discard.
    Weiguo
    --- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
    Weiguo,
    First, Matt is correct, the regular expression tool is perfect for general text substitution situations, and as a completely independent
    tool its use is not restricted to migration situations (or file types
    for that matter).
    >
    Second, I sympathize with the unfortunate trouble you are experiencing due to Jasper's (perhaps more strict) compilation, but
    in what way did the iMT automated translation contribute to these
    inconsistencies that you cited?
    >
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    The iMT does not generate any OnClick or onClick clauses per se. In a translation situation, the only way "OnClick" would have been
    introduced was if it had been part of the pre-existing
    project's "extraHTML" (which was written by the original customer and
    just passed through unchanged by the iMT) or if it was added manually
    by the post-migration developer.
    >
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be similar to the OnClick situation described above?
    >
    >
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    Again, the content tag would never have been generated by the iMT. There was no equivalent in the NetDynamics world, so any content tags
    in your code must have been introduced by your developers manually.
    Its a shame that jasper is so particular, but the iMT could not help
    you out here even if we wanted to. The constants that are used by the
    iMT are defined in
    com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can
    see, the only situation of a closing tag with any space in it is
    public static final String CLOSE_EMPTY_ELEMENT = " />";
    But that should not cause the type of problem you are referring to.
    Mike
    ----- Original Message -----
    From: Matthew Stevens
    Sent: Thursday, September 06, 2001 10:16 AM
    Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
    Weiguo,
    Others will chime in for sure...I would highly recommend the Regex Tool from
    the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
    posted to the group (even recently) on directions and advantages of creating
    your own RULES (rules file) in XML for arbitary batch processing of source.
    >
    matt
    -----Original Message-----
    From: weiguo.wang@b...
    [mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174048139046">weiguo.wang@b...</a>]
    Sent: Thursday, September 06, 2001 12:25 PM
    Subject: [iPlanet-JATO] sp3 jsp compiler problem
    Matt/Mike/Todd,
    We are trying to migrate to sp3 right now, but have had a lot of
    issues with the new jasper compiler.
    The following workaround has been employed to solve the issues:
    1. Changed the case of the tag attribute to be the same as
    what's
    defined in tld.
    example: changed OnClick to onClick
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    As I see it, we have two options to go about solving this problem:
    >>
    1. Write a script which will iterate through all the jsp files and
    call jspc on them. Fix the errors manually when jspc fails. Jspc will
    flag the line number where an error occurs.
    2. Write a utility which scans the jsp files and fix the errors when
    they are encountered. We should define what's an error and how to
    correct it. It's best if we combine this with solution 1 since we
    might miss an error condition.
    Actually, there might be another option, which is seeking help from
    you guys since you have better understanding of JATO and iAS. Can you
    do anything to help us?
    We would be happy to hear your thoughts.
    At last, I would like to suggest modifying the moko tool so that
    these rules are enforced and the generated JSPs work with the new
    compiler. This is for the benefit of any new migration projects.
    Thanks a lot.
    Weiguo
    [email protected]
    Choose from 1000s of job listings!
    [email protected]
    Service.
    >
    >
    >
    [Non-text portions of this message have been removed]

  • Servlet Compilation Problem !

    Hi,
    I am just starting to learn servlets and I got problem in compiling them. I got compilation error in
    import javax.servlet.*;statement. Seems that the compiler cannot find the servlet package. I got J2EE 1.4 beta installed on my machine but there is no servlet.jar package. I am using J2SDK 1.4.1_02, J2EE 1.4 beta and Tomcat 4.1.24.
    Can anyone help me with my servlet compilation problem?
    Thanks in advance!
    Josh

    servlet.jar is here :
    <tomcatdir>\common\lib
    add it to your compiler classpath

  • Compilation problem in a JSP page

    Hi all,
    I'm trying to write a jsp page and some java stuff in it.
    It goes something like this -
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
    "http://www.w3.org/TR/html4/loose.dtd">
    <%@ page contentType="text/html;charset=windows-1255"%>
    <html>
      <head>
        <meta http-equiv="Content-Type" content="text/html; charset=windows-1255"/>
        <title>Michael</title>
      </head>
      <body>
    <%
              String strError="";
    %>
    </body>Now the problem is that I get compilation problem about the use in java -
    "String cannot be resolved to a type"
    I know for sure that in other computers it's work, the question is what I'm missing?
    I have Java VM installed and I've downloaded and installed the latest JDK, what else?
    thanks,
    Michael.

    Michael4488 wrote:
    BalusC wrote:
    Then you should be using JSTL/EL.I don't familiar with this technology, any way - Its work on one computer so in my understanding it should work on the other as well.It is not related to the actual problem. It was just a comment on your code. Using scriptlets is considered as bad practice.
    I understand that of course, but I don't use any configuration file or set any special parameters in my computer.
    What exactly does the compiler need in order to recognize the Java code in the JSP page? If i manually add the JAVA_HOME environment variable it will work?
    where should I refer it to? "..\Java\jre1.6.0_07\lib" will do?It must point to the root installation directory of the JDK (thus not the JRE!).

  • DB Adapter JCA-12563, XSD Resolution problem

    Hi,
    I am using Oracle SOA Suit, 11.1.1.4 and I am getting error in my db adapter.
    Below is the SOA adapter logs.
    This is intermittent issue, and occurs If i test the process for some time. After reeploying the service, same does not happen for some time but reoccurs after some good amount of testing.
    Can anybody help me with this issue?
    [2011-07-23T14:48:31.398+01:00] [managed1_metbsoa2] [ERROR] [] [oracle.soa.adapter] [tid: orabpel.engine.pool-5.thread-26] [userId: <anonymous>] [ecid: 16acbfc99351d211:2a7cdad1:13156bb951c:-8000-0000000000118eab,0:1:100392924] [APP: soa-infra] JCABinding=> NotificationService:DBA_GetConfigurationDetail [ DBA_GetConfigurationDetail_ptt::DBA_GetConfigurationDetailSelect(DBA_GetConfigurationDetailSelect_inputParameters,TConfigurationCollection) ] Could not invoke operation 'DBA_GetConfigurationDetailSelect' against the 'Database Adapter' due to: [[
    BINDING.JCA-12563
    Exception occured when binding was invoked.
    Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBReadInteractionSpec due to: XSD Resolution problem.
    XSD Resolution problem.
    Unable to load Translation schemas from for http://xmlns.oracle.com/pcbpel/adapter/db/top/DBA_GetConfigurationDetail due to:
    Please make sure all used XML schemas are imported/included correctly.
    The invoked JCA adapter raised a resource exception.
    Please examine the above error message carefully to determine a resolution.

    I am also observing the similar issue , when db adapter is called getting the error
    Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'ObjectVersionNumber' failed due to: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBPureSQLInteractionSpec due to: XSD Resolution problem. XSD Resolution problem. Unable to load Translation schemas from for http://xmlns.oracle.com/pcbpel/adapter/db/ObjectVersionNumber due to: Global element declaration/definition of name '{http://xmlns.oracle.com/apps/cac/soaprovider/plsql/jtf_tasks_pub/create_task/}InputParameters' are duplicated at the following locations: oramds:/apps/crm/services/IntegratedSoaGateway/APPS_ISG_CREATE_TASK_JTF_TASKS_PUB-24CREATE_TASK.xsd [line#: 3] http://civiceb.mfltest.co.uk/webservices/SOAProvider/plsql/jtf_tasks_pub/APPS_ISG_CREATE_TASK_JTF_TASKS_PUB-24CREATE_TASK.xsd [line#: 1] There are at least two of them looking different: oramds:/apps/crm/services/IntegratedSoaGateway/APPS_ISG_CREATE_TASK_JTF_TASKS_PUB-24CREATE_TASK.xsd [difference starting at line#:79] http://civiceb.mfltest.co.uk/webservices/SOAProvider/plsql/jtf_tasks_pub/APPS_ISG_CREATE_TASK_JTF_TASKS_PUB-24CREATE_TASK.xsd [difference starting at line#:1] Please make sure all used XML schemas are imported/included correctly. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
    There is a retry logic in a composite and after 2 or 3 retries this error does not comes, Its an intermittent issue.
    Is anyone able to find the resolution for this issue?.

  • OpenTrans 2.1 .xsd import problem into PI 7.1

    Hello,
    While trying to import the latest version 2.1 of openTrans .xsd Files (I downloaded "openTRANS_2.1_german_all-in-one_package.zip") into PI 7.1 we fail. Error message while loading the file "opentrans_2_1.xsd" is:
    Unable to convert imported document to WSDL
    Reason:
    Unable to recognize document as valid XSDCheck selected category
    OpenTrans 1.0 we have already in use since several time, however there is a need for the latest version now.
    Has anybody managed to get openTrans 2.1 to work with PI 7.1? And if so - how?
    Thanks!
    Andreas

    Hello Andreas
    This error can occur if there is an element tag with the name XML, e.g.: <xsd:element name="xml">.  If the element name is something other than xml, e.g. <xsd:element name="test">, then the import should be ok.
    SAP does not allow the element name in an XSD to start with the prefix -   xml                                                                               
    This conforms to the xml schema standards set by W3C  i.e.  http://www.w3schools.com/xml/xml_elements.asp
    -> XML Naming Rules section.
    Also, check note #1255351 External Defintion - XSD Checks Problem
    Regards
    Mark

  • Compilation problem on solaris9  x86

    I am working on JAVA/J2EE . Am new to solaris9 . My requirement is to compile a source distribution of MOD-JK 1.2.21 (apache 2.0 server connector)and to produce binary distribution (*.so file) in solaris9 X86 box. But i got only source distribution of solaris10 X86 platform . Even with this source i tried to compile in solaris9 box its giving some error message and i can't able to make a executable file. Below i pasted the error message .
    # ./configure -with-apxs=/usr/apache2/bin/apxs
    checking build system type... i386-pc-solaris2.10
    checking host system type... i386-pc-solaris2.10
    checking target system type... i386-pc-solaris2.10
    checking for a BSD-compatible install... scripts/build/unix/install-sh -c
    checking whether build environment is sane... yes
    checking for gawk... no
    checking for mawk... no
    checking for nawk... nawk
    checking whether make sets $(MAKE)... no
    checking for gcc... no
    checking for cc... cc
    checking for C compiler default output file name... configure: error: C compiler cannot create executables
    See `config.log' for more details.
    Can any body help me in this regards. Even i don't know, am proceeding in right direction to compile this file. If any body having the binary distribution for the same MOD-JK1.2.21 on solaris9 or solaris10 X86 platform for apache2.0 . please help me to compile this file .I given below the config.log file entries also.
    Thanks in advance..........
    karthikeyan.u
    [email protected]
    AIM or AOL :: karthikeyanu
    CONFIG.log entries......
    This file contains any messages produced by compilers while
    running configure, to aid debugging if configure makes a mistake.
    It was created by configure, which was
    generated by GNU Autoconf 2.59. Invocation command line was
    $ ./configure -with-apxs=/usr/apache2/bin/apxs
    ## Platform. ##
    hostname = Solaris
    uname -m = i86pc
    uname -r = 5.10
    uname -s = SunOS
    uname -v = Generic_118844-26
    /usr/bin/uname -p = i386
    /bin/uname -X = System = SunOS
    Node = Solaris
    Release = 5.10
    KernelID = Generic_118844-26
    Machine = i86pc
    BusType = <unknown>
    Serial = <unknown>
    Users = <unknown>
    OEM# = 0
    Origin# = 1
    NumCPU = 1
    /bin/arch = i86pc
    /usr/bin/arch -k = i86pc
    /usr/convex/getsysinfo = unknown
    hostinfo = unknown
    /bin/machine = unknown
    /usr/bin/oslevel = unknown
    /bin/universe = unknown
    PATH: /usr/sbin
    PATH: /usr/bin
    PATH: /usr/openwin/bin
    PATH: /usr/ucb
    ## Core tests. ##
    configure:1546: checking build system type
    configure:1564: result: i386-pc-solaris2.10
    configure:1572: checking host system type
    configure:1586: result: i386-pc-solaris2.10
    configure:1594: checking target system type
    configure:1608: result: i386-pc-solaris2.10
    configure:1640: checking for a BSD-compatible install
    configure:1695: result: scripts/build/unix/install-sh -c
    configure:1706: checking whether build environment is sane
    configure:1749: result: yes
    configure:1814: checking for gawk
    configure:1843: result: no
    configure:1814: checking for mawk
    configure:1843: result: no
    configure:1814: checking for nawk
    configure:1830: found /usr/bin/nawk
    configure:1840: result: nawk
    configure:1850: checking whether make sets $(MAKE)
    configure:1874: result: no
    configure:2085: checking for gcc
    configure:2114: result: no
    configure:2165: checking for cc
    configure:2181: found /usr/ucb/cc
    configure:2191: result: cc
    configure:2355: checking for C compiler version
    configure:2358: cc --version </dev/null >&5
    /usr/ucb/cc: language optional software package not installed
    configure:2361: $? = 1
    configure:2363: cc -v </dev/null >&5
    /usr/ucb/cc: language optional software package not installed
    configure:2366: $? = 1
    configure:2368: cc -V </dev/null >&5
    /usr/ucb/cc: language optional software package not installed
    configure:2371: $? = 1
    configure:2394: checking for C compiler default output file name
    configure:2397: cc conftest.c >&5
    /usr/ucb/cc: language optional software package not installed
    configure:2400: $? = 1
    configure: failed program was:
    | /* confdefs.h. */
    |
    | #define PACKAGE_NAME ""
    | #define PACKAGE_TARNAME ""
    | #define PACKAGE_VERSION ""
    | #define PACKAGE_STRING ""
    | #define PACKAGE_BUGREPORT ""
    | #define PACKAGE "mod_jk"
    | #define VERSION "1.2.21"
    | /* end confdefs.h. */
    |
    | int
    | main ()
    | {
    |
    | ;
    | return 0;
    | }
    configure:2439: error: C compiler cannot create executables
    See `config.log' for more details.
    ## Cache variables. ##
    ac_cv_build=i386-pc-solaris2.10
    ac_cv_build_alias=i386-pc-solaris2.10
    ac_cv_env_CC_set=
    ac_cv_env_CC_value=
    ac_cv_env_CFLAGS_set=
    ac_cv_env_CFLAGS_value=
    ac_cv_env_CPPFLAGS_set=
    ac_cv_env_CPPFLAGS_value=
    ac_cv_env_CPP_set=
    ac_cv_env_CPP_value=
    ac_cv_env_CXXCPP_set=
    ac_cv_env_CXXCPP_value=
    ac_cv_env_CXXFLAGS_set=
    ac_cv_env_CXXFLAGS_value=
    ac_cv_env_CXX_set=
    ac_cv_env_CXX_value=
    ac_cv_env_F77_set=
    ac_cv_env_F77_value=
    ac_cv_env_FFLAGS_set=
    ac_cv_env_FFLAGS_value=
    ac_cv_env_LDFLAGS_set=
    ac_cv_env_LDFLAGS_value=
    ac_cv_env_build_alias_set=
    ac_cv_env_build_alias_value=
    ac_cv_env_host_alias_set=
    ac_cv_env_host_alias_value=
    ac_cv_env_target_alias_set=
    ac_cv_env_target_alias_value=
    ac_cv_host=i386-pc-solaris2.10
    ac_cv_host_alias=i386-pc-solaris2.10
    ac_cv_prog_AWK=nawk
    ac_cv_prog_ac_ct_CC=cc
    ac_cv_prog_make_make_set=no
    ac_cv_target=i386-pc-solaris2.10
    ac_cv_target_alias=i386-pc-solaris2.10
    ## Output variables. ##
    ACLOCAL='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run aclocal-1.9'
    AMDEPBACKSLASH=''
    AMDEP_FALSE=''
    AMDEP_TRUE=''
    AMTAR='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run tar'
    APACHE20_OEXT=''
    APACHE_CONFIG_VARS=''
    APACHE_DIR=''
    APXS=''
    APXSCFLAGS=''
    APXSCPPFLAGS=''
    APXSLDFLAGS=''
    AR=''
    AUTOCONF='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run autoconf'
    AUTOHEADER='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run autoheader'
    AUTOMAKE='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run automake-1.9'
    AWK='nawk'
    CC='cc'
    CCDEPMODE=''
    CFLAGS=''
    CP=''
    CPP=''
    CPPFLAGS=''
    CXX=''
    CXXCPP=''
    CXXDEPMODE=''
    CXXFLAGS=''
    CYGPATH_W='echo'
    DEFS=''
    DEPDIR=''
    ECHO='echo'
    ECHO_C=''
    ECHO_N='-n'
    ECHO_T=''
    EGREP=''
    EXEEXT=''
    F77=''
    FFLAGS=''
    GREP=''
    INSTALL_DATA='${INSTALL} -m 644'
    INSTALL_PROGRAM='${INSTALL}'
    INSTALL_SCRIPT='${INSTALL}'
    INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s'
    INSTALL_TYPE=''
    JAVA_HOME=''
    JK_JNI_WORKER=''
    LDFLAGS=''
    LIBOBJS=''
    LIBS=''
    LIBTOOL=''
    LIB_JK_TYPE=''
    LN_S=''
    LTLIBOBJS=''
    MAKEINFO='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run makeinfo'
    MAKE_DYNAMIC_APACHE_FALSE=''
    MAKE_DYNAMIC_APACHE_TRUE=''
    MKDIR=''
    OBJEXT=''
    OS=''
    PACKAGE='mod_jk'
    PACKAGE_BUGREPORT=''
    PACKAGE_NAME=''
    PACKAGE_STRING=''
    PACKAGE_TARNAME=''
    PACKAGE_VERSION=''
    PATH_SEPARATOR=':'
    PERL=''
    RANLIB=''
    RM=''
    SED=''
    SET_MAKE='MAKE=make'
    SHELL='/bin/bash'
    STRIP=''
    TEST=''
    VERSION='1.2.21'
    WEBSERVER=''
    ac_ct_AR=''
    ac_ct_CC='cc'
    ac_ct_CXX=''
    ac_ct_F77=''
    ac_ct_RANLIB=''
    ac_ct_STRIP=''
    am__fastdepCC_FALSE=''
    am__fastdepCC_TRUE=''
    am__fastdepCXX_FALSE=''
    am__fastdepCXX_TRUE=''
    am__include=''
    am__leading_dot='.'
    am__quote=''
    am__tar='${AMTAR} chof - "$$tardir"'
    am__untar='${AMTAR} xf -'
    apache_include=''
    bindir='${exec_prefix}/bin'
    build='i386-pc-solaris2.10'
    build_alias=''
    build_cpu='i386'
    build_os='solaris2.10'
    build_vendor='pc'
    datadir='${prefix}/share'
    exec_prefix='NONE'
    host='i386-pc-solaris2.10'
    host_alias=''
    host_cpu='i386'
    host_os='solaris2.10'
    host_vendor='pc'
    includedir='${prefix}/include'
    infodir='${prefix}/info'
    install_sh='/export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/install-sh'
    int32_t_fmt=''
    int32_value=''
    int64_t_fmt=''
    int64_value=''
    libdir='${exec_prefix}/lib'
    libexecdir='${exec_prefix}/libexec'
    localstatedir='${prefix}/var'
    mandir='${prefix}/man'
    mkdir_p='$(install_sh) -d'
    oldincludedir='/usr/include'
    prefix='NONE'
    program_transform_name='s,x,x,'
    sbindir='${exec_prefix}/sbin'
    sharedstatedir='${prefix}/com'
    sysconfdir='${prefix}/etc'
    target='i386-pc-solaris2.10'
    target_alias=''
    target_cpu='i386'
    target_os='solaris2.10'
    target_vendor='pc'
    uint32_t_fmt=''
    uint32_t_hex_fmt=''
    uint64_t_fmt=''
    uint64_t_hex_fmt=''
    ## confdefs.h. ##
    #define PACKAGE "mod_jk"
    #define PACKAGE_BUGREPORT ""
    #define PACKAGE_NAME ""
    #define PACKAGE_STRING ""
    #define PACKAGE_TARNAME ""
    #define PACKAGE_VERSION ""
    #define VERSION "1.2.21"
    configure: exit 77

    You need to make sure the source is for the same version i.e. if you run apache 2.0.52 you need the source of 2.0.52. I successfully ran mixed installs, but I would not recommend it. You can download the required source from Apache.
    As for your compiler problem, make sure you have �/usr/ccs/bin/� in the your path, if you do not have it installed you will have to add the pkg �SUNWsprot�. You do not have 'make' in yout path.
    Make sure you have the following packages installed:
    SUNWbtool, SUNWsprot, SUNWtoo
    SUNWhea, SUNWarc, SUNWlibm, SUNWlibms
    SUNWdfbh, SUNWcg6h, SUNWxwinc, SUNWolinc,
    SUNWxglh,SUNWarcx, SUNWbtoox, SUNWdplx,
    SUNWscpux, SUNWsprox, SUNWlmsx, SUNWlmx
    SUNWlibCx, SUNWtoox, SUNWsra, SUNWsrh

  • Compilation problem with templates while using option -m64

    Hi,
    I have compilation problem with template while using option -m64.
    No problem while using option -m32.
    @ uname -a
    SunOS snt5010 5.10 Generic_127111-11 sun4v sparc SUNW,SPARC-Enterprise-T5220
    $ CC -V
    CC: Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25
    Here is some C++ program
    ############# foo5.cpp #############
    template <typename T, T N, unsigned long S = sizeof(T) * 8>
    struct static_number_of_ones
    static const T m_value = static_number_of_ones<T, N, S - 1>::m_value >> 1;
    static const unsigned long m_count = static_number_of_ones<T, N, S - 1>::m_count + (static_number_of_ones<T, N, S - 1>::m_value & 0x1);
    template <typename T, T N>
    struct static_number_of_ones<T, N, 0>
    static const T m_value = N;
    static const unsigned long m_count = 0;
    template <typename T, T N>
    struct static_is_power_of_2
    static const bool m_result = (static_number_of_ones<T,N>::m_count == 1);
    template <unsigned long N>
    struct static_number_is_power_of_2
    static const bool m_result = (static_number_of_ones<unsigned long, N>::m_count == 1);
    int main(int argc)
    int ret = 0;
    if (argc > 1)
    ret += static_is_power_of_2<unsigned short, 16>::m_result;
    ret += static_is_power_of_2<unsigned int, 16>::m_result;
    ret += static_is_power_of_2<unsigned long, 16>::m_result;
    ret += static_number_is_power_of_2<16>::m_result;
    else
    ret += static_is_power_of_2<unsigned short, 17>::m_result;
    ret += static_is_power_of_2<unsigned int, 17>::m_result;
    ret += static_is_power_of_2<unsigned long, 17>::m_result;
    ret += static_number_is_power_of_2<17>::m_result;
    return ret;
    Compiation:
    @ CC -m32 foo5.cpp
    // No problem
    @ CC -m64 foo5.cpp
    "foo5.cpp", line 20: Error: An integer constant expression is required here.
    "foo5.cpp", line 36: Where: While specializing "static_is_power_of_2<unsigned long, 16>".
    "foo5.cpp", line 36: Where: Specialized in non-template code.
    "foo5.cpp", line 26: Error: An integer constant expression is required here.
    "foo5.cpp", line 37: Where: While specializing "static_number_is_power_of_2<16>".
    "foo5.cpp", line 37: Where: Specialized in non-template code.
    "foo5.cpp", line 20: Error: An integer constant expression is required here.
    "foo5.cpp", line 43: Where: While specializing "static_is_power_of_2<unsigned long, 17>".
    "foo5.cpp", line 43: Where: Specialized in non-template code.
    "foo5.cpp", line 26: Error: An integer constant expression is required here.
    "foo5.cpp", line 44: Where: While specializing "static_number_is_power_of_2<17>".
    "foo5.cpp", line 44: Where: Specialized in non-template code.
    4 Error(s) detected.
    Predefined macro:
    @ CC -m32 -xdumpmacros=defs foo5.cpp | & tee log32
    @ CC -m64 -xdumpmacros=defs foo5.cpp | & tee log64
    @ diff log32 log64
    7c7
    < #define __TIME__ "09:24:58"
    #define __TIME__ "09:25:38"20c20
    < #define __sparcv8plus 1
    #define __sparcv9 1[snipped]
    =========================
    What is wrong?
    Thanks,
    Alex Vinokur

    Bug 6749491 has been filed for this problem. It will be visible at [http://bugs.sun.com] in a day or two.
    If you have a service contract with Sun, you can ask to have this bug's priority raised, and get a pre-release version of a compiler patch that fixes the problem.
    Otherwise, you can check for new patches from time to time at
    [http://developers.sun.com/sunstudio/downloads/patches/]
    and see whether this bug is listed as fixed.

  • Pro*Cobol PCO Compilation problem in Linux

    Hi,
    DB :oracle 11g on RHEL 5.5
    when we are compiling the (Pro*cobol ) PCO code it is giving us the error :
    System default option values taken from: /oracle/oracle11g/app/product/11.2.0/dbhome_1/precomp/admin/pcbcfg.cfg
    Error at line 320, column 35 in file BR2385.PCO
    WHERE A.SOC_NO = :PARAM-SOC
    ..................................1
    PCB-S-00223, Undeclared variable "PARAM-SOC".
    when we change the pcbcfg.cfg file with flag : declare_section=no it's compile without error.
    But in this scenario cobol app doesn't run.
    if we declare the undeclared variable in the section
    EXEC SQL BEGIN DECLARE SECTION END-EXEC.
    PARAM-SOC PIC X(25).
    EXEC SQL END DECLARE SECTION END-EXEC.
    and compile it with declare_section=yes then cobol app. run fine.
    Are different files generated (cob,int,gnt) after compilation with the option declare_section=no and declare_section=yes.
    Pls help us in this regards. we have lot of file which having these issue and we don't want to do manual changes "EXEC SQL BEGIN" in it.
    Thanks in advance..

    Your code is faulty and has to be fixed.
    No compilation problem is present, the compiler correctly barfs.
    As this is not a support forum, kindly keep your non-issues out of this forum.
    Thank you!!!
    Sybrand Bakker
    Senior Oracle DBA

  • Occi::Number compilation problem in Linux

    Hi,
    I got following error when I complile my application which uses OCCI (Oracle C++ Call Interface) shiped with Oracle 9.2. I added the compiler flag -Dlint .
    When I dont add the compiler flag I dont get following error. My machine is running RedHat linux 7.3
    /usr/bin/g++ -c -I/opt/ora9/product/9.2/rdbms/demo -I/opt/ora9/product/9.2/rdbms/public -I/opt/ora9/product/9.2/plsql/public -I/opt/ora9/product/9.2/network/public myapp.cpp -g -Wall -DLiS -Dlint -DORACLE -I../include -DQT_THREAD_SUPPORT
    In file included from /opt/ora9/product/9.2/rdbms/demo/occi.h:40,
    from ../include/DatabaseSupport.h:17,
    from myapp.cpp:4:
    /opt/ora9/product/9.2/rdbms/demo/occiData.h:374: `oracle::occi::Number::Number (char)' has already been
    declared in `oracle::occi::Number'
    /opt/ora9/product/9.2/rdbms/demo/occiData.h:408: `oracle::occi::Number::operator char () const' has
    already been declared in `oracle::occi::Number'
    If I dont compile my application with -Dlint compiler flag I cant run the application.
    I think this is a bug in occi::Number class
    Any solusion??
    Thanking in advance
    nkran

    Your code is faulty and has to be fixed.
    No compilation problem is present, the compiler correctly barfs.
    As this is not a support forum, kindly keep your non-issues out of this forum.
    Thank you!!!
    Sybrand Bakker
    Senior Oracle DBA

  • Before Update Trigger compilation problem

    Hello experts! I have a compilation problem for a trigger I am trying to create.
    As a matter of fact it should update INT_INITIAL with the old value of INT_LOCK.
    The compilation fails and the debugger raises an ORA 01747 error (invalid declaration for user table, user column etc.)
    Do you have an idea what is wrong with my code?
    create or replace
    TRIGGER TRIGGER_INT_INITIAL
    BEFORE UPDATE ON  TBL_MATRIX_INTERMEDIATE_RESULT
    FOR EACH ROW
    Begin
      IF NVL(:new.INT_INITIAL, 0) != :old.INT_LOCK THEN
           UPDATE TBL_MATRIX_INTERMEDIATE_RESULT set
          :NEW.INT_INITIAL = :old.INT_LOCK;
      END IF;
    END;Regards,
    Seb

    Hi Seb,
    You don't need to use UPDATE stmt here as you are updating the same table on which your trigger is fired. So it may cause mutating table error too.
    when you use :new.colname it will immediately take care of the new value to be inserted in the respective column.
    So no need to write Update stmt.
    Hence remove,
    UPDATE TBL_MATRIX_INTERMEDIATE_RESULT set And use := is an assignment operator whereas = is to equate..
    :=Twinkle

  • Compiling problem in oracle 11g environment

    Hello mates,
    We have recently migrated from oracle10g to oracle11g. we have lot of pro*c and forms programs.
    my requirement is to compile all those pro*c and form programs in 11g.
    for compiling pro*c programs we have compilation scripts. these compilation scripts are prepared
    based on oracle10g. pro*c programs are compiling fine by using this compilation scripts.
    after migrated to 11g, ihave used same 10g compilation scripts to compile pro*c programs.
    1.while compiling the programs first time, i got these errors
    /oracle/app/product/11.2.0.3_cli/lib32/libsql10.a: No such file or directory
    /oracle/app/product/11.2.0.3_cli/rdbms/lib32/kpudfo.o: No such file or directory
    /oracle/app/product/11.2.0.3_cli/lib32/libpls10.a: No such file or directory
    /oracle/app/product/11.2.0.3_cli/lib32/libpls10.a: No such file or directory
    /oracle/app/product/11.2.0.3_cli/lib32/libpls10.a: No such file or directory
    so i have replace all libsql10.a,libpls10.a,libpls10.a,libpls10.a to libsql11.a,libpls11.a,libpls11.a,libpls11.a
    2.then these errors got resolved but second time compilation it shown below error.
    /oracle/app/product/11.2.0.3_cli/rdbms/lib/kpudfo.o: No such file or directory
    so i have removed kpudfo.o file from compilation script.
    3. i have compiled third time then it shown diffrent error as shown below
    ld: fatal: library -lnapt: not found
    ld: fatal: file /oracle/app/product/11.2.0.3_cli/lib/libclntsh.so: wrong ELF class: ELFCLASS64
    ld: fatal: file /oracle/app/product/11.2.0.3_cli/rdbms/lib/cdf.o: wrong ELF class: ELFCLASS64
    ld: fatal: File processing errors. No output written to ./ebsparam
    i have changed script
    "/usr/local/bin/gcc -m32 -g -DSOLARIS -DSOLARIS2 -I$HOME/include"
    to
    "/usr/local/bin/gcc -m64 -g -DSOLARIS -DSOLARIS2 -I$HOME/include"
    4. then i have compiled again then it shown error as below
    ld: fatal: file /usr18/SIR02551/mydomain/BD/obj/ebsparam.o: wrong ELF class: ELFCLASS32
    ld: fatal: File processing errors. No output written to ./ebsparam
    collect2: ld returned 1 exit status
    because of 32 bit problem i have changed script to 32 to 64. but now it is showing this error
    what is the problem i am not able to understand.
    please help on this
    Thanks
    Edited by: ramadurga.v on Jan 25, 2013 3:10 PM
    Edited by: ramadurga.v on Jan 25, 2013 3:26 PM

    Pl do not post duplicates -
    Compilaton problem in 11g environment
    Compilation problem in 11g environment
    Compilation problem in 11g environment

  • RE: RE : Compile problems

    Doug,
    I also had a very similar error. At first I thought it might have been
    similar to the technote 38525, but in the end I force compiled the workspace
    and re made the distribution and the fcompile worked like normal. So if you
    don't think the technote matches your situation then I recommend force
    compiling your workspace.
    Regards,
    Allister
    -----Original Message-----
    From: [email protected]
    [<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of Ajith Kallambella
    Sent: Thursday, 6 May 1999 23:01
    To: [email protected]; [email protected]
    Subject: RE : Compile problems
    Doug,
    Your method is probably returning a data type that the codegenerator
    is misinterpreting.
    It could be related to a documented problem where a return statement
    returning an unsigned long( or a few other type ) value generates a
    GENERICRETURN instruction, which codegen erroneously believed
    to have no
    operands, causing decompilation errors.
    Take a look at Bug # 38525.
    The suggested work around is not to return unsigned long( or a few other
    data types ).
    Ajith Kallambella M
    Subject: Compile problems
    Has anyone ever seen this error when using fcompile to compile their
    partitions?? The create/compile of the workspace & the
    partitioning of the
    application all went fine. It seems to indicate there may be a
    problem with
    the fetchEncounterWithItsClaim method. What's the IRBlock ?? Any
    help would
    be greatly appreciated!!
    Processing partition generation file:
    /usr/local/bin/forte3j/appdist/hcssdeve/hcssmain/cl27/codegen/hcss
    ma8/hcssma
    8.pgf
    Creating and initializing code generator, this could take some time.
    ERROR: Exiting due to following exception:
    SYSTEM ERROR: Client partition FTCompile_cl0_Client was terminated by
    escaped
    exception. See the remainder of the error stack for more information.
    Class: qqsp_ResourceException
    Error #: [1001, 3]
    Detected at: qqrt_ForteExecAgent::LoadPartition at 1
    Error Time: Wed May 5 17:38:50
    Exception occurred (locally) on partition "Forte_Executor",
    (partitionId
    =
    25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1, taskId =
    [25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1.6]) in application
    "FTCompile_cl0", pid 13061 on node gromit.HealthPartners.com in
    environment <unknown>.
    SYSTEM ERROR: Variable index 71 is outside the range 0 to 26 for the
    IRBlock fetchEncounterWithItsClaim.
    Class: qqsp_Exception
    Error #: [1001, 203]
    Detected at: qqrt_IRBlock::GetTypeIndex at 1
    Last TOOL statement: method ForteCompiler.ProcessPGF
    Error Time: Wed May 5 17:38:50
    Exception occurred (locally) on partition "Forte_Executor",
    (partitionId =
    25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1, taskId =
    [25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1.6]) in application
    "FTCompile_cl0", pid 13061 on node gromit.HealthPartners.com in
    environment <unknown>.
    Doug Scurr
    HealthPartners
    8100 34th Avenue South
    9th Floor
    Minneapolis, MN 55440-1309
    (612)883-7317
    - att-1.unk
    Get Free Email and Do More On The Web. Visit <a href=
    "http://www.msn.com">http://www.msn.com</a>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
    >
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

    Allister,
    That's the only thing(force compile) I could think of to try, so I did & re
    made the distribution last night & it worked fine!!
    Doug Scurr
    HealthPartners
    8100 34th Avenue South
    9th Floor
    Minneapolis, MN 55440-1309
    (612)883-7317
    -----Original Message-----
    From: Allister Dickson [SMTP:[email protected]]
    Sent: Friday, May 07, 1999 1:23 AM
    To: Ajith Kallambella; [email protected];
    [email protected]
    Subject: RE: RE : Compile problems
    Doug,
    I also had a very similar error. At first I thought it might have
    been
    similar to the technote 38525, but in the end I force compiled the
    workspace
    and re made the distribution and the fcompile worked like normal. So
    if you
    don't think the technote matches your situation then I recommend
    force
    compiling your workspace.
    Regards,
    Allister
    > -----Original Message-----
    > From: [email protected]
    > [<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of Ajith
    Kallambella
    > Sent: Thursday, 6 May 1999 23:01
    > To: [email protected]; [email protected]
    > Subject: RE : Compile problems
    >
    >
    > Doug,
    >
    > Your method is probably returning a data type that the
    codegenerator
    > is misinterpreting.
    >
    > It could be related to a documented problem where a return
    statement
    > returning an unsigned long( or a few other type ) value generates
    a
    > GENERICRETURN instruction, which codegen erroneously believed
    > to have no
    > operands, causing decompilation errors.
    >
    > Take a look at Bug # 38525.
    >
    > The suggested work around is not to return unsigned long( or a few
    other
    > data types ).
    >
    >
    > Ajith Kallambella M
    >
    >
    > Subject: Compile problems
    >
    >
    > Has anyone ever seen this error when using fcompile to compile
    their
    > partitions?? The create/compile of the workspace & the
    > partitioning of the
    > application all went fine. It seems to indicate there may be a
    > problem with
    > the fetchEncounterWithItsClaim method. What's the IRBlock ?? Any
    > help would
    > be greatly appreciated!!
    >
    > Processing partition generation file:
    > /usr/local/bin/forte3j/appdist/hcssdeve/hcssmain/cl27/codegen/hcss
    > ma8/hcssma
    > 8.pgf
    > Creating and initializing code generator, this could take some
    time.
    > ERROR: Exiting due to following exception:
    >
    > SYSTEM ERROR: Client partition FTCompile_cl0_Client was terminated
    by
    > escaped
    > exception. See the remainder of the error stack for more
    information.
    > Class: qqsp_ResourceException
    > Error #: [1001, 3]
    > Detected at: qqrt_ForteExecAgent::LoadPartition at 1
    > Error Time: Wed May 5 17:38:50
    > Exception occurred (locally) on partition "Forte_Executor",
    > (partitionId
    > =
    > 25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1, taskId =
    > [25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1.6]) in application
    > "FTCompile_cl0", pid 13061 on node gromit.HealthPartners.com
    in
    > environment <unknown>.
    >
    > SYSTEM ERROR: Variable index 71 is outside the range 0 to 26
    for the
    > IRBlock fetchEncounterWithItsClaim.
    > Class: qqsp_Exception
    > Error #: [1001, 203]
    > Detected at: qqrt_IRBlock::GetTypeIndex at 1
    > Last TOOL statement: method ForteCompiler.ProcessPGF
    > Error Time: Wed May 5 17:38:50
    > Exception occurred (locally) on partition
    "Forte_Executor",
    > (partitionId =
    > 25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1, taskId =
    > [25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1.6]) in
    application
    > "FTCompile_cl0", pid 13061 on node
    gromit.HealthPartners.com in
    > environment <unknown>.
    >
    > Doug Scurr
    > HealthPartners
    > 8100 34th Avenue South
    > 9th Floor
    > Minneapolis, MN 55440-1309
    > (612)883-7317
    >
    >
    > - att-1.unk
    >
    >
    > _______________________________________________________________
    > Get Free Email and Do More On The Web. Visit <a href=
    "http://www.msn.com">http://www.msn.com</a>
    > -
    > To unsubscribe, email '[email protected]' with
    > 'unsubscribe forte-users' as the body of the message.
    > Searchable thread archive
    <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
    >
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

  • XSD Location Problem.

    Hi Gurus,
    After starting the node in a cluster environemnt, often receiving "Unable to load Translation schemas from for http://xmlns.oracle.com/BRM/schemas/BusinessOpcodes due to: XSD Location problem.
    XSD Loading problem."
    This is mainly observed in BRM schemas, has anyone exprienced this? what shall be the workaround/solution other than restarting the container/application?
    We are using SOA 10.1.3.4 MLR 8 and Oracle AIA 2.4.
    Please help.

    The BRM schemas are present in the AIA Components which will be referred by the load balancer url in a clustered environment. However, if in any of the nodes, the url for AIA Components has the local node url instead of load balancer url, this issue occurs.
    Identify the node which is giving the issue (shutting down one node at a time and retrying the operation which gives the error). In the node which has the issue, try doing a search on AIA components to find out if there is any reference using local node url instead of load balancer.
    If you find any, replace with the load balancer url. I had faced a similar issue and I was able to resolve it as I have mentioned above.
    Cheers,
    - AR

Maybe you are looking for