Error when Building Simple Project

Hello Community!
I am developing a new project in the NWDS / NWDI by [this tutorial.[http://help.sap.com/saphelp_nw70/helpdata/en/44/0d18d725301a78e10000000a1553f6/frameset.htm].
When I am in the Java Perspective and in the Java DC Explorer and want to build my DC (Right Click -> Development Component -> Build...), II always get this error prompt:
- I have tried out many different versions of the JDK, but nothing works.
- I have also done [this step|http://www.drftpd.org/forums/viewtopic.php?f=5&t=2978]
Can you help me?
10.10.2011 11:31:22 /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: test/tax/calc: Build failed for vwg.audi.in/test/tax/calc(vwg.audi.in_APPLICATION_1) in variant "default": The Build terminated with errors
------------------------------------- Build log ------------------------------------------------------
Development Component Build (2011-10-10 11:31:22)
Component name: test/tax/calc
Component vendor: vwg.audi.in
SC compartment: vwg.audi.in_APPLICATION_1
Configuration: AZB_APPLFIN_D
Location: AZB_APPLFIN_D
Source code location: http://isazbdbz:54400/dtr/ws/APPLFIN/vwg.audi.in_APPLICATION/dev/inactive/DCs/vwg.audi.in/test/tax/calc/_comp/
DC root folder: C:\Dokumente und Einstellungen\UO94F87\.dtc\0\DCs\vwg.audi.in\test\tax\calc\_comp\
DC type: Java
Host: audiinc07394527
DC Model check:
   All used DCs are available locally
   validating dependency to build plugin "sap.com/tc/bi/bp/javaLib"
   DC model check OK
Start build plugin:
   using build plugin: sap.com/tc/bi/bp/javaLib
   starting build plugin from : C:\Dokumente und Einstellungen\UO94F87\.dtc\0\DCs\sap.com\tc\bi\bp\javaLib\_comp\gen\default\public\saplib\
Build Plugin 'JavaPlugin', Version 7.00 SP 15 (645_VAL_REL, built on 2008-02-16 00:52:15 CET, CL79160)
   development component: test/tax/calc (vwg.audi.in)
      software component: APPLICATION (vwg.audi.in)
                location: AZB_APPLFIN_D
                    type: Java
           build variant: default
         output location: C:\Dokumente und Einstellungen\UO94F87\.dtc\0\DCs\vwg.audi.in\test\tax\calc\_comp\gen\default
       generation folder: C:\Dokumente und Einstellungen\UO94F87\.dtc\0\t\38AAC310BC92CAB879CB0B2FFFDE0EF0
       plugin start time: 2011-10-10 11:31:22 GMT+01:00 (CEST)
                 Java VM: Java HotSpot(TM) Client VM, 10.0-b22 (Sun Microsystems Inc.)
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Checking path lengths for sources
Path length checks finished in 0 seconds
Preparing data context..
No 'default' JDK defined, will use running VM.
Warning: Did not find any tools.jar in C:\Programme\Java\jre1.6.0_06
Data context preparation finished in 0.031 seconds
Creating Ant build file..
Creating output file: C:\Dokumente und Einstellungen\UO94F87\.dtc\0\DCs\vwg.audi.in\test\tax\calc\_comp\gen\default\logs\build.xml
Using macro file:     C:\Dokumente und Einstellungen\UO94F87\.dtc\0\DCs\sap.com\tc\bi\bp\javaLib\_comp\gen\default\public\saplib\macros\build.vm
Build file creation finished in 0.078 seconds
Starting Ant..
Using build file:     C:\Dokumente und Einstellungen\UO94F87\.dtc\0\DCs\vwg.audi.in\test\tax\calc\_comp\gen\default\logs\build.xml
Using build target:   build
Using Ant version:    1.6.2
compile:
      [echo] Starting Java compiler
      [echo] Settings:
      [echo]         debug: on
      [echo]      optimize: off
      [echo]   deprecation: default
      [echo]       verbose: default
      [echo]      encoding: UTF8
      [echo]        source: default
      [echo]        target: default
      [echo]   source path: C:\Dokumente und Einstellungen\UO94F87\.dtc\0\DCs\vwg.audi.in\test\tax\calc\_comp\src\packages
      [echo]    class path: none
      [echo]    output dir: C:\Dokumente und Einstellungen\UO94F87\.dtc\0\t\38AAC310BC92CAB879CB0B2FFFDE0EF0\classes
     [javac] Compiling 3 source files to C:\Dokumente und Einstellungen\UO94F87\.dtc\0\t\38AAC310BC92CAB879CB0B2FFFDE0EF0\classes
Error: C:\Dokumente und Einstellungen\UO94F87\.dtc\0\DCs\vwg.audi.in\test\tax\calc\_comp\gen\default\logs\build.xml:74: Unable to find a javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK
     at org.apache.tools.ant.taskdefs.compilers.CompilerAdapterFactory.getCompiler(CompilerAdapterFactory.java:105)
     at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:929)
     at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:758)
     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
     at org.apache.tools.ant.Task.perform(Task.java:364)
     at org.apache.tools.ant.Target.execute(Target.java:341)
     at org.apache.tools.ant.Target.performTasks(Target.java:369)
     at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
     at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:116)
     at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:58)
     at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:196)
     at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:168)
     at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
     at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
     at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:99)
     at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:73)
     at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)
     at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1750)
     at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:6004)
     at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.buildDCsForDevConfig(BuildAction.java:307)
     at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.access$200(BuildAction.java:58)
     at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction$1.run(BuildAction.java:212)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Ant runtime 0.172 seconds
Ant build finished with ERRORS
Unable to find a javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK
Error: Build stopped due to an error: Unable to find a javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK
Build plugin finished at 2011-10-10 11:31:22 GMT+01:00 (CEST)
Total build plugin runtime: 0.485 seconds
Build finished with ERROR

@ John Wu!
You are right!
I have solved my problem.
Thank yoo for your helpful answer.
I use NWDI 7.01 SP7 and JDK 1.5 / 5.
So I replaced only:
C:\Programme\SAP\IDE\IDE70\eclipse\SapIde.exe -vm "C:\Programme\Java\JDK1.5\jdk\bin\javaw.exe"
And now it works fine

Similar Messages

Error when building Azure project

A few days ago I started to see an error when compiling my Azure Project (cloud service with web and worker roles). I've been working with this Azure project for almost 3 years without seeing this before. When I attempt to build my Azure Project, 9 times
out of 10 it fails with this error:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Windows Azure Tools\2.2\Microsoft.WindowsAzure.targets(1371,5): error : Could not find file '<SourceCode>\SomeProject\bin\Debug\ServiceDefinition.csdef'.
Here's another when I attempt to build again:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Windows Azure Tools\2.2\Microsoft.WindowsAzure.targets(985,5): error : Could not find a part of the path 'C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\csx\Debug\ServiceDefinition.csdef'.
Sometimes the error refers to ServiceDefinition, sometimes to ServiceConfiguration. The problem is that it is looking for the two files in places where it's not supposed to be. I have a single Azure Project in my solution, and a single service definition
in my solution, but when building the error message says it can't find the service definition/config in some other Project in the solution. For example, it may try to find the service definition in some unit testing C# Project instead of in the Azure Project.
Some isolation:
Building same source code works fine for my colleauges.
I've set up a new computer with Windows 8, VS2013, VS2013 Update 1, Azure SDK 2.2. Still same error.
I've turned off multi-core builds. Still same error.
I've seen another post on SO with a similar issue, but then it was related to publish settings files in his solution which were missing.

Hi,
Did your colleague build the same solution or create a new solution with the existing code? If they have exactly the same solution as you have, then please check if the environment of your machine (both old and new) is different from theirs. For instance,
please check Azure version, VS extension, etc. If they created a new solution with the existing code, you can try to do that yourself to see whether it works.
Best Regards,
Ming Xu
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error when Building DC Project for CAF Entity Service

Hi All,
I got the following error message when Im building my CAF DC Project for Entity Services:
01.02.2008 12:09:10 /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: ewrdata/metadata: Failed to read component definition from local file MyComponents:com.cas.elisa.gp/ewrdata/metadata : Cannot read component definition. File does not exist: C:\Documents and Settings\tfelp4\.dtc\LocalDevelopment\DCs\com.cas.elisa.gp\ewrdata\metadata\_comp\.dcdef (Cannot read component definition. File does not exist: C:\Documents and Settings\tfelp4\.dtc\LocalDevelopment\DCs\com.cas.elisa.gp\ewrdata\metadata\_comp\.dcdef)
But ".dcdef" file exists, its an XML file.
My NWDS environment is 7.0.13.
I used the tutorial exactly how it was written in the tutorial from SAP:
http://help.sap.com/saphelp_nw04s/helpdata/en/05/3a0741b5b7ee6fe10000000a1550b0/frameset.htm
What could be the problem?
Thanks for helping me...
Steve

Hi Chandan,
Can you do person.getRelatedModelObjects() and get the contact object, to check whether it is null, also check in the CAF DB whether the data you entered is present.
I am not sure the code is actually adding the contact model object to person.
Go thru this SDN Blog on usage of the CMI API's, there is a link for CMI documentation in it which might help you get the right code for adding the contact object.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cef4f43e-0d01-0010-db84-ede25c874115.
award points if info is helpful
Regards,
Anish

Error when building PDA project 'Unsupported control - Knob, 680'

Hi,
I'm developing an application for my PDA (8.2 LabVIEW version) which was in the past running in my laptop with the 7.1 version of LabVIEW. I'm working step by step and as soon as I inserted an own subVI an error occur. This own subVI containes also other own subVI but everything was working perfectly on my laptop. So I just provide you a picture of the error window, hoping somebody already encounters this kind of message.
Thanks
Attachments:
LabVIEW PDA error.jpg ‏541 KB

LabVIEW PDA do not allow using the same variety of functions and controls as the PC versions. You should rework your "faulty" vis by replacing the original controls with the available PDA controls (and functions). When developing for a PDA, avoid as much as possible prototyping on a LV PC version... Good luck !
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...

Which files should include in path when building J2EE project?

Hi,
I'm new to J2EE. Trying some examples on Servlet. But I've the error messages stating that it can't locate the javax.servlet.* classes like the ones below:
<code>
import javax.servlet.http.HttpServlet;
import java.io.IOException;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
</code>
Could anybody pls tell me which file (of J2EE SDK) I should include in my path when building J2EE projects?
thanks,
jackling

You need to have $J2EE_HOME/lib/j2ee.jar in your CLASSPATH when compiling your servlet

Error When building ess/tra/tre and ess/tra/tre/trs DC's

I had customized the ess/tra/tre and ess/tra/tre/trs DC's and had them working, but I do not know what I did or what happened that am now getting the following errors when building, can anyone help tell what the problem could be?
Error
-     The project was not built since its classpath is incomplete. Cannot find the class file for com.sap.xss.tra.model.openccmodel.OVSOpenCostcenterModel. Fix the classpath then try rebuilding this project.
-     HDI_HNS15.02_Desstratresap.com
Error
-     This compilation unit indirectly references the missing type com.sap.xss.tra.model.openccmodel.OVSOpenCostcenterModel (typically some required class file is referencing a type outside the classpath)
-      InternalVcTreReview.java
-      HDI_HNS15.02_Desstratresap.com/gen_wdp/packages/com/sap/xss/tra/tre/vc/review/wdp
-     line 0

For anyone who might need to know, I managed to fix this by adding tra to the required projects on the build path. On the Navigator View, right click -> Properties -> Java Build Path -> Projects tab -> check dependant project.

When Building a Project

When I'm building my DVD Project it sometimes gets stuck at around 42 percent. I'm thinking this my be a problem with some of the music I have put into the videos. Does anyone no of any problems DVDSP might have when building a project ?
Thank You

What does the log say when the error occurs? Is you audio AC3? Is DVDSP encoding your assests? or compressor? Try encoding your audio and video outside DVDSP and importing your encoded assets then all DVDSP will have to do is multiplex.

Icon path restricted error when building release version for ipad3

Hi,
i get the following error when building the release build ipa file for ipad 3: "The path icon.png is restricted. If you were trying to package Icon.png you should correct the case." In debug mode everything works. My icon is under assets folder and added in the app-xml with:
<icon>
<image72x72>assets/icon_72.png</image72x72>
</icon>
Did I missed something in configuration? Seems to be that the problem is known but cant find a solution for it. If i try to packegae per command line despite the fact building works I could not install the app. When I change the icon tag to use no icon everything works fine. Any ideas?
Greetz and thanks in advance!

I solved it. When you export the release build you can choose package contents to be compiled in the ipa. When I tried to add an icon at first I named it icon.png, which seems to be a reserved name. The configuration to include this icon.png was still saved though i deleted it. Wired... After unchecking the ceckbox for icon.png not to be compiled in the ipa, the release build was build.

Packed project library 1003 error when building it

Hi,
I am trying to build packed project library, but I get 1003 error. I have tried all things suggested in other threads regarding the 1003 error, but nothing helps.
My two project HardwareSpecificFunctionalities and ModuleTemplate are attached. HardwareSpecificFunctionalities PPL is used in the ModuleTemplate's VIs. When I am trying to build ModuleTemplate PPL I get 1003 error saying that one VI is broken, but actually it is not. If I remove the ReadOffset.vi from the AcquisitionInitialization_Main.vi, the ModuleTemplate PPL is build successfully.
Have anybody an idea what is wrong?
Attachments:
PPL problem.zip ‏1230 KB

Hello Andrej.
I just noticed that in document LabVIEW 2011 and 2011 SP1 Known Issues (http://www.ni.com/white-paper/13164/en#323425_by_Category) it is stated that this bug will be fixed in LV 2012 (32 bit).
This version of LV will be available in August 2012.
All workarounds that are known, are the one that are described in this link.
Kind regards,
Sofija

Why do I get 'ResolveManifestFiles task failed' error when building a WPF app that references WinRT API?

0
down vote
favorite
I am working on a WPF app that I want to create for Windows 8. I followed steps mentioned in
Hansleman's blog to make some manual modifications using WinRT functions in a WPF app. Everything worked well, until I tried to publish the app. When I clicked on publishing the app I got error "The 'ResolveManifestFiles' task failed unexpectedly.
System.ArgumentException: Value does not fall within the expected range."
Afterwards, it will produce the same error when attempting a simple solution build.
Even if you create a simple WPF project and add the references mentioned in blog to access WinRT functions and publish, this issue can be reproduced.
I think it would be common scenario to call WinRT functions from WPF and someone should have done it. Is anyone aware what should be done to fix this issue?

I am having the same problems and came across this article while researching a workaround.
It is surprising more people aren’t talking about this.
Here are the steps to reproduce the problem; Using Visual Studio Express 2012 (x64) create a new VB Windows Forms Application.
Unload the project and edit the [ProjName].vbproj in the solution explorer.
Add <TargetPlatformVersion>8.0</TargetPlatformVersion> to the <PropertyGroup>.
Save and reload the project. In Add Resource/Reference Manager add the Windows.minmd found under Windows/Core.
This WinRT/Desktop solution will run as expected. Now try to Publish this solution.
It will FAIL with the following ERROR; “The ResolveManifestFiles task failed unexpectedly, Value does not fall within the expected range.”
Attempting to build or run the solution again now will fail with the same Error.
The only way to build the project now is to remove the “Enable ClickOnce security settings” option under the project properties Security settings.
Occasionally using this trick, the solution will build but not run.
When that happens jiggle around with Debug/Release Solution Configurations and the Any CPU/x64 Solution Platforms then rebuild and try the run again.
This fussing around will get you through development however any attempt to publish with restore the ClickOnce security setting and create the previous Error.
The first question here is how do you publish a WinRT app for the desktop with VS2012 Express.
Then secondly, if that is not possible can we publish this Express solution with a 3rd party deployment tool like InstallShield Limited Edition or the WIX Toolset.
Neither however seems functional in a VS Express environment.
Then thirdly, are there ways to access hardware sensor devices from a desktop solution without resorting to the WinRT API.
Any ideas or new research directions would be greatly appreciated.

Error when deploying a project

Everytime when i want to deploy any simple project i get an error. Even if i try samples, tutorials or something else.
At deployment time I see this in the Ant log:
BUILD FAILED
C:\product\jdevstudio10134\jdev\mywork\DemoExpen\ExpenseRequest\build.xml:97: Error while deploying the form on server "localhost" Error message :
java.lang.SecurityException
at oracle.ide.IdeCore$7.checkExit(IdeCore.java:177)
at java.lang.Runtime.exit(Runtime.java:88)
at java.lang.System.exit(System.java:868)
at oracle.oc4j.admin.deploy.cmdline.Oc4jAdminCmdline.executeCommand(Oc4jAdminCmdline.java:141)
at com.collaxa.cube.ant.taskdefs.DeployForm.deployIAS(DeployForm.java:818)
at com.collaxa.cube.ant.taskdefs.DeployForm.deployForm(DeployForm.java:578)
at com.collaxa.cube.ant.taskdefs.DeployForm.deployForms(DeployForm.java:849)
at com.collaxa.cube.ant.taskdefs.DeployForm.execute(DeployForm.java:875)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at oracle.jdevimpl.ant.runner.AntLauncher.launch(AntLauncher.java:321)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at oracle.jdevimpl.ant.runner.InProcessAntStarter.runAnt(InProcessAntStarter.java:295)
at oracle.jdevimpl.ant.runner.InProcessAntStarter.mav$runAnt(InProcessAntStarter.java:43)
at oracle.jdevimpl.ant.runner.InProcessAntStarter$1.run(InProcessAntStarter.java:71)
Total time: 18 seconds
I just made new basic installation . ANd using oracle soa suite 10.1.3.4
i can use oracle BPEL console, worklist application and other web pages.
Can any1 tell me please what is wrong?

Make sure that you are deploying using the right ports. I encounter that most often when the RMI ports are wrong. You can find the RMI ports by running opmnctl status -l

[JDeveloper/BPEL] "repository.jar" is missing when building the project

Hi,
First of all let me say that I'm new to JDeveloper and BPEL. I followed the "CreditFlow" tutorial and everything was OK. I could deploy and run it. Then I wanted to create my own webservice and try to create a simple HelloWorld BPEL workflow. My problem now is that I get a "Error: C:\oracle\JDeveloper\jlib\repository.jar (The system cannot find the file specified)" error when I build my project.
I had the same error message for the following jars:
-jaxb-libs.jar
-jaxb-impl.jar
-jaxb-api.jar
I just copied them from "<jdeveloper_inst_dir>\adfp\lib" to "<jdeveloper_inst_dir>\webservices\lib" to get rid of thoses error messages.
But this "repository.jar" simply doesn't exist on my filesystem...
I think it's pretty strange...
BTW I use JDeveloper version 10.1.3.3.0.
Thanks for any help!
Nicolas

Hi,
I am getting the same error. Any help is greatly appreciated.
May be if you have repossotory.jar in your lib folder by any chance please send it to [email protected]
Thanks

I get a "vi is not executable" error when building an application.

I have an ongoing project that has worked fine in the past when building an application. I have recently added some report generation toolkit vis(Excel) and get an error for some of the ni vis and some of my own that call lower level excel vis. The error is that he vi is not executable, however they run fine in the development environment. I do not get this error if I save all vi's into one llb with save with options command and then build. However, when I try to run the app, this error re-appears. Also, do I have to add the dynamically loaded vi's that are part of the toolkit in my build script? Could this be the cause of the problem? If so, what's the best way to find all of them? Any suggestions?

You have hit in on the nail! You do need to add the dynamically loaded VIs when you are creating an executable from your VI. You need to add _wordsub.lib and _exclsub.lib as dynamically loaded VIs into your executable. Try this and let us know if you have any more problems with it.
J.R. Allen

Error when building application with Excel included

Hi All !
I've read several post on problems with Report Generation Toolkit when building applications that uses Excel or Word interactivity.
I've included both _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi in my project and added them to the dynamic vis and support files.
When building I get the error :
The VI is broken. Open the VI in LabVIEW and fix the errors.
C:\Programmer\National Instruments\LabVIEW 8.2\vi.lib\addons\_office\_exclsub.llb\_Excel Dynamic VIs.vi
When opening that VI there is no broken arrow and all the vi's included in this is not broken either.
I've tried mass compiling and so on but so far luck.
Regards Morten Kahr
Regards Kahr
Certified LabVIEW Architect
CIM A/S

If you do a search on this forum you will find this to be a common and vexing problem. I myself had this same exact problem about a year ago, and it took me the better part of a day to track it down. As you will find by reading the various threads on this problem, there seems to be no specific cause for this, and it remains a mystery, and the solutions are no better than chanting voodoo, and probably just as effective.
One thing you can try is to force a recompile of your VI hierarchy. Open you top-level VI. If it's set up to run when opened, stop it. Hold down the Control key and click the run button. This will force a recompile of the application. Sometimes this works, sometimes it doesn't. Like I said, voodoo.
Another thing to look for is to check if you are using any diagram disable structures or case structures with a constant wired, as in trying to use the case structure to comment out code.
Are you using classes and passing by reference? There was a mention of this here.

Error when building the Java pricing userexit manual code

I went throught the manual for the pricing userexit manual... it tells you to ignore the errors when you do an ant build but I want to remove all the errors since they dont let the rest the code compile.... where are the jars for these errors:
[javadoc] C:\DEV\PRC_UE_CUSTOMER\lib_src\src\com\sap\spc\document\DocumentConstants.java:16: package com.sap.vmc.logging does not exist
     [javadoc] import com.sap.vmc.logging.Category;
     [javadoc]                            ^
     [javadoc] C:\DEV\PRC_UE_CUSTOMER\lib_src\src\com\sap\spc\document\DocumentConstants.java:26: cannot resolve symbol
     [javadoc] symbol : class Category
     [javadoc] location: class com.sap.spc.document.DocumentConstants
     [javadoc]     public static final Category CATEGORY = Category.getCategory(Category.APPLICATIONS, "/AP/SPC/Document");
     [javadoc]                         ^

See the [SAP note 809820 - Userexit concept for pricing|https://service.sap.com/sap/support/notes/809820]
Use ZIP file the attached to the above note - PRC_UE_CUSTOMER_V105.zip
ZIP file contains an Eclipse .project file that has the required build path. If you read the documents carefully, it does refer this project file.
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
     <classpathentry kind="src" path="src"/>
     <classpathentry sourcepath="lib_src/src" kind="lib" path="lib_api"/>
     <classpathentry kind="lib" path="lib_vmc_api/base_services_stripped_api.jar"/>
     <classpathentry kind="output" path="bin"/>
</classpath>
Again read the documents thoroughly. They are neither fictions nor non-fictions, but technical documents written with care. So, we must also read them with care. If we don't follow them, then it is time to engage someone who does. )
BTW, coming back to the Java basics - One must have a class and source files to debug. You won't get a class file unless it is compiled. The Java file won't compile correctly if it has syntax / reference errors. Unfortunately or fortunately, all these apply to the IPC java userexit development as well.
Easwar Ram

Error when Building Simple Project

Similar Messages

Maybe you are looking for