"Occasionally" successful compilation issue on sun4v machine.

Hi,
I have created a thread on JSP section of the forum for this.
Intermittently successful JSP compilation issue
But I am putting the link here too because the only difference between the success and failed case is the platform we are using. We are using Solaris SPARC machines.
The compilation is a success on sun4u machine.
But on sun4v is mostly a failure (sometimes it succeeds though strangely).
I will be very grateful if you can go through the thread I have shared above and share some pointers on this.
Regards

Post Author: usaitconsultant
CA Forum: JAVA
Hi Ted,
Thanks for the reply.The file is not available in the server. Though, I checked CMS and I found an instance in history tab and the status is failed with error below.
Error Message:
A variable prevented the data provider Query 1 with BANRRD30 from being refreshed. (DMA0008).When I checked my codes, I found out that the object Im using is for web intelligence data provider. However, I cannot find any documentation and example for passing parameter values in desktop intelligence data provider. Any idea on this? You think this is not suported by Report Engine SDK?Thanks.

Similar Messages

Intermittently successful JSP compilation issue

Hi,
I am facing a weird issue. I feel this is the right place. If not kindly point me to right place.
We are using Solaris SPARC machines.
We have a bunch of JSP files which compile fine on a sun4u machine.
bash-2.05$ uname -a
SunOS YYYY 5.10 Generic_141444-09 sun4u sparc SUNW,Sun-Fire-V245
But the same bunch of files throws error on compilation on sun4v machine.
bash-2.03$ uname -a
SunOS XXXX 5.10 Generic_141414-01 sun4v sparc SUNW,Sun-Fire-T1000
We are using the weblogic.appc to compile it. These are the options we are using it with to aid debugging.
-g -lineNumbers -verbose -forceGeneration -keepgenerated
What makes it even weird is that around 30% of time the compilation is success. But remaining 70% of time it fails.
The Weblogic installer is same on both machines.
The Java is same on both machines. (jdk1.6)
The error is something like this:
[jspc] Compiling /xyz/abc.jsp
There are 1 nested errors:
weblogic.utils.compiler.ToolFailureException: jspc failed with errors :weblogic.servlet.jsp.CompilationException: abc.jsp:42:18: Syntax error on token "}", { expected after this token
If I open the file at that line number there is no } to be seen.
Also the errors keep varying in content. I mean they are of similar type in the sense that they have Syntax errors but on different compilation runs their contents are different.
Like this is something which we have seen too.
weblogic.utils.compiler.ToolFailureException: jspc failed with errors :weblogic.servlet.jsp.CompilationException: xyz.jsp:34:47: Syntax error on token "if", Identifier expected
The file names vary. The error exact text varies.
But the thing which is really strange is that sometimes it complies just fine.
We clear off all the class files before compiling so that the JSP files do get compiled.
Any pointers as to where to look at?
Regards
Edited by: I_Kept_walking on Sep 8, 2011 7:02 AM
Edited by: I_Kept_walking on Sep 8, 2011 7:07 AM

Its around 70 odd JSP. And also i do not see any out of memory errors.
Is there any way I can get more info out of it.
I have seen that -g parameter in case of weblogic appc compiler puts the debug info in the class file.
-g :Compiles debugging information into a class file.
Which class file? Where its located? And if anyway to analyze that class file??Anyone has any idea?

Is there anyone at all here who has successfully compiled and deployed an SSRS custom report item in VS2012?

Is there anyone at all here who has successfully compiled and deployed an SSRS custom report item in VS2012? Is there a demo out there that actually works in VS2012? Is there anyone who has actually been able to compile and deploy that
apparently obsolete Polygons demo? (Pardon my impatience but I'm running a bit short of time here.)
After much hacking and googling I was able to get Polygons to compile but I still can't deploy it to the toolbox. ('The custom report item type PolygonsDesigner is not installed'). I've modified the RSReportDesigner.config
as instructed but I have no rssrvpolicy.config file on my local machine and
as yet I have no idea if that is necessary for local development.
In order to get it to compile I first added the reference C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies\Microsoft.ReportingServices.ProcessingCore.dll to both projects.
To the PolygonsDesigner Project I also added the references:
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies\Microsoft.ReportDesigner.Controls.dll
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies\Microsoft.ReportingServices.Designer.11.0.dll
C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\Microsoft.ReportingServices.Interfaces.dll
Are these the correct references?
Exactly what software do you need installed on your local machine in addition to VS2012 in order to create a custom control?
(Designer.11.0 was added per the instructions in reference: https://connect.microsoft.com/VisualStudio/feedback/details/783391/unable-to-integrate-previously-working-ssrs-custom-report-item-to-vs-2012s-toolbox
After that I added the alias RSDesigner to it's properties and extern alias RSDesigner; at the top of the PolygonsDesigner.cs file. )
As of now, the top of the PolygonsDesigner.cs is as follows. I don't recall making any other changes to the code. As far as I can remember this is all I did in order to be able to compile the code in VS2012.
extern alias RSDesigner;
using System;
using System.ComponentModel;
using System.ComponentModel.Design;
using System.Collections;
using System.Collections.Generic;
using System.Diagnostics;
using System.Drawing;
using System.Windows.Forms;
using Microsoft.ReportDesigner;
using Microsoft.ReportDesigner.Design;
using Microsoft.ReportingServices.Interfaces;
using Microsoft.ReportingServices.RdlObjectModel;
using System.Xml;
using System.Xml.Xsl;
using System.Xml.XPath;
[LocalizedName("Polygons")]
[Editor(typeof(CustomEditor), typeof(ComponentEditor))]
[ToolboxBitmap(typeof(PolygonsDesigner), "Polygons.ico")]
[CustomReportItem("Polygons")]
[ToolboxItem(typeof(RSDesigner::Microsoft.ReportDesigner.Shell.CRIToolboxItem))]
[System.CLSCompliant(false)]
public class PolygonsDesigner : CustomReportItemDesigner
{ etc...

Just fixed this myself.
It appears the documentation online is wrong and the sample code is missing a reference to a reporting services dll and an attribute.
What you need to do to get it working in VS2012 is add a reference to: Microsoft.ReportingServices.designer.11.0.dll to the PolygonsDesigner project and then add the following attribute to the PolygonsDesigner class: [ToolboxItem(typeof(Microsoft.ReportDesigner.Shell.CRIToolboxItem))]
I also removed the [System.CLSCompliant(false)] attribute.
You then recompile and place both dlls in C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies directory and the PolygonsDesigner.dll into the C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\bin
or what ever is you reporting services path.
You also need to change the Microsoft example for the rereportserver.config file to:
 <ReportItemDesigner>
 <ReportItem Name="Polygons" Type="Microsoft.Samples.ReportingServices.PolygonsDesigner, PolygonsDesigner" />
 </ReportItemDesigner>
 <ReportItems>
 <ReportItem Name="Polygons" Type="Microsoft.Samples.ReportingServices.PolygonsCRI,PolygonsCRI"/>
 </ReportItems>
Notice that I changed the namespaces and class to what is in the actual code so if you change it make sure you change it here.
And here in the RSReportDesigner.config:
<ReportItems>
 <ReportItem Name="Polygons" Type="Microsoft.Samples.ReportingServices.PolygonsCustomReportItem,PolygonsCRI" />
 </ReportItems>
 <ReportItemDesigner>
 <ReportItem Name="Polygons" Type="Microsoft.Samples.ReportingServices.PolygonsDesigner, PolygonsDesigner" />
 </ReportItemDesigner>
 <ReportItemConverter>
 <Converter Source="Chart" Target="Polygons" Type="PolygonsCRI.PolygonsConverter, PolygonsDesigner" />
 </ReportItemConverter>
Notice I haven't changed the last part as I didn't know what the PolygonsCRI.PolygonsConverter was.
And make sure the rssrvpolicy.config looks like this:
 <CodeGroup class="UnionCodeGroup" version="1" PermissionSetName="FullTrust" Description="This code group grants PolygonsCRI.dll FullTrust permission. ">
 <IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Program Files\Microsoft SQL Server\MSRS10_50.SQLSERVER\Reporting Services\ReportServer\bin\PolygonsCRI.dll" />
 </CodeGroup>
After a restart of ssrs and relaunch of VS2012 I opened a test project and added the PolygonsDesigner.dll to the toolbox and it works.
Jamie

FPGA code successfully compiled in 2010 is giving compilation error in 2014.

I have developed RS485 FPGA code and successfully compiled with LabVIEW FPGA 2010.
Later changed the software to 2014 and installed Xilinx 14.7.
Now if I compile the same code with LabVIEW 2014 compile worker, i am getting error 'Process "Synthesis" failed'.
I am using a case structure with Error cluster as selector, So the case structure has 'No error' and 'Error' cases.
If I change the selector to 'True/False' then the compilation works.
Below is the error that i am getting when using Case structure with Error cluster as selector
LabVIEW FPGA: The compilation failed due to a Xilinx error. Details: ERROR:HDLParsers:1401 - "C:/NIFPGA/jobs/JyWfWcc_Gv3a9ah/NiFpgaAG_00000041_CaseStructureFrame_0001.vhd" Line 41. Object tunnel_s_error_out_2007 of mode OUT cannot be read. ERROR:HDLParsers:1401 - "C:/NIFPGA/jobs/JyWfWcc_Gv3a9ah/NiFpgaAG_00000041_CaseStructureFrame_0001.vhd" Line 42. Object tunnel_s_error_out_2007 of mode OUT cannot be read. --> Total memory usage is 190240 kilobytes Number of errors : 2 ( 0 filtered) Number of warnings: 1 ( 0 filtered) Number of infos : 0 ( 0 filtered)

Attached FPGA_error_2014.jpg which depicts the working and 'not working' code in 2014.
In 'Not working' code,the selector terminal is error cluster.
I am able to resolve the issue just by changing the selecter terminal to boolean as in 'working code'.
But both sets of software code works fine in version 2010.
Attachments:
FPGA_error_2014.jpg ‏128 KB

Same float code compiled differently on different machines

Hi,
Scenario: same project build on different machines. and then both the application executed on
same machine .. giving slightly different results..(like 23.07499 to 23.07500)
project involves many float operations. project build on vs2013. c++
there is difference oberved in the final value of float calculations.. like 23.07499 to 23.07500
seems , Same float code compiled differently on different machines, any input
Regards,
james

>Scenario: same project build on different machines. and then both the application executed on same machine ..
giving slightly different results..(like 23.07499 to 23.07500)
Do you get consistent results with the same executable each time you
run it?
Assuming you do, and the only difference is the EXEs, what's the
difference between them - there must be something. Have a look at "How
to compare binary images of the same project builds"
https://support.microsoft.com/en-us/kb/164151/ and see if that sheds
any light onto the issue.
Dave

Communicating with C Compiler Toolchain on Remote Machine

Hi,
I'm trying to develop a target for LabVIEW Embedded where the C compiler resides on another machine. I have a Debian Linux machine hosting my BSP development for my target (MPC5121e); gcc cross-compiler w/patches, ltib, u-boot, etc. is all configured and running; linux loads on my target and NFS mounts a file system hosted on this machine.
All of the target examples for LV Embedded have the development tools hosted on the same machine as LabVIEW (Windows); though some use Cygwin to "fake" out a linux development toolchain. I'm trying not to duplicate my linux hosted development toolchain on Windows; though possible; it will probably create a whole host of other problems. Thus; is there a "proper" way of calling a toolchain hosted on another machine? Should I still use the system exec wrapper? RPC calls? or some type of script to ftp the files to the remote machine and compile them? Any suggestions or documentation would be greatly appreciated.
Thanks.

Wow, thanks for all this feedback! I'll address some of the issues below:
- While using the target
editor; if path to LEP file is too long; the actual file name isn't
shown; and there isn't a way to see it by browsing; thus you must
manually view the TgtSupp.xml file to see what it is.
I'm not seeing this behavior. If the path to the plug-in VI is too long, it will wrap the name. If you place your cursor in the field and move it with the arrow keys, you should be able to see the full VI name, line by line. If you see different behavior, let me know what page/tab of the Target Editor you see it in and I will try to reproduce it.
- If there is an error in one of the LEP vi's (i.e. vi is not executable for linkage or other reasons); there is no indication of this while either using the target editor or when configuring a project for that embedded target. Weird stuff happens such as LEP's pointed to by the Shortcut Menu Items & Category tabs via Target Editor; sometimes do not show up in the project manager. I've spent way too much time trying to figure this out. I eventually printed out the TgtSupp.xml file and manually opened up each LEP vi to ensure they opened without errors (which naturally occur when you're trying to develop a new target).
As I develop plug-in VIs, I do so with them in the Windows target context, so that I can verify that they should run properly. Also, I set the INI token projectDebugPumpOSMsgs=True (per the readme) so that I can debug plug-in VIs. It is true that the target editor does not warn you when you give it paths to broken VIs. A more proactive detection of broken VIs by the Target Editor could make things easier on LV MPU SDK developers.
- Need better description / documentation on
calling details for LEP functions; i.e. - wrapper functions that are
there to integrate with the rest of the development system. The
developer shouldn't have to look at example code in order to reverse
engineer this stuff.
I assume you are talking about the architecture of some of the example targets that use VI references for many of the example targets. This architecture scales very well when making new targets, but it is probably overkill when you just want to make a single target, and it is probably easier to just have a simple set of VIs to build/download/run/debug. Which VIs would you like to be more well-documented?
- Need some documentation of the mechanism
used to store parameters for targets & build options. This is some
black-box infrastructure that doesn't appear to be described anywhere;
with password protected vi's. Again; the developer shouldn't have to
look at example code in order to reverse engineer this stuff when
developing their own target. The
LEP_Utilities_GetSetProjectData_Variant does have a help file, but I
haven't seen documentation on how to "properly" use these in any of the
manuals, training or even example code (comments).
The LEP_Utilities_GetSetProjectData is a very important part of creating VIs. The VI documentation describes its behavior, although I'm sure it could use some more explanation. When you set project data, you are essentially telling LabVIEW that you want to save that variable to the lvproj file (on next project save). This data can be saved for the entire target, or per build specification. Getprojectdata allows you to retrieve that information the next time the project is opened. The Embedded Development Module palette contains many VIs that can be used in the creation of a new target. Please let me know if you find the VI documentation for any of these to be insufficient.
- How are
embedded target lists unified across the targets directory; i.e.
targets/NI/embedded/unix and targets/mycompany/embedded/unix; I've seen
some strange behaviour when selecting a target at the project level
because of this. This may be due to the fact that I copied a target
from the targets/NI/embedded/unix and put it into
targets/mycompany/embedded/unix for modification; maybe a taboo; but I
could not find any documentation on this.
All sorts of cross-linking errors might occur from copying a directory of plug-n VIs. The Porting Guide describes the directory architecture. This architecture is important because when LabVIEW is opened, it looks in these specific locations to populate the available embedded targets. You can use the Target Editor to create copies of targets (use Save/Save As), and this will relink/rename VIs.
Please keep the feedback coming, and let me know if you have further questions.
Michael P
National Instruments

Runtime error after successful compile and link with cl.exe

Finally, got the configuration for cl.exe and link.exe right and got a successful compile and link to produce a dll. Then ran the main method of my Java class. The main method calls the constructor, and loading the class runs the static block which loads the native dll. I get one of those error files of the type hs_err_pid4064.log. The file is as follows:
# An unexpected error has been detected by Java Runtime Environment:
# Internal Error (0xe06d7363), pid=4064, tid=3576
# Java VM: Java HotSpot(TM) Client VM (10.0-b22 mixed mode, sharing windows-x86)
# Problematic frame:
# C [kernel32.dll+0x12aeb]
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
--------------- T H R E A D ---------------
Current thread (0x00395800): JavaThread "main" [_thread_in_native, id=3576, stack(0x003b0000,0x00400000)]
siginfo: ExceptionCode=0xe06d7363, ExceptionInformation=0x19930520 0x003fdf14 0x02de7b04
Registers:
EAX=0x003fde4c, EBX=0x00000000, ECX=0x00000000, EDX=0x02f80600
ESP=0x003fde48, EBP=0x003fde9c, ESI=0x003fdedc, EDI=0x003fdedc
EIP=0x7c812aeb, EFLAGS=0x00000206
Top of Stack: (sp=0x003fde48)
0x003fde48: 02de1de0 e06d7363 00000001 00000000
0x003fde58: 7c812aeb 00000003 19930520 003fdf14
0x003fde68: 02de7b04 02e80087 003fdf14 003fdf28
0x003fde78: 02e99500 00000039 003fde70 00000039
0x003fde88: 003fdec8 02e81a50 02eabf00 003fdf14
0x003fde98: 003fdf28 003fdedc 02dce583 e06d7363
0x003fdea8: 00000001 00000003 003fded0 02a72388
0x003fdeb8: 00000000 e06d7363 00000001 00000000
Instructions: (pc=0x7c812aeb)
0x7c812adb: 8d 7d c4 f3 a5 5f 8d 45 b0 50 ff 15 10 15 80 7c
0x7c812aeb: 5e c9 c2 10 00 85 ff 0f 8e 36 93 ff ff 8b 55 fc
Stack: [0x003b0000,0x00400000], sp=0x003fde48, free space=311k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [kernel32.dll+0x12aeb]
C [summarizer37.dll+0x1e583]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
v ~BufferBlob::Interpreter
v ~BufferBlob::Interpreter
v ~BufferBlob::Interpreter
v ~BufferBlob::StubRoutines (1)
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x02a66000 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=3108, stack(0x02d10000,0x02d60000)]
0x02a58000 JavaThread "CompilerThread0" daemon [_thread_blocked, id=2488, stack(0x02cc0000,0x02d10000)]
0x02a56c00 JavaThread "Attach Listener" daemon [_thread_blocked, id=2508, stack(0x02c70000,0x02cc0000)]
0x02a56000 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=3720, stack(0x02c20000,0x02c70000)]
0x02a51800 JavaThread "Finalizer" daemon [_thread_blocked, id=2968, stack(0x02bd0000,0x02c20000)]
0x02a4d400 JavaThread "Reference Handler" daemon [_thread_blocked, id=600, stack(0x02b80000,0x02bd0000)]
=>0x00395800 JavaThread "main" [_thread_in_native, id=3576, stack(0x003b0000,0x00400000)]
Other Threads:
0x02a4c000 VMThread [stack: 0x02b30000,0x02b80000] [id=2528]
0x02a67000 WatcherThread [stack: 0x02d60000,0x02db0000] [id=1604]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
def new generation total 960K, used 195K [0x22960000, 0x22a60000, 0x22e40000)
eden space 896K, 21% used [0x22960000, 0x22990c38, 0x22a40000)
from space 64K, 0% used [0x22a40000, 0x22a40000, 0x22a50000)
to space 64K, 0% used [0x22a50000, 0x22a50000, 0x22a60000)
tenured generation total 4096K, used 0K [0x22e40000, 0x23240000, 0x26960000)
the space 4096K, 0% used [0x22e40000, 0x22e40000, 0x22e40200, 0x23240000)
compacting perm gen total 12288K, used 22K [0x26960000, 0x27560000, 0x2a960000)
the space 12288K, 0% used [0x26960000, 0x269658c8, 0x26965a00, 0x27560000)
ro space 8192K, 66% used [0x2a960000, 0x2aeb0e10, 0x2aeb1000, 0x2b160000)
rw space 12288K, 52% used [0x2b160000, 0x2b7b04c8, 0x2b7b0600, 0x2bd60000)
Dynamic libraries:
0x00400000 - 0x00423000      C:\Program Files\Java\jdk1.6.0_06\bin\javaw.exe
0x7c900000 - 0x7c9af000      C:\WINDOWS\system32\ntdll.dll
0x7c800000 - 0x7c8f6000      C:\WINDOWS\system32\kernel32.dll
0x77dd0000 - 0x77e6b000      C:\WINDOWS\system32\ADVAPI32.dll
0x77e70000 - 0x77f02000      C:\WINDOWS\system32\RPCRT4.dll
0x77fe0000 - 0x77ff1000      C:\WINDOWS\system32\Secur32.dll
0x7e410000 - 0x7e4a1000      C:\WINDOWS\system32\USER32.dll
0x77f10000 - 0x77f59000      C:\WINDOWS\system32\GDI32.dll
0x7c340000 - 0x7c396000      C:\Program Files\Java\jdk1.6.0_06\jre\bin\msvcr71.dll
0x6d870000 - 0x6dac0000      C:\Program Files\Java\jdk1.6.0_06\jre\bin\client\jvm.dll
0x76b40000 - 0x76b6d000      C:\WINDOWS\system32\WINMM.dll
0x6d320000 - 0x6d328000      C:\Program Files\Java\jdk1.6.0_06\jre\bin\hpi.dll
0x76bf0000 - 0x76bfb000      C:\WINDOWS\system32\PSAPI.DLL
0x6d820000 - 0x6d82c000      C:\Program Files\Java\jdk1.6.0_06\jre\bin\verify.dll
0x6d3c0000 - 0x6d3df000      C:\Program Files\Java\jdk1.6.0_06\jre\bin\java.dll
0x6d860000 - 0x6d86f000      C:\Program Files\Java\jdk1.6.0_06\jre\bin\zip.dll
0x10000000 - 0x10006000      D:\Servers\SummarizerServer\native\jsummarizer.dll
0x02db0000 - 0x02df2000      D:\Servers\SummarizerServer\native\summarizer37.dll
0x02e00000 - 0x02f6d000      D:\Servers\SummarizerServer\native\platform37.dll
0x4a800000 - 0x4a893000      D:\Servers\SummarizerServer\native\icuuc30.dll
0x4ad00000 - 0x4b52d000      D:\Servers\SummarizerServer\native\icudt30.dll
0x5b860000 - 0x5b8b5000      C:\WINDOWS\system32\NETAPI32.dll
0x77c10000 - 0x77c68000      C:\WINDOWS\system32\msvcrt.dll
VM Arguments:
jvm_args: -Djava.library.path=native
java_command: com.sra.pipeline.servers.summarizer.JSummarizer
Launcher Type: SUN_STANDARD
Environment Variables:
JAVA_HOME=C:\Program Files\Java\jdk1.6.0_06
CLASSPATH=.;C:\Program Files\Java\jre1.6.0_06\lib\ext\QTJava.zip
PATH=D:\Servers\SummarizerServer\native;C:\Program Files\Microsoft Visual Studio 9.0\VC\redist\x86\Microsoft.VC90.CRT
USERNAME=Jim Jones
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 7, GenuineIntel
--------------- S Y S T E M ---------------
OS: Windows XP Build 2600 Service Pack 3
CPU:total 1 (1 cores per cpu, 1 threads per core) family 15 model 2 stepping 7, cmov, cx8, fxsr, mmx, sse, sse2
Memory: 4k page, physical 1048032k(245796k free), swap 2521804k(1060880k free)
vm_info: Java HotSpot(TM) Client VM (10.0-b22) for windows-x86 JRE (1.6.0_06-b02), built on Mar 25 2008 01:22:05 by "java_re" with MS VC++ 7.1
time: Mon Sep 01 15:22:10 2008
elapsed time: 0 seconds
The dll I'm wrapping is C++ VC++ compiled.
Would like to know what I do to trouble-shoot this error and hope to fix it?
Jim

Using Java print statement was able to show that the my JNI dll was being loaded and that the problem was in the first call to one of my JNI functions. Then by using "DebugBreak()" in that function and gradually moving it down line by line through the function was able to isolate the line causing the problem. Unfortunately it is the line where I call a function from the dll I'm wrapping. See newer thread.

Pro*C - PERCENT_RANK() compilation issue

Hello,
I have a pro*C compilation issue, while using PERCENT_RANK() in-built function. I am using Oracle 10.2.0.4.
Here are the details :
The Pro*C code :
================================================== ========
int srccct2_insert()
EXEC SQL
select * from (
select
trad_code,
comp_code,
file_code,
insp_yymm,
poly_numb,
entr_numb,
data_code,
caus_date,
insd_code,
rule_ordr,
sex_code,
entr_age,
resd_numb,
entr_name,
hire_date,
entr_date,
work_year,
hire_grad,
datt_entr,
ijry_entr,
wkdt_entr,
base_saly,
expt_amnt,
rsrv_rato,
rsrv_amnt,
PERCENT_RANK() OVER (ORDER BY base_saly) pr FROM SRCCCT2 where trad_code = 'N' AND
comp_code = '01' AND
insp_yymm = '200403' AND
data_code = 'B' AND
hire_grad = '2' AND
base_saly > 0)
where pr > 0.05 and pr < 0.95 and base_saly > 641840;
return SUCCESS;
================================================== ======
I am compiling it like this :
/oracle/product/10.2.0/bin/proc iname=srascs01.pc ireclen=320 oreclen=320 sqlcheck=full userid=retr/rteru maxopencursors=32 dbms=v8 char_map=varchar2 release_cursor=yes include=/oracle/product/10.2.0/precomp/public include=/ihome/hp/../common/include include=/ihome/retr/include include=/usr/include include=/ihome/hp/portlib DEFINE=HPUX
I have put the same sql statements in the sql promt and it works fine. But in Pro*C when i compile it using above options, here is the error :
================================================== ======
Pro*C/C++: Release 10.2.0.4.0 - Production on Thu Feb 25 00:57:42 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
System default option values taken from: /oracle/product/10.2.0/precomp/admin/pcscfg.cfg
Syntax error at line 192, column 28, file srascs01.pc:
Error at line 192, column 28 in file srascs01.pc
PERCENT_RANK() OVER (ORDER BY base_saly) pr
...........................1
PCC-S-02201, Encountered the symbol "(" when expecting one of the following:
, into, from,
Error at line 0, column 0 in file srascs01.pc PCC-F-02102, Fatal error while doing C preprocessing
*** Error exit code 1
Stop.
*** Error exit code 1
Stop.
================================================== =======
After searching in this website, i saw a related thread. But that solution did not work for me. I have posted a reply on that aswell, for Mark_Williams. Here is the related link:
Re: help for analysis function in PRO*C
Please help me on this.
Thanks,
Kumar

Hi Sumit,
Thanks much for a reply.
I am very novice for Pro*C. Please bear with me, if i sound odd anywhere.
I did check the program again. When i leave EXEC SQL and put the whole SELECT statement in double quotes and then postfix back slashes at each line in the SELECT statement, compilation succeeds. But I am just wondering, if this works fine, even if we don't use, "EXEC SQL" ?
When we use "EXEC SQL" and double quotes also, there seems to be two double quotes before SELECT and so compilation fails, with the below error msg. I think "EXEC SQL" is also appending a double quote.(??)
I did not really understand when you said "declaring the sql statement and calling EXEC SQL PREPARE". Are you talking about declaring the sql statement in sqlplus ?
If the above method of removing "EXEC SQL" and using double quotes and slashes is correct, then i think we anyway need not do anything else as the compilation went through.
Thanks again,
-Kumar

Batik-related compiler issue

<div class=Section1> I received this error calling the flex2.tools.Compiler’s main[] method. The MXML input compiles successfully in the Flex 2 builder. I wanted to check to see if anyone had experienced this before digging deeper into source code.<o:p></o:p> <o:p> </o:p> --Scott<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> ------------------------------------------------------------------------- ----------------------<o:p></o:p> <o:p> </o:p> font-family:"Courier New";color:red'>Error: org.apache.batik.css.parser.Parser.getLineNumber()I<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New"'><o:p> </o:p> font-family:"Courier New";color:red'>java.lang.NoSuchMethodError: org.apache.batik.css.parser.Parser.getLineNumber()I<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flash.css.StyleParser.getLineNumber(font-family:"Courier New";color:navy'>StyleParser.java:208<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flash.css.StyleDocumentHandler.startFontFace(10.0pt;font-family:"Courier New";color:navy'>StyleDocumentHandler.java:100<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at org.apache.batik.css.parser.Parser.parseFontFaceRule(<span style='font-size:10.0pt;font-family:"Courier New";color:navy'>Parser.java:484<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at org.apache.batik.css.parser.Parser.parseStyleSheet(<span style='font-size:10.0pt;font-family:"Courier New";color:navy'>Parser.java:224<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flash.css.StyleParser.init(<span style='font-size:10.0pt;font-family:"Courier New";color:navy'>StyleParser.java:172<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flash.css.StyleParser.<init>(font-family:"Courier New";color:navy'>StyleParser.java:106<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flash.css.StyleSheet.parse("Courier New";color:navy'>StyleSheet.java:5410.0pt;font-family:"Courier New";color:red'>)10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.mxml.analyzer.SyntaxAnalyzer.parseStyle(<span style='font-size:10.0pt;font-family:"Courier New";color:navy'>SyntaxAnalyzer.java:551<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.mxml.analyzer.SyntaxAnalyzer.analyze(<span style='font-size:10.0pt;font-family:"Courier New";color:navy'>SyntaxAnalyzer.java:122<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.mxml.dom.StyleNode.analyze(10.0pt;font-family:"Courier New";color:navy'>StyleNode.java:50<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.mxml.dom.AnalyzerAdapter.traverse(<span style='font-size:10.0pt;font-family:"Courier New";color:navy'>AnalyzerAdapter.java:172<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.mxml.dom.AnalyzerAdapter.analyze(<span style='font-size:10.0pt;font-family:"Courier New";color:navy'>AnalyzerAdapter.java:164<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.mxml.analyzer.SyntaxAnalyzer.analyze(<span style='font-size:10.0pt;font-family:"Courier New";color:navy'>SyntaxAnalyzer.java:55<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.mxml.dom.Node.analyze(font-family:"Courier New";color:navy'>Node.java:47<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.mxml.InterfaceCompiler.parse1(10.0pt;font-family:"Courier New";color:navy'>InterfaceCompiler.java:222<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.mxml.Compiler.parse1(font-family:"Courier New";color:navy'>Compiler.java:95<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.API.parse1("Courier New";color:navy'>API.java:2306font-family:"Courier New";color:red'>)font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.API.parse1("Courier New";color:navy'>API.java:2259font-family:"Courier New";color:red'>)font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.API.batch2("Courier New";color:navy'>API.java:367font-family:"Courier New";color:red'>)font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.API.batch("Courier New";color:navy'>API.java:1108font-family:"Courier New";color:red'>)font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.API.compile("Courier New";color:navy'>API.java:1281font-family:"Courier New";color:red'>)font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.compiler.API.compile("Courier New";color:navy'>API.java:1201font-family:"Courier New";color:red'>)font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.tools.Compiler.mxmlc("Courier New";color:navy'>Compiler.java:24010.0pt;font-family:"Courier New";color:red'>)10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at flex2.tools.Compiler.main("Courier New";color:navy'>Compiler.java:5310.0pt;font-family:"Courier New";color:red'>)10.0pt;font-family:"Courier New"'><o:p></o:p> font-family:"Courier New";color:red'> at net.sf.jasperreports.export.flex.JRSwfExporter.exportReportToStream(<span style='font-size:10.0pt;font-family:"Courier New";color:navy'>JRSwfExporter.java:268<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p> color:red'> at net.sf.jasperreports.export.flex.JRSwfExporter.exportReport(<span style='font-size:10.0pt;font-family:"Courier New";color:navy'>JRSwfExporter.java:177<span style='font-size:10.0pt;font-family:"Courier New";color:red'>)<o:p></o:p> </div>

Would you provide some details on how you’re calling this, which branch (e.g. Compiler is now known as Mxmlc on the trunk)? You need to have all libs from trunk/lib on the classpath.
- Jono
From: chauncy <[email protected]>
Reply-To: <[email protected]>
Date: Thu, 17 Apr 2008 10:31:31 -0700
To: <[email protected]>
Subject: Batik-related compiler issue
A new discussion was started by chauncy in
Developers --
 Batik-related compiler issue
I received this error calling the flex2.tools.Compiler’s main[] method. The MXML input compiles successfully in the Flex 2 builder. I wanted to check to see if anyone had experienced this before digging deeper into source code.
--Scott
Error: org.apache.batik.css.parser.Parser.getLineNumber()I
java.lang.NoSuchMethodError: org.apache.batik.css.parser.Parser.getLineNumber()I
 at flash.css.StyleParser.getLineNumber(
StyleParser.java:208
 at flash.css.StyleDocumentHandler.startFontFace(
StyleDocumentHandler.java:100
 at org.apache.batik.css.parser.Parser.parseFontFaceRule(
Parser.java:484
 at org.apache.batik.css.parser.Parser.parseStyleSheet(
Parser.java:224
 at flash.css.StyleParser.init(
StyleParser.java:172
 at flash.css.StyleParser.<init>(
StyleParser.java:106
 at flash.css.StyleSheet.parse(
StyleSheet.java:54
 at flex2.compiler.mxml.analyzer.SyntaxAnalyzer.parseStyle(
SyntaxAnalyzer.java:551
 at flex2.compiler.mxml.analyzer.SyntaxAnalyzer.analyze(
SyntaxAnalyzer.java:122
 at flex2.compiler.mxml.dom.StyleNode.analyze(
StyleNode.java:50
 at flex2.compiler.mxml.dom.AnalyzerAdapter.traverse(
AnalyzerAdapter.java:172
 at flex2.compiler.mxml.dom.AnalyzerAdapter.analyze(
AnalyzerAdapter.java:164
 at flex2.compiler.mxml.analyzer.SyntaxAnalyzer.analyze(
SyntaxAnalyzer.java:55
 at flex2.compiler.mxml.dom.Node.analyze(
Node.java:47
 at flex2.compiler.mxml.InterfaceCompiler.parse1(
InterfaceCompiler.java:222
 at flex2.compiler.mxml.Compiler.parse1(
Compiler.java:95
 at flex2.compiler.API.parse1(
API.java:2306
 at flex2.compiler.API.parse1(
API.java:2259
 at flex2.compiler.API.batch2(
API.java:367
 at flex2.compiler.API.batch(
API.java:1108
 at flex2.compiler.API.compile(
API.java:1281
 at flex2.compiler.API.compile(
API.java:1201
 at flex2.tools.Compiler.mxmlc(
Compiler.java:240
 at flex2.tools.Compiler.main(
Compiler.java:53
 at net.sf.jasperreports.export.flex.JRSwfExporter.exportReportToStream(
JRSwfExporter.java:268
 at net.sf.jasperreports.export.flex.JRSwfExporter.exportReport(
JRSwfExporter.java:177
View/reply at Batik-related compiler issue
<http://www.adobeforums.com/webx?13@@.59b50561>
Replies by email are OK.
Use the unsubscribe
<http://www.adobeforums.com/webx?280@@.59b50561!folder=.3c060fa3> form to cancel your email subscription.

SCCM 2007 Client doesn't successfully compiled policy

We have McAfee endpoint product installed on windows XP client, we found client without McAfee endpoint product can successfully download package before the program runs, but client with McAfee endpoint product will not download package before the program
runs, instead it will wait to the time for program runs then start download package.
We compare the AgentPolicy log on the normal client vs. failed download client, we found in the failed download client the policy will not successfully compiled, but we didn't see any valuable message for troubleshooting.
Please advise how to troubleshooting this issue.
PS. All McAfee endpoint blocking/restricting function has been disabled.
Regards
Steven

Hi,
Can you please upload the logs file PolicyEvaluator and PolicyAgent.log to Skydrive and post the link here?
Juke Chou
TechNet Community Support

Compilation problem in diferent machine

Hi All,
I am having some problem in compiling my code in different machine.
The problem is that i have defined classes which access each other in a cyclic manner. e.g. class A access the class B, class B access class A and C while class C access A and B.
So it didn't give me any problem when i was coding since it was a step by step process so class B was already compiled when class A needed it. Now that i am doing the cmpilation from the scratch i am getting the above problem.
In C++ one can do a forward declaration. I tried that here but it is not working..
Could you guys give me any suggestions...
Thanks
Amitabh

I'm kind of confused by what you mean. You say you
can't compile on a different machine but it seems like
you are trying to use multiple inheritence in Java
which isn't allowed. Have you even got this to compile
in Java at all? Post some code.Hi JustLee,
By accessing a class i mean i am just calling the public memebers of that class I am not inheriting from that class.
here is a part of the code
There are 4 classes: RouteTable, RouteTableEntry, InterfaceList and InterfaceListEntry
the following code is in RouteTable
public static boolean IfEntryPresentInRouteTable(InterfaceListEntry tmpEntry){
Iterator r = routingTable.iterator();
while (r.hasNext()){
RouteTableEntry tmpRoute = (RouteTableEntry)r.next();
if (tmpEntry.ipAddress.equals(tmpRoute.dstIP) && tmpRoute.selfRoute == 1)
return true;
return false;
It access the InterfaceListEntry class. Now InterfaceListEntry, i have defined in a file named InterfaceList. And InterfaceList calls the members of RouteTableEntry and RouteTable which are defined in the same file viz. RouteTable.
So because of this cyclic accesing of classes the compilation is not going through
Does it make any clearer?
Amitabh

Lion 10.7.4 issues with Virtual Machines

Hi,
I'm having lot of issues with virtual machines (both Parallels and VMWare)
since having update to lion 10.7.4.
I make myself:
If I switch on Mac OS a run any vitrual machine software
I can run Windows XP and Ubuntu at same time with no issue and very fluently.
But, if I switch on Mac OS and start using Eclipse, Safari 5.2 and other production stuff and
want to use vmware or paralles
they become unusable even if I quit all the tasks ans "purge" memory.
(eg: if i click start button on windows I have to wait seconds before the start menu pops up)
Any Idea?
I have MacBook Pro 13 Unibody mid 2009 with SSD Drive AND 4GB of RAM
and I had no such issues with Lion 10.7.3

alex_75 wrote:
As you wrote before, virtual mchines need big chunks of contigous RAM and
2,5 GB of free RAM wuold have enough ammount of such a RAM.
No, it wouldn't. 2.5 GB of free RAM could consist of 5 chunks of 500 MB of contiguous RAM, separated by RAM allocated by other processes.
Here is a hypothetical memory map. Assume a is application memory, o is operating system memory, and - is free memory.
boot:           oooo--------------
run app1:    ooooaao-----------
run app2:    ooooaaoaaaaaaoo---quit app1:   oooo---aaaaaaoo---
Maybe there is some issue in the way 10.7.4, in some perticolar situations, handle the process of freeing RAM.
What you can't accept, and I don't know why, is that before the update to 10.7.4 everithing was fine.
I don't know why you don't beleve me.
There is nothing in the 10.7.4 update description that mentions a re-write of the virtual memory system. http://support.apple.com/kb/HT5167
I just worte here to see if someone could give any advice to do further invesigations.
I know the price of upgrading RAM but I think that this would be a "microsoft like" solution
and I'm trying to find what service or task or whatever is creating this issue.
The only thing "Microsoft like" about buying more RAM is the fact that you need it to run your Microsoft operating systems. It has been this way as long as I can remember. I upgraded my MacBook to 4 GB RAM in 2008 just so I could run Windows more easily.
Perhaps you have your virtual memory settings too high. Depending on what you are doing in the VM, you may not need the default settings. XP will run low-intensity tasks with a 500 MB VM size. It will run just about anything in 1 GB. Linux should run fine in the same range too.

How to successfully compile form in Linux

Hi there,
I have a form, which is called: TESTFORM.fmb
I tried to compile this form using the following command:
export LD_LIBRARY_PATH=/u0/oracle/prodora/8.0.6/lib
f60gen module=/u0/oracle/prodappl/ar/11.5.0/forms/US/TESTFORM.fmb USERID=apps/passwordAlthough fmx is successfully generated, the following error is also encountered during compile:
FRM-18108: Failed to load the following objects.
Source Module:APPSTAND
Source Object: STANDARD_PC_AND_VA
Source Module:APPSTAND
Source Object: STANDARD_TOOLBAR
Source Module:APPSTAND
Source Object: STANDARD_CALENDAR
I look for APPSTAND.fmb and I found it in this location: /u0/oracle/prodappl/ar/11.5.0/forms/US/
So I then tried to compile again using the following command, but the problem is still occurred:
export LD_LIBRARY_PATH=/u0/oracle/prodora/8.0.6/lib
export forms_path=/u0/oracle/prodappl/ar/11.5.0/forms/US/
f60gen module=/u0/oracle/prodappl/ar/11.5.0/forms/US/TESTFORM.fmb USERID=apps/passwordMy question is how to successfully compile this form?
Any input would be helpful. Thank you

Jimmy;
Are you using a WebLogic server?
If yes, you should use the Forms Compiler frmcmp.sh
#!/bin/sh
for file in *.fmb
do
frmcmp_batch.sh module=$file userid=<your connect string> compile_all=yes
done
Tested on WebLogic and working, your paths will be different
#!/bin/sh
export ORACLE_HOME=/u01/app/oracle/product/fmw/oracle_pfrd
export FORMS_PATH=/u01/app/oracle/product/fmw/fr_inst
export PATH=$PATH:$ORACLE_HOME/bin:$FORMS_PATH/bin
export TERM=vt220
export ORACLE_TERM=vt220
export TNS_ADMIN=/u01/app/oracle/product/fmw/oracle_pfrd/network/admin
for file in *.fmb
do
frmcmp_batch.sh module=$file userid=scott/tigersy@dev2 compile_all=yes
done
Edited by: mseberg on Mar 2, 2011 8:57 AM
script run from directory .fmb's are in
Should also work on iAS
Thanks!!
Edited by: mseberg on Mar 8, 2011 5:22 AM

BPEL Composite compilation issues in SOA Suite 11.1.2

I imported a SOA Composite BPEL project developed on SOA Suite 11.1.1 in SOA Suite 11.1.2. When compiling the project through ant using the "ant-sca-compile.xml" generated through JDev in 11.1.1 I am getting the following exception
java.lang.NoClassDefFoundError: oracle/fabric/common/FabricException
Caused by: java.lang.ClassNotFoundException: oracle.fabric.common.FabricException
     at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
Could not find the main class: oracle.soa.scac.ValidateComposite. Program will exit.
Exception in thread "main"
Have checked all my classpaths and jar's which are found to be in order. What can be the problem?

I changed some of the paths in the build file but now I am having compilation issues. It says the classpath is not set correctly. But I have included all the jar's properly in the build.xml.
Any pointers to where I might be going wrong?
D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\build\ant-sca-compile.xml
detokeniser:
scac:
[scac] Validating composite : 'D:/CommonTechServices/INT_ARCH/Construction/src/soa/CommonServices/NotificationServiceBpel/composite.xml'
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:14: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:15: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:16: package com.collaxa.cube.engine.core.map does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:21: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:100: package com.collaxa.cube.engine.core.ICubeProcess does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:107: package com.collaxa.cube.engine.core.ICubeProcess does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:148: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:148: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:148: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:390: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:390: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:401: package com.collaxa.cube.engine.core.map does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:401: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:401: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:841: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:841: package com.collaxa.cube.util does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:841: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:841: package com.collaxa.cube.util does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:857: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:872: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:872: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:872: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:872: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:900: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:900: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:930: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:941: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:941: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:990: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1044: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1044: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1089: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1089: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1105: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1122: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1122: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1122: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1300: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1348: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1348: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1348: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1348: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1404: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1404: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1449: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1449: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1465: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1509: package com.collaxa.cube.engine.types.bpel does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1526: package com.collaxa.cube.engine.types.bpel does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1553: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1607: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1607: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1652: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1652: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1668: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1685: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1685: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1685: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1780: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1797: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1797: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1797: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1964: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1981: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1981: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1981: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2154: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2208: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2208: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2253: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2253: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2269: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2286: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2286: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2286: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2381: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2398: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2398: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2398: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2565: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2582: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2582: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2582: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2755: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2803: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2803: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2803: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2803: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2859: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2859: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2904: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2904: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2920: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2964: package com.collaxa.cube.engine.types.bpel does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2981: package com.collaxa.cube.engine.types.bpel does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:3008: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:3062: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:3062: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:3062: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:3062: package com.collaxa.cube.engine.core does not exist
[scac] Note: D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\
orabpel\notificationservicebpel\BPEL_BIN.java uses unchecked or unsafe operations.
[scac] Note: Recompile with -Xlint:unchecked for details.
[scac] FATAL_ERROR: location {ns:composite/ns:component[@name='NotificationServiceBpel']}(30,45): Failed to compile bpel generated classes.
[scac] failure to compile the generated BPEL classes for BPEL process "NotificationServiceBpel" of composite "default/NotificationServiceBpel!1.0
[scac] The class path setting is incorrect.
[scac] Ensure that the class path is set correctly. If this happens on the server side, verify that the custom classes or jars which this BPEL pr
ocess is depending on are deployed correctly. Also verify that the run time is using the same release/version.
[scac]
BUILD FAILED

Flash Builder 4.7 frequent compiler issues/restarts

Basically Flash Builder 4.7 on Mac OSX 10.7.5 is unusable. Very frustrating. Constant compiler issues that require frequent cleaning, closing of projects, restarts of FB, and even re-installs. I've seen none of these issues on FB 4.6 with the same projects/code.
The most common visible compiler errors are these two that randomly appear:
1) An internal build error has occurred
2) classes must not be nested
I tried increasing memory as some have suggested, but this has no effect.
It takes me 100 times longer to code now becuase every tiny code change cuases these errors. Crazy!
Before I revert back to FB 4.6, any suggestions?
Thanks,
Don

Hi!
Close any unneeded projects in workspace.
You can also split your large project to few libraries compiled into SWC. After compiling libraries, if not need to change often, close their projects. When such projects are closed main project compiling with just use of SWC libraries usually takes much less resources.

"Occasionally" successful compilation issue on sun4v machine.

Similar Messages

Maybe you are looking for