JSP compilation issue

Hello,
When we use the exploded war format we are getting some issues in JSP precompilation.
The issue comes only when we do some local changes to the JSPs in the domain directly and refresh the webpage without restarting the server.
A sample error is given below.
Compilation of JSP File '/en/abc/xyz.jsp' failed:
xyz.jsp:19:5: The page failed validation from validator: "Illegal scope attribute without var in "c:set" tag.".
<c:set var="targetContentEnabled" value="${tmpTargetContentEnabled}" scope="session" />
^-------------------------------------------------------------------------------------^
xyz.jsp:27:1: The page failed validation from validator: "Illegal scope attribute without var in "c:set" tag.".
<c:set target="${sessionScope.WDSContext}" property="site" value="${requestScope.SITENAME}" scope="session"/>
^-----------------------------------------------------------------------------------------------------------^
xyz.jsp:28:1: The page failed validation from validator: "Illegal scope attribute without var in "c:set" tag.".
<c:set target="${sessionScope.WDSContext}" property="market" value="${requestScope.MARKET}" scope="session"/>
Can any one shed some light in to the issue ?
You help is greatly appreciated.
Thanks.

Hello,
Here is the error details.
<Jun 8, 2012 12:32:30 PM GMT> <Info> <HTTP> <BEA-101344> <frontendapp: Attempting to precompile /en/Admin/localization/includes/actions/ajax/SM.jsp,
since the class file associated with it was not found in the webapp classpath.>
<Jun 8, 2012 12:32:40 PM GMT> <Warning> <HTTP> <BEA-101212> <frontendapp:online Failure while Precompiling JSPs: weblogic.servlet.jsp.CompilationException:
BKGD.jsp:12:18: The page failed validation from validator: "Illegal scope attribute without var in "c:set" tag.".
<%@ include file="Panels/MiniRuleLink.jsi" %>
^-----------------------^
BKGD.jsp:12:18: The page failed validation from validator: "Illegal scope attribute without var in "c:set" tag.".
<%@ include file="Panels/MiniRuleLink.jsi" %>
^-----------------------^
BKGD.jsp:12:18: The page failed validation from validator: "Illegal scope attribute without var in "c:set" tag.".
<%@ include file="Panels/MiniRuleLink.jsi" %>
^-----------------------^
BKGD.jsp:12:18: The page failed validation from validator: "Illegal scope attribute without var in "c:set" tag.".
<%@ include file="Panels/MiniRuleLink.jsi" %>
Edited by: 939426 on Jun 12, 2012 5:17 AM

Similar Messages

  • JSP compiler issue

    Hi,
    I have a JSP based web application that works well when deployed in Tomcat 6. I am trying to deploy it in jboss 4.2.1, everything seems to be ok but when I try to access to a JSP page I have the following error
    java.lang.IllegalStateException: No Java compiler available
         org.apache.jasper.JspCompilationContext.createCompiler(JspCompilationContext.java:229)
         org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:561)
         org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:311)
         org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
         org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    my JAVA_HOME is set to use a JDK 1.5, but it should work with a JRE as the Tomcat embedded in jboss has its own compiler. I changed the web deployer configuration to use the sun compiler instead of the default but I have the same problem despite tools.jar is in the classpath. Has someone had this problem before or could someone help me on the issue ?
    Thanks,
    Cyril

    Hi here is what JBOSS displays at startup, everything seems to be right and points to a JDK
    JBOSS_HOME: D:\java\jboss\jboss-4.2.1.GA
    JAVA: D:\java\jdk1.5.0_12\bin\java
    JAVA_OPTS: -Djava.library.path="D:\java\jboss\jboss-4.2.1.GA\bin\native;..." -Dprogram.name=run.bat -server -Xms256m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
    CLASSPATH: D:\java\jdk1.5.0_12\lib\tools.jar;D:\java\jboss\jboss-4.2.1.GA\bin\run.jar
    To use sun compiler instead of jdt in tomcat I modified web.xml in JBOSS_HOME\server\default\deploy\jboss-web.deployer\conf and added the following to the jsp servlet configuration
    <init-param>
    <param-name>compilerClassName</param-name>
    <param-value>com.sun.tools.javac.main.Main</param-value>
    </init-param>
    <init-param>
    <param-name>compilerTargetVM</param-name>
    <param-value>1.5</param-value>
    </init-param>
    <init-param>
    <param-name>compilerSourceVM</param-name>
    <param-value>1.5</param-value>
    </init-param>
    but I have the same error as when I use the jdt compiler. I'm clueless on what else I could try from here, I posted also the issue on jboss forums last week but haven't got an answer so far, I suspect a classloader side effect with my application as I get the same error accessing the jboss web-console only when my application is deployed.

  • 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?

  • JSP Compilation Issue with Tomcat 4.0.6

    Hi There,
    I've been checking the following issue online for sometime but I just can't seem to figure what is wrong with the server setup. I've this very simple JSP page processing the form variables submitted to an action page which is another JSP page. Thecode segement in the target JSP is like this;
    if(request.getParameter("contactUsSubmit")!=null)
    }Whenever I try to use request.getParameter("XYZ") in the target page just like above, I get following error from Tomcat;
    Apache Tomcat/4.0.6 - HTTP Status 500 - Internal Server Error
    type Exception report
    message Internal Server Error
    description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request.
    exception
    javax.servlet.ServletException: org/apache/jasper/runtime/JspException
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:481)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:98)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:176)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:172)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:458)
         at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551)
         at java.lang.Thread.run(Thread.java:534)
    root cause
    java.lang.NoClassDefFoundError: org/apache/jasper/runtime/JspException
         at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:463)
         at org.apache.jsp.contact$jsp._jspService(contact$jsp.java:174)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:98)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:176)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:172)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:458)
         at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551)
         at java.lang.Thread.run(Thread.java:534)
    When I comment the code fragment, it works. It is not about what is in the if statment is true, I can assure you. Consider it as simple output to ease your mind.
    Any ideas why this might be happening? I'vve tried the same code with Resin 2.x and Tomcat 5.5 , it works just fine. Do you think there is something missed with the Tomcat setup or the Tomcat version (4.0.6) on that specific server is no good?
    Any comments are greatly appreciated.
    Thanks in advance...
    Regards,
    Mert

    Hi There,
    As you said using equals would not work as it should be a valid String in order for the eqauls function to work.
    Unfortuantely I can't access the Servlet created or the log files. It has crossed my mind too but this is a setup by the service provider and they don't let you nose into their business but they ahvedone something wrong with their system as far I can think.
    I've wanted to print the output to the web but when i use the request.getParameter it just creates the error.
    Java service is provided optional and as any optional service it is not well supported so I need to make them some pointers. So any more ideas?
    Cheers,
    Mert

  • Custom taglib and inexplicable jsp compilation issue

    Can someone explain what could possibly be happening here? I have been working on this for two days to no avail.
    With the following configuration, my jsp behaves as I expect it to on Tomcat, but fails to compile both for Jetty and the Maven2 jspc plugin
    deepfij.tld
    <taglib version="2.0" xmlns="http://java.sun.com/xml/ns/j2ee [3]" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee web-jsptaglibrary_2_0.xsd">
    <tlib-version>1.0</tlib-version>
    <short-name>deepfij</short-name>
    <uri>com.fijimf.deepfij</uri>
    <tag>
    <name>menuItem</name>
    <tag-class>com.fijimf.deepfij.web.tag.MenuItemTag</tag-class>
    <body-content>scriptless</body-content>
    <attribute>
    <name>item</name>
    <required>false</required>
    <rtexprvalue>true</rtexprvalue>
    </attribute>
    </tag>
    </taglib>
    menubar.jsp
    <%@ taglib prefix="df" uri="/WEB-INF/tlds/deepfij.tld"%>
    <c:forEach var="page" items="${menuRootPages}">
    <df:menuItem item="${page}" />  
    </c:forEach>
    MenuItemTag.java
    package com.fijimf.deepfij.web.tag;
    .With the error: com.fijimf.deepfij.web.tag cannot be resolved to a type.
    BUT*, if I move MenuItemTag into the package com.fijimf.web, and correspondingly change the .tld, everything works as expected.
    Is this a bug, or is there a constraint in taglib packages I don't know about?
    Any guidance would be great, because I'd like to put classes where I want them.

    This is most likely a bug on the server. The JSP formatted Tag Files usually have a .tag extension on them ( [see tutorial|http://java.sun.com/javaee/5/docs/tutorial/doc/bnama.html] ). The server is probably looking at yyy.xxx.tag and trying to use it as if it was a Tag File named xxx.tag, rather than a package.

  • "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.    

  • JSP complilation issue (JAVAC message file is broken)

    i am facing a jsp compilation issue with error message JAVAC message file is broken .
    i have one main jsp in which i have one module of about 4000 line of coding.i splitted this file in 4 segments and included them in main jsp. Each segment is included using
    <jsp:include page="Module_ProductsTab_PAOChangeValid_Apply.jsp" flush="true">
    <jsp:param name="adspot" value="dotcom3" />
    <jsp:param name="page" value="ProdTab" />
                             </jsp:include>
    tag , but now it takes as much long time to load that would result in page timeout.
    can anyone give me input how i handle this issue?

    This sounds like a corrupt installation.
    Try uninstalling java and re-installing it. (With 1.4.2_04 if you can)

  • 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]

  • Weblogic 9 and JSP compiler errors

    Hello everyone,
              I am having problems with my Jsps in my EAR file deployed on WL 9.0.
              I have a Jsp called upms.jsp that contains the following code snippets:
              After my import statements, I have some code that creates a resource bundle that accesses a properties file:
               <%!
                   ResourceBundle bundle = null;
                   public void jspInit() {
                   bundle = ResourceBundle.getBundle("conf.properties");
              %>
              I get an error from the above code:
              upms.jsp:3:11: 'try' statement has neither 'catch' nor 'finally' clause
                        import="java.util.ResourceBundle"
              ^----------------------^
              I am totally clueless as to what that error means.
              Next I declare a bean I use in the jsp:          
                   <jsp:useBean
                        id="userPrefsManagerBean"
              class="controllers.beans.UserPreferencesManagerBean"
                   scope="session">
                   </jsp:useBean>
                   <jsp:setProperty name="userPrefsManagerBean" property="*" />
              I get these errors from the above portion:
              upms.jsp:27:3: The qualifier of this name is a package, which cannot contain fields.
                   <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: The qualifier of this name is a package, which cannot contain fields.
                   <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: Expression expected (found '.' instead)
                   <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: Syntax error: expected ) (found 'class' instead)
                   <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: Syntax error: expected <identifier> (found ')' instead)
                   <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              Has anyone encountered these before?
              This jsp worked perfectly well when I deployed my EAR file on JBoss...no such luck using Weblogic.
              Is there something I am missing here? I appreciate any help.
              Cheers, :-)
              M.

    Mildred,
              Two suggestions:
              1) use option weblogic.jspc's "-keepgenerated", you can keep the generated
              servlet's source code.
              Please paste it here.
              2) Can you create a simple reproducer(e.g. a war), and put it here, so that
              we can debug it and give more clues.
              To reproduce your issue, I write a simple a simple
              UserPreferencesManagerBean classs below :
              package controllers.beans;
              public class UserPreferencesManagerBean {
              private int p1;
              public void setP1(int p)
              p1 = p;
              public int getP1()
              return p1;
              But it works(oh, I run it under 910MP1).
              We cannot tell too much without your further information
              Thanks
              Leon
              <Mildred A> wrote in message news:[email protected]...
              I am still fighting with this issue.. Dang!
              I don't know what to change in my JSP because the WL JSP compiler errors are
              so out there..
              Here is the first portion of the JSP file:
              <%@ page language="java" contentType="text/html; charset=ISO-8859-1"
              session="true"
              pageEncoding="ISO-8859-1"
              import="java.util.ArrayList"
              import="java.util.HashSet"
              import="java.util.Date"
              import="java.util.Collections"
              import="java.util.ResourceBundle"
              %>
              <%!
              ResourceBundle bundle = null;
              public void jspInit() {
              bundle = ResourceBundle.getBundle("conf.properties");
              %>
              <jsp:useBean
              id="userPrefsManagerBean"
              class="controllers.beans.UserPreferencesManagerBean"
              scope="session">
              </jsp:useBean>
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              Below is the error I get from this section alone (after precompiling):
              upms.jsp:3:11: 'try' statement has neither 'catch' nor 'finally' clause
              import="java.util.ArrayList"
              ^-----------------^
              upms.jsp:27:3: The qualifier of this name is a package, which cannot contain
              fields.
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: The qualifier of this name is a package, which cannot contain
              fields.
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: Expression expected (found '.' instead)
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: Syntax error: expected ) (found 'class' instead)
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: Syntax error: expected <identifier> (found ')' instead)
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: Expression expected (found 'catch' instead)
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: Illegal use of an expression as a statement.
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: No variable or field with this name could be found at this
              location.
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: No variable or field with this name could be found at this
              location.
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: Syntax error: expected ) (found '__ee' instead)
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: Illegal use of an expression as a statement.
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: Syntax error: expected ; (found ')' instead)
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: No variable or field with this name could be found at this
              location.
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: No variable or field with this name could be found at this
              location.
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              upms.jsp:27:3: Syntax error: expected } (found 'EOF' instead)
              <jsp:setProperty name="userPrefsManagerBean" property="*" />
              ^-------------^
              Can anyone see what I am doing wrong here? ?:| ?:|
              Cheers,
              M

  • Nitro 1.1 JSP compilation bug

    empty

    I am starting to see a pattern here of problems. One issue might be that we
    are using Resin as a container. Im not sure if that is contibuting to some
    compile issues but it might. For example, nitro complains about this
    scriptlet
    <%
    this.getServletContext().log("Bad Hashcode for RegulatoryApplication");
    %>
    Changing the "this" to "seesion" fixes it. Since this works in resin, I
    assume resin, I assume it is an container issue.
    Nitro's jsp complier seems to really not like stuff like this:
    <% if (noUser.booleanValue()) { %>
    href="javascript:window.alert('You must be a member of DrillingInfo to
    access the download functions.')">Download this data</a>
    <% } else { %>
    href="/download.do?type=prod&format=<%=com.drillinginfo.struts.actions.downl
    oad.ProductionDownloadController.DOWNLOAD_FORMAT_DRI %>"
    target="_blank">Download this data</a>
    <% } %>
    Giving an error "syntax error on else: finally expected"
    Is there some way to turn off jsp complile entirely or on a file by file
    bases?
    "Alan Berezin" <[email protected]> wrote in message
    news:[email protected]...
    Installed Nitro1.1 along with it's eclipse3.0.I am seeing an error reported in a scriptlet. Here is a clip of the JSP:
    table bgcolor="eeeeee" width="650"
    % int[] npvp =
    (int[])calcAnalysisDO.getNetPresentValuePercentsIntegers();
    logic:iterate name="calcAnalysisDO" property="netPresentValues"
    id="value"
    indexId="index"
    tr
    td><font face="Arial, Helvetica, sans-serif"
    size="2"><b><%=npvp[index.intValue()]%>%</b
    $<bean:write name="value" format="###,###"/></font></td
    /tr
    /logic:iterate
    /table
    It is reporting an error on this line: <% int[] npvp ...
    The error is "Type Mismatch: cannot convert from null to int"
    Interestly, when I move that statement to the top of the file, into a
    scriptlet with some other code, the error disappears. That will work fine
    at runtime.
    This jsp scriptlet causes the same error: <%=
    leaseData.getWells().toString() %
    I change it to this but still get the same error (getWells() returns a
    String): <% out.print(leaseData.getWells()); %
    Note that Nitro knows this object, leaseData, because it properly does
    statement completion on it.

  • JSP Deployment Issues

    Guys:
              I saw your names posted in the weblogic jsp news group. I thought you
              might be able to help me with a jsp deployment problem. A number of our
              jsps take a long time to compile. As a result, the first user who
              accesses our jsps after deployment pays a significant latency penalty.
              To get around this problem, we manually "touch" each jsp as part of
              deployment. That way when users access the site, they get reasonalble
              response time.
              The problem we face is that we are now in a clustered environment in
              production and staging. As a result, it can take a long time to
              manually "touch" each jsp. There is also a secondary issue. Our
              staging and production environments are hosted by an extenal service
              provider. We are uncomfortable with deploying source code -- e.g., jsps
              -- in these environments.
              Here is what I have done to date:
              I have written a unix script that invokes the weblogic.jspc compiler for
              each jsp. The intent is to pre-compile the JSPs ahead of time. In our
              testing this script we still notice that Weblogic (e.g., 4.5.1) still
              attempts to recompile the jsps on-demand when they are first accessed
              from the browser by the first user after jsp deployment. (This defeats
              the purpose of pre-compiling the jsps.)
              What are we doing wrong and what can we do so that the jsp-s are
              pre-compiled and not re-compiled on demand. Again, at a minimum we want
              to avoid the latency problems associated with the first user. Best case
              scenario, we would like to ship a jar file that contains the compiled
              jsp servlet classes.
              Your recommendations are most appreciated.
              Mark C. Berman
              Javelin Solutions
              [email protected]
              

    I've never tried this, but I don't see any reason why it wouldn't
              work... Don't even register the JSPServlet. Build the JSPs (servlets)
              and deploy them like any other servlet. You can register them with a
              .jsp extension or you could give them a different alias altogether.
              The WL JSP compiler (weblogic.jspc) may be used to compile the jsps
              into servlets during the normal build process and there are options
              that may be used to modify the package, install dir, etc.
              Hope that helps.
              Jason
              On Tue, 26 Dec 2000 17:09:25 -0600, mark berman
              <[email protected]> wrote:
              >Guys:
              >
              >I saw your names posted in the weblogic jsp news group. I thought you
              >might be able to help me with a jsp deployment problem. A number of our
              >jsps take a long time to compile. As a result, the first user who
              >accesses our jsps after deployment pays a significant latency penalty.
              >To get around this problem, we manually "touch" each jsp as part of
              >deployment. That way when users access the site, they get reasonalble
              >response time.
              >
              >The problem we face is that we are now in a clustered environment in
              >production and staging. As a result, it can take a long time to
              >manually "touch" each jsp. There is also a secondary issue. Our
              >staging and production environments are hosted by an extenal service
              >provider. We are uncomfortable with deploying source code -- e.g., jsps
              >-- in these environments.
              >
              >Here is what I have done to date:
              >
              >I have written a unix script that invokes the weblogic.jspc compiler for
              >each jsp. The intent is to pre-compile the JSPs ahead of time. In our
              >testing this script we still notice that Weblogic (e.g., 4.5.1) still
              >attempts to recompile the jsps on-demand when they are first accessed
              >from the browser by the first user after jsp deployment. (This defeats
              >the purpose of pre-compiling the jsps.)
              >
              >What are we doing wrong and what can we do so that the jsp-s are
              >pre-compiled and not re-compiled on demand. Again, at a minimum we want
              >to avoid the latency problems associated with the first user. Best case
              >scenario, we would like to ship a jar file that contains the compiled
              >jsp servlet classes.
              >
              >Your recommendations are most appreciated.
              >
              >Mark C. Berman
              >Javelin Solutions
              >[email protected]
              >
              

  • Automatic JSP compilation

    All,
    I am working with R12-iStore. As per metalink link note: 458338.1, I have enabled automatic JSP compilation. Bounced all services.
    After logging into iStore then when I click on Profile link, blank page displayed.
    ibeCAcpProfMenuHome.jsp -> This is the JSP file which is used for Profile page. This page exists in $OA_HTML & class file in $COMMON_TOP/_pages directory.
    The above profile jsp page contains the following JSPs. These files are there in $OA_HTML directory but the classe files are not there in $COMMON_TOP/_pages directory.
    1) ibeCZzpHeader.jsp
    2) jtfincl.jsp
    My question is , do I need to compile them to fix this issue even though auto JSP compilation option is enabled ?
    is this auto compilation doesn't compile the pages while loading or accessing ??
    Thanks,

    Hi Hussein,
    I have checked the log file. It looks like , the bounce was proper.
    Also, I have raised SR with ORacle Support.. lets hope we get some good solution.
    ================================================================================
    04/03/09-16:10:34 :: adapcctl.sh version 120.6.12000000.4
    04/03/09-16:10:34 :: adapcctl.sh: stopping OPMN managed OHS instance
    opmnctl: stopping opmn managed processes...
    04/03/09-16:10:36 :: adapcctl.sh: exiting with status 0
    ================================================================================
    04/03/09-16:10:48 :: adapcctl.sh version 120.6.12000000.4
    04/03/09-16:10:48 :: adapcctl.sh: starting OPMN if it is not running
    opmnctl: opmn is already running.
    04/03/09-16:10:48 :: adapcctl.sh: starting OPMN managed OHS instance
    opmnctl: starting opmn managed processes...
    04/03/09-16:10:51 :: adapcctl.sh: exiting with status 0
    ================================================================================

  • JSP compilation error, IOException, can not output (Urgent)

              Hi,
              I met the error that Weblogic can compile the jsp to a temporary java file but can
              not compile the temporary java file to class file, it said java.io.IOException, anybody
              can tell why?
              Thanks a millon!
              

              Your system does not have enough swap space to run the JSP compiler.
              Add swap space.
              Mike
              "dai shui" <[email protected]> wrote:
              >
              >Hi,
              >I met the error that Weblogic can compile the jsp to a
              >temporary java file but can
              >not compile the temporary java file to class file, it
              >said java.io.IOException, anybody
              >can tell why?
              >
              >Thanks a millon!
              

  • JSP compiler reading the web.xml file?

    Hi,
              I am trying to use the weblogic JSP compiler (weblogic.jspc) to
              pre-compile some JSP that use custom tags. Does the compiler
              read the web.xml file if there is one? In particular the taglib
              elements in that file so that the compiler understands the
              <%@ taglib ... %> directive.
              In the JSP I try to compile I use this statement to declare a taglib:
              <%@ taglib uri="xyz/xyz-taglib" prefix="xyz" %>
              and in my web.xml I have:
              <taglib>
              <taglib-uri>xyz/xyz-taglib</taglib-uri>
              <taglib-location>/WEB-INF/tlds/xyz.tld</taglib-location>
              </taglib>
              When I try to compile the JSP I get the following error:
              Could not parse embedded JSP code: weblogic.utils.ParsingException: nested
              IOException: java.io.IOException: cannot resolve 'xyz/xyz-taglib' into a
              valid tag library.
              Any ideas how I can resolve this?
              In advance thank you for any help.
              Florian
              

    open it in a text editor and modify it.
    %

  • 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

Maybe you are looking for

  • Code could not be generated because an external component or driver is missing

    Greetings All,      I've using Labview for a little over a year and I have an interesting situation with regards to Labview that I came across today.  When I left off yesterday (01/11/12) my TestStand sequence was compiling fine.  Today for some reas

  • VC Error: There are no BI systems defined in portal/ no authorization

    Hi, when trying to launch the BI integration wizard on an iview in Visual Composer in the ESA Discovery system I get the follwing error message: "WARNING 2005: There are no BI systems defined in portal. In order to use BI integration wizard, you must

  • Excise invoice date and delivery date difference..

    Hi all, 1. Excise invoice is generated in the month of July for the delivery happened in June. Is there any implications? When i do registry update and Utilisation, does it have an effect? 2. Pending Excise are yet to be created for the month of June

  • Access Violation when trying to read from Open Hub in BW

    Hi, Can someone help me out. I use BODS version 14.1.1.210. I have setup the connection to BW source and imported metadata for my OpenHub - no problem. Then created DTP and processchain to load Open hub data in BW. Made dataflow in BODS with Open Hub

  • Passing Select-option to Function Module

    Hi ,      I want to pass a select-option directly to the function Module tables parameter . Can anyone highlight on how i can declare the table in Function module side . Thanks & Regards, Raj