Can I develop externally in netbeans referencing JCAPS 5.1.2 OTDs?

Question

I am trying to port some old eGate 4.5.3 code into Sun JCAPS 5.1.2. I have developed a user defined OTD and have been able to unmarshall data successfully inside eDesigner. The original developer had import statements that brought in the old etd definitions to some utility classes developed in netbeans. The import statement looks like this: import com.lmco.ecs.etd.zCustomerContract.bapevbak.BAPE_VBAK; The old etd defined a record with fields in it. Can I import the otd created under Sun JCAPS in a similar manner in netbeans? Or am I stuck with eDesigner? How do I download the jar file or reference the repository so I can import the otd class?
Thank you for your help.
Chris.
Edited by: hcmason1 on Mar 27, 2009 9:47 AM

Answer 1

I am working with some of the jar files I exported from the ear file. The class I ported uses an OTD that was created from an xsd schema. The CMEHelper class I create has a constructor that takes the OTD and a boolean as parameters. I am able to create an object locally inside netbeans. However, when I try and import the jar file back into the eDesigner from the dist directory of netbeans, eDesigner can't "See" the constructor with the parameters. Have you ever experienced this? Could it be that different java compiler versions are mangling the names? When I run javap against CMEHelper.class on my computer it can understand the clas = Compiled from "CMEHelper.java"
public class com.lmco.ecs.cme.CMEHelper extends java.lang.Object{....  The signature of the Constructor is detected =     public com.lmco.ecs.cme.CMEHelper(xsd.CME_CME_534859835.CME,boolean);  I have netbeans building the class using D:\j2sdk1.4.2_13\bin\javac I'm pretty sure...Now that I have removed the fastjavac reference from eDesigner, maybe it's getting the old 1.3.1 compiler I also have for the eGate 4.5.3 stuff I maintain...I was able to reference the OTD by importing CME_CME200904081331580577.jar as a jar file in netbeans.  I also had to import some of the xml jar files such as com.stc.otd.xsdimpl.jar.  Maybe this is a result of packages namespace rules?