Hello! Couldn't found header file extcode.h in LabVIEW 6i

Hello! At the monent I try to use a cluster from LabVIEW 6i to get Data from VC ++ dll. I knew that I need the header file extcode.h. I could found it at directory of LabVIEW 6i.

Hello,
I found one here "C:\Program Files\National Instruments\LabVIEW 6.1\cintools\extcode.h".
You'll find it in attachment.
Maybe you forgot to install the CIN tool when you installed LabVIEW 6.1 ?
I hope it will help you.
Attachments:
extcode.h ‏26 KB

Similar Messages

Shared library: function is not found and recognized in header file

Hello,
I am trying to use Java methods into LV. I am doing so by creating Java Invocation Interface, usind which I can call Java methods into C++ and then create a shared library that can be called into LV.
When I am importing my shared library into Labview, I am getting the following error messages:
The shared library contains 3 function(s). But no function is found and recognized in the header file. The following function(s) cannot be wrapped. If you want to import these functions, please review the warning messages next to the functions below. You will need to fix the problems before you can continue with the wizard.
jclass invokeJavaClass(JNIEnv* jenv, string className);
The following symbols are not defined:
jclass;
Undefined symbols can prevent the wizard from recognizing functions and parameters. To correct this problem, check the header file to determine if you must add preprocessor definitions. Click the Back button to return to the previous page of the wizard to add a preprocessor definitionsl (for example, "NIAPI_stdcall = __stdcall" or "NIAPIDefined = 1").
The following header file was not found in the specified header file or one of the referenced header files:
- string
- iostream
- cstring
- jni.h
To fix, click the Back button to go to the previous page and add the header file path to the Include Paths list.
Please advise.
Regards,
H
Attachments:
SharedLibError.png ‏51 KB

Hello Vivek,
The LabVIEW dll that I am trying to import does not include any third-party device..all my code is fully based on LabVIEW. Maybe this helps you to guess what is happening: once I've parsed the dll' header appears an error
like this one:
void
__cdecl Zdmt(LVBoolean *stop, double P, char channelName[],
    TD1
*errorIn, TD14 *FFTOptions, TD12 *Calibration, char FileName[],
int32_t minRecordLength, TD26 *InstrumentHandler, LVRefNum
sessionRefArray[],
    LVRefNum *queueIN, TD1 *errorOut, LVBoolean
*averagingDone,
    HWAVES LastRecordFetched, TD24 *Impedance, TD17
*ColeColeCluster,
    TD18 *FFTcluster, TD5
*InstrumentHandleOutputCluster, LVRefNum *queueOut,
    int32_t
*Acquired, TD6 *FreqTimeInfoCluster, double *averagesCompleted,
int32_t len);
The following symbols are not defined:
LVBoolean;
int32_t; LVRefNum;
Undefined symbols can prevent the wizard
from recognizing functions and parameters. To correct this problem,
check the header file to determine if you must add predefined symbols.
Click the Back button to return to the previous page of the wizard to
add a preprocessor definitionsl (for example, "NIAPI_stdcall =
__stdcall" or "NIAPIDefined = 1").
The following header file was
not found in the specified header file or one of the referenced header
files:
- extcode.h
To fix, click the Back button to go to the
previous page and add the header file path to the Include Paths list.
I have replaced the first line #include "extcode.h" of
the dll header file for #include "C:\Program Files\National
Instruments\LabVIEW 8.6\cintools\extcode.h" that is the full path where
the header file is located. However, new libraries seems to be missed:
- stdint.h
- MacTypes.h
As far as I know, Mactypes.h contains basic mac os data types and it doesn't have any relation with stdint.h...
I have created both of them and stored into the same folder as extcode.h, but then other libraries are missed!!!
Do you know if it would be possible to create the .dll generating all the header files associated for its data structures???
And if this is not factible, then what do you suggest me? because I hope to not having to create all the header files until it stops giving me an error!
thanks for four time,
ben

Problem while including the header file in C source code in CIN

While Creating code interface node....
In the C source code we are supposed to include the Header file "extcode.h".In my system i have installed
Turbo C. I couldn't able to find the above header files.When i am trying to use the above header file i am getting error,what could be the reason

Hi,
You need to point your turbo C to ..\labview\cintools which is where you will find the extcode.h and other h file and also the lib file.
Regards
Ray Farmer
Regards
Ray Farmer

Missing header files when importing a shared library with labview 8.6?

Hi all,
I want to import a .dll into my .vi program but I am not able to do it...
I have created the dll following the ni website tutorial
http://zone.ni.com/devzone/cda/tut/p/id/3303#toc2
Once the dll has been created, I have tried to import it with
Tools-Import-Shared Library(dll)
After parsing the header file appears an error like this one:
void __cdecl Zdmt(LVBoolean *stop, double P, char channelName[],
    TD1 *errorIn, TD14 *FFTOptions, TD12 *Calibration, char FileName[],
    int32_t minRecordLength, TD26 *InstrumentHandler, LVRefNum sessionRefArray[],
    LVRefNum *queueIN, TD1 *errorOut, LVBoolean *averagingDone,
    HWAVES LastRecordFetched, TD24 *Impedance, TD17 *ColeColeCluster,
    TD18 *FFTcluster, TD5 *InstrumentHandleOutputCluster, LVRefNum *queueOut,
    int32_t *Acquired, TD6 *FreqTimeInfoCluster, double *averagesCompleted,
    int32_t len);
The following symbols are not defined:
LVBoolean; int32_t; LVRefNum;
Undefined symbols can prevent the wizard from recognizing functions and parameters. To correct this problem, check the header file to determine if you must add predefined symbols. Click the Back button to return to the previous page of the wizard to add a preprocessor definitionsl (for example, "NIAPI_stdcall = __stdcall" or "NIAPIDefined = 1").
The following header file was not found in the specified header file or one of the referenced header files:
- extcode.h
To fix, click the Back button to go to the previous page and add the header file path to the Include Paths list.
I have replaced the first line #include "extcode.h" of the dll header file for #include "C:\Program Files\National Instruments\LabVIEW 8.6\cintools\extcode.h" that is the full path where the header file is located. However, new libraries seems to be missed:
- stdint.h
- MacTypes.h
Does anybody know what I have to do??
Any help will be really appreciated,
Regards,
Benjamin

If you use any of the LabVIEW cintools headers, they reference other headers too. The import wizard is written in a way that it simply skips parsing datatypes that can not be resolved due to missing header files. If your functions you want to import references such datatypes then you get an according error about any include files the wizard could not load, otherwise not. The wizard can not know which of the missing header files is the problem since it obviously doesn't know what would be in those header files.
The LabVIEW cintools headers are multiplatform, meaning they evaluate various compiler predefined defines to determine which platform they are included in. The import library wizard does not define any specific defines, since it is not really a compiler. So you have to define them. And they get adapted with each new LabVIEW version to support new compilers and compiler versions, so the defines described in the link in the first post do not have to be correct for cintools headers in newer LabVIEW versions.
All in all writing DLLs that interface to LabVIEW cintools headers should not be done by writing them and then importing them using the wizard but instead you should write the VI and create the Call Library Node, then let LabVIEW create a template C file from the context menu of the Call Library Node and copy that into your C sources and fill in the functions from there.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Header file 'dlfcn.h' not found

Hi,
I am trying to compile some dynamic library stuff in my application. I am getting the error "header file 'dlfcn.h' not found". I searched for the file dlfcn.h in directory "/usr/include" and "/usr/local/include" but unable to find the file.
Please help me how to download this file?
Thanks

Hi header file........................etc
You could make your own.
Script is here;
http://www.koders.com/c/fid7E0BB9E61334ACD4F547A739488E20E0F68C502E.aspx
Just leave out the line numbers at the start of each line.
regards roam

Header File Not Found

I installed the TestU01 Suite for testing some random number generators I am working on, but when I use the #includes in my code, the systems says it can't find them at compile time. I followed the instructions for downloading and installing the library from Dr. Richard Simard's site . Its in the MinGW repository for the Linux environment MSYS. I point Eclipse straight at it for the project and Eclipse says it can't find the file upon compiling. See attached images.
From the attached images you can see that I have gone in and for this project added a custom path to where the include files were installed with MSYS. You can also see that Eclipse did add those paths as a valid path for includes in the project folder. However when I go to build the project Eclipse says there is an error, S4, and the error specifically states that the file can't be found. However, it is listed in the path of the includes so Eclipse should be able to see it.

So I got Eclipse to find the header files, and I believe I have set up the library additions appropriately. I have even changed \ to / in all the areas that a library or the includes folder was added.
Eclipse in the file now sees the header and even allows me to make variable of the struct type that is in the header. However when I go to use several of the functions from the header I am getting an "undefined reference" error. I have checked, and the function names are correct.
Will not compile with these errors, and I really need to use this tool set/library for a project I am working on. Any help would be appreciated.

Header files not found

I have a piece of code in C with header files included.
I run it on Mac OS X Maverick with XCode 4.6.2 installed. GCC is also installed. Note that Command Line Tools in XCode are already installed.
When I compile it, the error I receive says something like this:
add.c:1:19: error: stdio.h: No such file or directory
add.c:2:20: error: stdlib.h: No such file or directory
add.c:3:20: error: unistd.h: No such file or directory
However when I run it on Ubuntu, it compiles without a problem.
what to do?

fredjefrito wrote:
I run it on Mac OS X Maverick with XCode 4.6.2 installed. GCC is also installed. Note that Command Line Tools in XCode are already installed.
That doesn't add up. Doesn't Mavericks require Xcode5? Regardless, you should install Xcode5. Forget GCC. That's obsolete.

Place function in header file?

Hello, again.
Suppose I have a piece of code that I know I am going to be using very often. Obviously, the logical thing to do is place it in a function. And, suppose that I know I'm going to be calling that function often, and in a lot of different projects. How can I best make it so that I don't have to declare and define the function in every file in every project that I want to use this function in?
Would I place the function in a header file, and then use the #include preprocessor directive to include the .h file in every file I want to use the function in? If so, why couldn't I just store the function in a .c/.cpp file? What does a header file offer over a .c or .cpp file -- why use one over the other?
Also, where do I go to create the header file? If I go to File > New File and select header file, then it creates it as a file within the project that I have open at that moment, and I'm going to want to use the file in other projects. Is there somewhere I can save the header file outside of any specific project, so that I can include it in any project I want?
Thanks.

Tron55555 wrote:
So, technically, I could define the entire function in the header file, even without declaring it as inline, and I wouldn't have to define it in a source file?
Nope. You'll get linker errors, or at least warnings, about the function being defined twice.
1.) Why define it in a source file in the first place? Why not always define it in the header file? I can imagine there's obviously a very good reason for this -- I'm just curious what it is.
Code bloat and the sheer inefficiency of having the same code duplicated everywhere.
2.) You said that if the function is defined in the header file instead of a source file then it is treated as a macro and the whole function is picked up and dropped in your code wherever it is called. This sounds like the same thing as an inline function, so if you did define the entire function in the header file, what would be the difference between defining the whole thing in the header file using the inline keyword, versus defining the whole thing in the header file without the inline keyword?
Well, it is an inline function. You must use the inline keyword.
3.) Finally, if I did decide to define the entire function in the header file and not use a source file, would I still need to write the function signature as well, or just the definition?
Just the definition.

Error Reading Header File When Creating a CIN

Hello everyone. I am a college student new to LabView and Im using the
software to create a real time data acquisition system for EMG signal
analysis for a research project. However, Im having difficulty building
a CIN for my C code. I am using Microsoft Visual Studio.NET 2003 and
running LabView 7.1 on Windows XP. I am using the "Using External Code
in LabView" (April 2003 Edition) manual and I am attempting to do the
steps located in section 3-15 under Visual C++ IDE. However, I keep
getting fatal error C1083: Cannot open include file: 'extcode.h': No
such file or dir. I have followed all of the directions in the manual
and even explicitly tried adding extcode.h to my project but I
still get this error. My version of Visual Studio is different then the
one described so I was wondering if there is something different that I
have to do in this process. Any help would be greatly appreciated.
Thanks for your time.
Pat

Is there a particular reason you're not using a Call Library Function Node to call a DLL instead of using a CIN? Calling DLLs from Call Library Function Node are usually a much more user-friendly process, which I would recommend, unless you need to take advantage of the extra features listed on page 1-4 of Using External Code in LabVIEW.
Jarrod S.
National Instruments

How can I use a dll if I dont have a header file

I'm not sure if I'm even trying the possible here as I have searched and not been able to find much at all. However I figured it was worth asking here.
I have access to several dll's used by a program, I need to open a file using the program (for some reason it is completely non responsive unless you open it "within" the program itself) and so decided to browse the .dll files included. Ive found a few functions which may carry out the function I need. Is there a way of figuring out the inputs/outputs if I don't have documentation or a header file?
This is the next stage in a huge project I am working on at the moment and I've been banging my head against the wall all day trying to figure this out.
Thanks in advance for any help
Rik
That glass?
Thats glass is neither half full or half empty....
Its twice the size it needs to be

Yes, that makes sense. It also means that what you are trying to do is not likely to work. You have no way of knowing what the program does when opening the file, so guessing at using the DLLs is purely a shot in the dark without even knowing where the dark is. Even if you could find the function (assuming it's just one) that loads a file, how is the program supposed to use it now? That function has to be called from within the program. When you call it from LabVIEW you are not sitting inside the program's memory space, so it has no way of knowing about the file.
I would suggest, instead, to see if the program accepts command-line parameters. For example, does it accept a name of a file to open as part of launching it from the command line? If not, then you may need to resort to trying to control it via automation. If it has no built-in automation then you need to resort to using the OS to make pretend you're clicking buttons and typing text. This has come up many times before, and there have been numerous posts on this, so please do a search on controlling an external program from LabVIEW within this forum. You can call the Windows API functions to move the mouse to a specific location and click the button as well as typing text, or you can use third-part automation tools. One that I have used successfully is AutoIt. The search I indicated will yield other suggestions.

Header file entry for Text Channel

I have taken an ASCII Text Data file, read the file, and created a Header File, then saved the data into a binary file. This is my attempt to speed up the loading of the text file. One of the columns is a text column, containing a flag for the state of the test. I can not figure out how to define the column as a Text Column in the Header File. If I define it as a numeric column, it returns an error for every entry in the data file. Normal (one of the states) is not a Numeric Value.
The script file(s) I am using is a modification of a script listed on this board by Brad Turpin ( TimeSlice DAT Hdr Create.zip ) The only thing I have changed is the Test for the Channel Name to see if it contains on of 3 states. If Date is present in the Channel Name , it changes the field to a Time channel, if the channel contains Relay it changes it to a Text channel (which doesn't work), else the Channel is a Numeric.
There must be a way to define a Text Channel in a Header File. I hope someone can show me the way.
Thanks
Bill Lane
Test Engineer
Takata, INC.

Hello Bill!
The DAT format was never able to store text channels (TDM is able today). Please refer to the DAT format description on your DIAdem CD or in this post.
Your idea to convert it to a numeric value is the right way. The error message must come out of the header. Do you convert all properties to numeric values? See page 4-6 and following in the header description or search for the word 'normal' in the created header file.
Matthias
Matthias Alleweldt
Project Engineer / Projektingenieur
Twigeater?

Couldn't crate task file; SAP R/3 4.7 Installation, ORacle9i, Sun Solaris

Hi all
Am doing Remote instllation through Windows desptop.
While installing Database instance at Database load (Porst Processing) step encountered error MSC-01004, Couldn't crate task file /oracle/SID/ora<sid>/sapdata/SAPSSEXC.TSK.
Details are :
User: Root
Pwd: /oracle/SID/ora<sid>/sapdata/
Any body faced problem like this...
Regards

Hi all,
Thanks for responses.
I found the resolution. The funny thing is while installation system looking for files in UPPER case where as the original CDs contain file names in lower case.
Once I changed to Upper case, Installation progressed.
Regards

How to include the RNDISFN.h header file in the WIN CE Build ?

I need to include the header file RNDISFN.h in the build of the WIN CE OS. By default the file is not included.
What do i need to include in the OS design to have the Header file compiled ?
Who can help ? (thx in advance to all these brave people that help in this forum)

Hello Mads, please check my answer to your previous question...
[click]
Regards,
Mariusz

Deploying an EJB WebService under WLS 9.1 - port component "Hello" is not found in wsdl.

Hi,
I'm trying to deploy a simple EJB webservice example on WLS 9.1. The appc
compile works fine, but the server deployment throw the following error
message:
[java] port component "Hello" is not found in wsdl.
It's simple JAX-RPC based webservice where a SessionBean method is used as
the service implementation. The same configuration (webservice.xml,
mapping.xml and HelloService.wsdl) works fine under JBoss 4.0, but not with
WLS 9.1. Maybe it's a simple configuration error and someone can help.
Regards
Guido
Appendix
webservice.xml
<webservices xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1\.xsd"
version="1.1">
<webservice-description>
<webservice-description-name>HelloService</webservice-description-name>
<wsdl-file>META-INF/wsdl/HelloService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/mapping.xml</jaxrpc-mapping-file>
<port-component>
<port-component-name>Hello</port-component-name>
<wsdl-port>HelloPort</wsdl-port>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<service-impl-bean>
<ejb-link>HelloBean</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
</webservices>
mapping.xml
<?xml version="1.0" encoding="UTF-8"?>
<java-wsdl-mapping version="1.1" xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/</namespaceURI>
</package-mapping>
<service-interface-mapping>
<service-interface>com.jcoffee.components.ws.HelloService</service-interface
>
<wsdl-service-name
xmlns:serviceNS="http://ws.components.jcoffee.com/">serviceNS:HelloService</
wsdl-service-name>
<port-mapping>
<port-name>HelloPort</port-name>
<java-port-name>HelloPort</java-port-name>
</port-mapping>
</service-interface-mapping>
<service-endpoint-interface-mapping>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<wsdl-port-type
xmlns:portTypeNS="http://ws.components.jcoffee.com/">portTypeNS:Hello</wsdl-
port-type>
<wsdl-binding
xmlns:bindingNS="http://ws.components.jcoffee.com/">bindingNS:HelloBinding</
wsdl-binding>
<service-endpoint-method-mapping>
<java-method-name>hello</java-method-name>
<wsdl-operation>hello</wsdl-operation>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_hello</w
sdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
<wsdl-return-value-mapping>
<method-return-value>java.lang.String</method-return-value>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_helloRes
ponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
</service-endpoint-interface-mapping>
</java-wsdl-mapping>
HelloService.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://ws.components.jcoffee.com/"
xmlns:tns="http://ws.components.jcoffee.com/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types/>
<message name="Hello_hello">
<part name="String_1" type="xsd:string"/>
</message>
<message name="Hello_helloResponse">
<part name="result" type="xsd:string"/>
</message>
<portType name="Hello">
<operation name="hello" parameterOrder="String_1">
<input message="tns:Hello_hello"/>
<output message="tns:Hello_helloResponse"/>
</operation>
</portType>
<binding name="HelloBinding" type="tns:Hello">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="hello">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</input>
<output>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</output>
</operation>
</binding>
<service name="HelloService">
<port name="HelloPort" binding="tns:HelloBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</port>
</service>
</definitions>
and last but not least the ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
<display-name>JCoffee web service sample</display-name>
<enterprise-beans>
<session>
<ejb-name>HelloBean</ejb-name>
<service-endpoint>com.jcoffee.components.ws.Hello</service-endpoint>
<ejb-class>com.jcoffee.components.ws.HelloBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<method-permission>
<unchecked/>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
<container-transaction>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

Hi again,
I got it - i've forgot the namespace prefix for the wsdl-port.
Now it works.
Thanks!
"Ben" <[email protected]> schrieb im Newsbeitrag
news:[email protected]...
Hi,
I'm trying to deploy a simple EJB webservice example on WLS 9.1. The appc
compile works fine, but the server deployment throw the following error
message:
[java] port component "Hello" is not found in wsdl.
It's simple JAX-RPC based webservice where a SessionBean method is used as
the service implementation. The same configuration (webservice.xml,
mapping.xml and HelloService.wsdl) works fine under JBoss 4.0, but notwith
WLS 9.1. Maybe it's a simple configuration error and someone can help.
Regards
Guido
Appendix
webservice.xml
<webservices xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1\.xsd"
version="1.1">
<webservice-description>
<webservice-description-name>HelloService</webservice-description-name>
<wsdl-file>META-INF/wsdl/HelloService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/mapping.xml</jaxrpc-mapping-file>
<port-component>
<port-component-name>Hello</port-component-name>
<wsdl-port>HelloPort</wsdl-port>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<service-impl-bean>
<ejb-link>HelloBean</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
</webservices>
mapping.xml
<?xml version="1.0" encoding="UTF-8"?>
<java-wsdl-mapping version="1.1" xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/</namespaceURI>
</package-mapping>
<service-interface-mapping>
<service-interface>com.jcoffee.components.ws.HelloService</service-interface
>>
<wsdl-service-name
xmlns:serviceNS="http://ws.components.jcoffee.com/">serviceNS:HelloService</
wsdl-service-name>
<port-mapping>
<port-name>HelloPort</port-name>
<java-port-name>HelloPort</java-port-name>
</port-mapping>
</service-interface-mapping>
<service-endpoint-interface-mapping>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<wsdl-port-type
xmlns:portTypeNS="http://ws.components.jcoffee.com/">portTypeNS:Hello</wsdl-
port-type>
<wsdl-binding
xmlns:bindingNS="http://ws.components.jcoffee.com/">bindingNS:HelloBinding</
wsdl-binding>
<service-endpoint-method-mapping>
<java-method-name>hello</java-method-name>
<wsdl-operation>hello</wsdl-operation>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_hello</w
sdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
<wsdl-return-value-mapping>
<method-return-value>java.lang.String</method-return-value>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_helloRes
ponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
</service-endpoint-interface-mapping>
</java-wsdl-mapping>
HelloService.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://ws.components.jcoffee.com/"
xmlns:tns="http://ws.components.jcoffee.com/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types/>
<message name="Hello_hello">
<part name="String_1" type="xsd:string"/>
</message>
<message name="Hello_helloResponse">
<part name="result" type="xsd:string"/>
</message>
<portType name="Hello">
<operation name="hello" parameterOrder="String_1">
<input message="tns:Hello_hello"/>
<output message="tns:Hello_helloResponse"/>
</operation>
</portType>
<binding name="HelloBinding" type="tns:Hello">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="rpc"/>
>
>
<operation name="hello">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</input>
<output>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</output>
</operation>
</binding>
<service name="HelloService">
<port name="HelloPort" binding="tns:HelloBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</port>
</service>
</definitions>
and last but not least the ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
<display-name>JCoffee web service sample</display-name>
<enterprise-beans>
<session>
<ejb-name>HelloBean</ejb-name>
<service-endpoint>com.jcoffee.components.ws.Hello</service-endpoint>
<ejb-class>com.jcoffee.components.ws.HelloBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<method-permission>
<unchecked/>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
<container-transaction>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

Header files not being included in JNI

I've written a java program which interfaces with some C code.In the c code i use certain functions which are defined in a header file that i include in the same c file.The problem i have ,is that the compiler shows an error when it comes across one of those functions.It seems to me that the header file is not being included.Here's what i've done at the start of the jni c code,any help will be greatly appreciated.
#include<stdio.h>
#include " mnt/cprog/ca.h"
JNIEXPORT void JNICALL......
Can other header files be included over here ,or do they have to be included from the java file?..but the problem there is that the header file is of .h extension.....any suggestions??
ps..The os is Linux
..Derick

If the header files are not found, the compiler will tell you. At least gcc does so. If only some functions you are using are missing, they are probably not in the header file you are including.
By the way, there is no way to include headers for your native code through Java. What kind of mechanism should that be?

Hello! Couldn't found header file extcode.h in LabVIEW 6i

Similar Messages

Maybe you are looking for