JAXB Compile error
I am new to JAXB and I would like to access XML data directly from an XML file without regarding the XML format and structure. As a result, I have followed the steps mentioned in the http://java.sun.com/developer/technicalArticles/WebServices/jaxb/index.html.
Step 1>
I can successfully generate a set of java classes and interfaces that represent the schema.
Step 2>
I run the following command: javac GCCities/jaxb/*.java GCCities/jaxb/impl/*.java
and then get the following error:
"GCCities\jaxb\impl\GuaranteeCalculatorCitiesReturnMessagesImpl.java:1: illegal escape character"
"GCCities\jaxb\impl\GuaranteeCalculatorCitiesReturnMessagesImpl.java:2: illegal escape character"
"GCCities\jaxb\impl\GuaranteeCalculatorCitiesReturnMessagesImpl.java:27: illegal escape character"
For your Information:
My OS is windows XP and jwsdp 1.5. Please help!
I dump the content of the GuaranteeCalculatorCitiesReturnMessagesImpl.java file.
// This file was generated by the JavaTM Architecture for XML Binding(JAXB) Reference Implementation, v@@BUILD_VERSION@@
// See http://java.sun.com/xml/jaxb
// Any modifications to this file will be lost upon recompilation of the source schema.
// Generated on: 2005.05.12 於 11:22:12 GMT+08:00
\u000d\u000a\u0070\u0061\u0063\u006b\u0061\u0067\u0065\u0020\u0047\u0043\u0043\u0069\u0074\u0069\u0065\u0073\u002e\u006a .....
The content of the java file is very strange but it is generated by the jAXB bining compiler automatically by running the following command:
xjc.bat -p GCCities.jaxb GCCities.xsd -d work
On the other hands, Even if I try the sample attached with the JAXB(jwsdp-1.5), the same error "illegal escape character" is met.
Similar Messages
-
JAXB compiler error : Complex Type Definition Representation Error
Hi,
I have a problem when I try to generate Java classes for the XML Digital Signature schema along with the XAdES extension. Apparently, we got an XML validation issue when the XAdES schema is parsed.
Here is the xjc tool ouput :
[ERROR] src-ct.1: Complex Type Definition Representation Error for type 'IdentifierType'. When complexContent is used, the base type must be a complexType.
line 33 of XAdES.xsd
[ERROR] src-ct.1: Complex Type Definition Representation Error for type 'EncapsulatedPKIDataType'. When complexContent is used, the base type must be a complexType.
line 57 of XAdES.xsdNow these are the schema lines from XAdES.xsd that cause the problem :
<xsd:complexType name="IdentifierType">
<xsd:complexContent>
<xsd:extension base="xsd:anyURI">
<xsd:attribute name="Qualifier" type="QualifierType" use="optional"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="EncapsulatedPKIDataType">
<xsd:complexContent>
<xsd:extension base="xsd:base64Binary">
<xsd:attribute name="Id" type="xsd:ID" use="optional"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>The most disturbing thing is that those two schemas I used (e.g. xmldsig-core-schema.xsd and XAdES.xsd) come directly from the W3C, so they should be fully compliant to the XML schema spec, shouldn't they ?
Moreover, I tried to validate these two schemas with XML Spy 4.3 and the problem occurs in slightly different way. In fact, the <xsd:complexContent> tags are replaced silently by XML Spy with <xsd:simpleContent> tags in order to validate the schema. So XML Spy seems to have a problem too with these complex type definitions. Besides, if I replace the <xsd:complexContent> tags the same way as XML Spy does, and if I run again the JAXB compiler, it works fine...
Does anyone have any knowledge about this issue ? I'd like very much to hear about anyone who has experienced or better solved the same kind of issue.
By the way, here is the version of JAXB that I use :
xjc version "1.0.2-b15-fcs"
JavaTM Architecture for XML Binding(JAXB) Reference Implementation, (build 1.0.2-b15-fcs)Any help appreciated.
Thanks,
Gregory<xsd:extension base="xsd:anyURI">
<xsd:extension base="xsd:base64Binary">
The base attribute of the xs:extension elements shoule refer to a complexType.
For example,
<xs:complexType name="complexTypeA">
</xs:complexType>
<xsd:complexType name="IdentifierType">
<xsd:complexContent>
<xsd:extension base="complexTypeA">
<xsd:attribute name="Qualifier" type="QualifierType" use="optional"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType> -
I got this error when executing a jaxb compilation against my xml schema
JAXB Compilation Exception: java.lang.Exception: Un problème est survenu parce que des fonctions de schéma XML non prises en charge sont utilisées dans le schéma. La définition de contraintes d'identité (identity-constraint), à savoir "key", "keyref" et "unique", n'est pas prise en charge. Utilisez le paramètre -extension.
Here is my xml schema :
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="classification">
<xs:annotation>
<xs:documentation source="../classification-reference-fr.doc" xml:lang="fr">Documentation de référence en français</xs:documentation>
<xs:documentation source="../classification-reference-de.doc" xml:lang="de">Deutsche Referez Beschreibungen des Schema</xs:documentation>
<xs:documentation source="../classification-reference-it.doc" xml:lang="it"/>
<xs:documentation source="../classification-reference-en.doc" xml:lang="en"/>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="classification-name" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation xml:lang="fr">Dénomination de la classification gérée dans le document</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:restriction base="classification-nameType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element ref="classification-version" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation xml:lang="fr">Liste des versions de la classification gérée dans le document. Les entrées originales sont maintenus si elles sont modifiées. Chaque modification est associée à une version. Les états antérieurs ou la liste des changements intervenus à chaque nouvelle version peuvent être obtenus en tout temps.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="classification-language">
<xs:complexType>
<xs:sequence>
<xs:element name="classification-language-code" type="xs:language">
<xs:annotation>
<xs:documentation xml:lang="fr">Code de la angue dans laquelle la classification peut être publiée</xs:documentation>
</xs:annotation>
<xs:unique name="classification-language-code-unique">
<xs:selector xpath="classification-language-code"/>
<xs:field xpath="."/>
</xs:unique>
</xs:element>
<xs:element name="classification-language-label" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="fr">Libellé de la angue dans laquelle la classification peut être publiée</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="classification-entry" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation xml:lang="fr">Entrées de premier niveau de la classification. Les entrées dépendantes sont répertoriées dans l'élément classification-entry-child qui met en oeuvre le même type que le présent élément. La hierarchie est donc récursive jusqu'au niveau de détail souhaité.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="classification-entryType"/>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="schema-version" type="xs:string" use="required" fixed="1.0"/>
</xs:complexType>
</xs:element>
<xs:complexType name="classification-nameType" mixed="true">
<xs:simpleContent>
<xs:extension base="classification-titleType"/>
</xs:simpleContent>
</xs:complexType>
<xs:element name="classification-version">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="validity-from-date" type="xs:date" use="required"/>
<xs:attribute name="validity-to-date" type="xs:date" use="optional"/>
<xs:attribute name="publication-date" type="xs:date" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:unique name="classification-version-unique">
<xs:selector xpath="classification-version"/>
<xs:field xpath="."/>
</xs:unique>
</xs:element>
<xs:complexType name="classification-entryType">
<xs:sequence>
<xs:element name="classification-entry-identification" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="fr">Code d'identification interne unique. Il est librement déterminé par les personnes chargées de la gestion de la classification. Chaque entrée est identifiée de manière unique au moyen de ce code.</xs:documentation>
</xs:annotation>
<xs:unique name="classification-id-unique">
<xs:selector xpath="classification-entry-identification"/>
<xs:field xpath="."/>
</xs:unique>
</xs:element>
<xs:element name="classification-entry-code" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="fr">Code de la classification pour ce niveau d'entrée. La classification est organisée sous la forme d'une hierarchie. Les niveaux précédents ne sont pas contenus dans le présent code, ils découlent du code du précédent niveau dans lequel l'entrée a été introduite.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="classification-entry-code-fullPath" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="fr">Code complet de la classification comprenant tous les codes des niveaux précédents et le code du présent niveau. Le code complet est généré, il ne devrait a priori ne pas être modifié manuellement. Il représente une clé utilisée pour les références utilisées lorsque des liens entre les entrées autre que hierarchiques sont déclarés.</xs:documentation>
</xs:annotation>
<xs:unique name="classification-entry-code-fullPath">
<xs:selector xpath="classification-entry-code-fullPath"/>
<xs:field xpath="."/>
</xs:unique>
</xs:element>
<xs:element name="classification-entry-status">
<xs:annotation>
<xs:documentation xml:lang="fr">Statut qui active ou desactive l'entrée. Le statut permet de gérer des entrées à titre historique, notamment des codes qui n'ont plus court mais qui ont existé dans des versions précédentes.</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="enable"/>
<xs:enumeration value="disable"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="classification-entry-title" type="classification-entry-titleType">
<xs:annotation>
<xs:documentation xml:lang="fr">Ensemble de titres pour l'entrée de la classification</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="classification-entry" type="classification-entryType" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation xml:lang="fr">Classification dépendante de la l'entrée de la classification</xs:documentation>
</xs:annotation>
<xs:keyref name="classification-id-ref" refer="classification-id-unique">
<xs:selector xpath="classification-entry-reference"/>
<xs:field xpath="."/>
</xs:keyref>
</xs:element>
<xs:element name="classification-entry-update" type="classification-entry-updateType" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation xml:lang="fr">Gestion des modification et des versions des entrées de la classification</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="classification-entry-link" type="classification-entry-linkType" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation xml:lang="fr">Liens non hierarchiques entre les entrées de la classification. Ces liens sont utilisésen particulier pour gérer les inclusions ou exclusions.</xs:documentation>
</xs:annotation>
<xs:keyref name="classification-entry-link-keyref" refer="classification-entry-code-fullPath">
<xs:selector xpath="classification-entry-link"/>
<xs:field xpath="."/>
</xs:keyref>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="classification-entry-titleType">
<xs:sequence>
<xs:element name="classification-entry-main-title" type="classification-main-titleType" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation xml:lang="fr">Titre principal de l'entrée de la classification. Les différents type de titres sont publiés de manière distinctes. Plusieurs titres principaux peuvent être introduits pour une même langue. Ils seront publiés dans l'ordre dans lesquels ils sont placés dans le document.</xs:documentation>
</xs:annotation>
<xs:keyref name="classification-entry-main-title-language-keyref" refer="classification-language-code-unique">
<xs:selector xpath="classifcation-entry-main-title"/>
<xs:field xpath="@language"/>
</xs:keyref>
</xs:element>
<xs:element name="classification-entry-complementary-title" type="classification-complementary-titleType" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation xml:lang="fr">Titre complémentaire de l'entrée de la classification. Les différents type de titres sont publiés de manière distinctes. Plusieurs titres comolémentaire peuvent être introduits pour une même langue. Ils seront publiés dans l'ordre dans lesquels ils sont placés dans le document.</xs:documentation>
</xs:annotation>
<xs:keyref name="classification-entry-complementary-title-language-keyref" refer="classification-language-code-unique">
<xs:selector xpath="classifcation-entry-complementary-title"/>
<xs:field xpath="@language"/>
</xs:keyref>
</xs:element>
<xs:element name="classificatin-entry-index-title" type="classification-index-titleType" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation xml:lang="fr">Titre utilisé pour les entrées dans les différents index lorsqu'ils sont différents du texte prévu dans l'index principal ou les entrées complémentaires.</xs:documentation>
</xs:annotation>
<xs:keyref name="classification-entry-index-title-language-keyref" refer="classification-language-code-unique">
<xs:selector xpath="classifcation-entry-index-title"/>
<xs:field xpath="@language"/>
</xs:keyref>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="classification-main-titleType">
<xs:simpleContent>
<xs:extension base="classification-titleType"/>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="classification-complementary-titleType">
<xs:simpleContent>
<xs:extension base="classification-titleType"/>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="classification-index-titleType">
<xs:simpleContent>
<xs:extension base="classification-titleType"/>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="classification-entry-updateType">
<xs:sequence>
<xs:element name="classification-update-version">
<xs:annotation>
<xs:documentation xml:lang="fr">Version pour laquelle la modification a été apportée</xs:documentation>
</xs:annotation>
<xs:keyref name="update-version-keyref" refer="classification-version-unique">
<xs:selector xpath="update-version"/>
<xs:field xpath="."/>
</xs:keyref>
</xs:element>
<xs:element name="classification-update-date">
<xs:annotation>
<xs:documentation xml:lang="fr">Date à laquelle le changement a été apporté</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="classification-update-author">
<xs:annotation>
<xs:documentation xml:lang="fr">Auteur de la modification. L'auteur de la modification est une personne autorisée déclarée dans le document xml correspondant.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="classification-update-category">
<xs:annotation>
<xs:documentation xml:lang="fr">Type de modification apportée à la classification</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="new entry"/>
<xs:enumeration value="updated entry"/>
<xs:enumeration value="suppressed entry"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="classification-update-description" type="update-descriptionType" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation xml:lang="fr">Description textuelle de la modification apportée. Cette description fera l'objet d'une entrée dans le journal des modifications apportées pour la version</xs:documentation>
</xs:annotation>
<xs:keyref name="classification-update-description-language-keyref" refer="classification-language-code-unique">
<xs:selector xpath="classifcation-update-description"/>
<xs:field xpath="@language"/>
</xs:keyref>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="update-descriptionType">
<xs:attribute name="language" type="xs:language" use="required"/>
</xs:complexType>
<xs:complexType name="classification-titleType" mixed="true">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="language" type="xs:language" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="classification-entry-linkType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="link-type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="excluding"/>
<xs:enumeration value="including"/>
<xs:enumeration value="seeAlso"/>
<xs:enumeration value="completeAlso"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:schema>The same xml schema compile sucessfully in top link workbench ...
-
I have a problem during the compiling of a schema. It returns the following errors:
parsing a schema...
[WARNING] src-import.0: Failed to read imported schema document 'xlink.xsd'.
line 29 of graphml-structure.xsd
[ERROR] src-resolve: Cannot resolve the name 'xlink:href' to a(n) attribute decl
aration component.
line 663 of graphml-structure.xsd
[ERROR] src-ct.0.1: Complex Type Definition Representation Error for type 'locat
or.type'. Element 'attribute' is invalid, misplaced, or occurs too often.
line 663 of graphml-structure.xsd
At the 29th line of "graphml-structure.xsd" is written:
<xs:import namespace="http://www.w3.org/1999/xlink" schemaLocation="xlink.xsd">
I visited that page but I haven't found any xlink.xsd. Any idea?Well, in the end I fixed that in some way... I got from a friend of mine the xlink.xsd (why is it not available at w3c web site?! Or maybe I simply didn't find it) and succeeded in the compiling. The Java code generated was too much for my tastes though, so I decided to drop JAXB and use Xerces/SAX in its place. That surely meant a little more coding efforts, but it defintely resulted in a cleaner and shorter code, hence in a faster execution of the application.
-
JAXB Bindings - error while compiling Schema(s)
Hello, I want to create Java classes from a XML Schema by using JAXB Binding. However, when I do that a message error appears: "Error while compiling Schema" and then it says:
"C:\...\NetBeansProjects\myproject\build.xml:12: Problem: failed to create task or type import
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place."
Does anybody know what it's happening? It could be that there is a .jar missing?
Thank you very muchThe document build.xml at line 12 says <import file="nbproject/build-impl.xml"/>. The file nbproject / build-impl.xml exists. If you want I could send it to you.You could post it here (the build-impl.xml, I mean).
I have a working example, we could compare.
I have included all the .jar you mentioned (excep the jaxb1-imp.jar).?
If you added this JAXB compiling target via NB's wizard, as you describe below, you shouldn't have to "include" whatever jars wich are already in the JDK. That is, if you're using JDK6 - JAXB was not (or not so much) included in the JDK prior to 1.6.
If the JDK is 1.5, I have no idea where you have to add these jars, possibly you're not add them in the correct classpath. Presumably Ant itself would need them in its classpath to be able to define the task.
And I have not touched anythingThey all say that... :o)
the only thing I did was to add other .jars (for other purposes).See?
Is it possible that you removed one of the important jars when doing back-and-forth tries?
But anyway I went back to remove this new .jars and the JAXB Binding still doesn't work .
Should I uninstall the IDE and re-install? I do not know what else to do ...Do you have any reason to believe you did corrupt the JDK or NetBeans's installation? For example, when you write about adding/removing the mentioned jars, did you do that somewhere in the JDK or NB installation?
Other than that, I don't see what reinstalling NB would do.
Without going to such extremes, have you tried simply to remove the JAXBBinding, and add it again in the NetBeans project, using the wizard? -
JAXB binding compiler error "Unique Particle Attribution"
I'm trying to compile an xsd but get an error:
parsing a schema...
[ERROR] cos-nonambig: "":SomeData and WC[##any] (or elements from their substitution group) violate "Unique Particle Attribution".
line 4 of TestCase.xsd
Failed to parse a schema.
I've narrowed the error down to this test case:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="AnElement" type="AnElementType"/>
  <xs:complexType name="AnElementType">
  <xs:sequence>
  <xs:element name="SomeData" type="xs:string" minOccurs="0"/>
  <xs:any minOccurs="0"/>
  </xs:sequence>
  </xs:complexType>
</xs:schema>
If I remove the 'minOccurs' from the 'SomeData' element, it compiles fine. Any ideas on why Sun's JAXB compiler doesn't like this xsd?
Thanks,
JoshDoes modifying the schema remove the error?
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="AnElement" type="AnElementType"/>
<xs:complexType name="AnElementType">
<xs:choice>
<xs:any minOccurs="0"/>
<xs:sequence>
<xs:element name="SomeData" type="xs:string" minOccurs="1"/>
<xs:any minOccurs="0"/>
</xs:sequence>
</xs:choice>
</xs:complexType>
</xs:schema>
thanks,
Deepak -
Compilation Error: "class or interface expected" for simple EAR???
Dear all,
I have access to the customers NW CE 7.1 SP07 and of course I am using the corresponding NWDS 7.1 SP07 that comes with this CE installation. I am trying to study JEE 5 @ SAP and I have created a very simple Application (from the Book http://www.sap-press.de/katalog/buecher/titel/gp/titelID-1480).
In NWDS I have created the following 4 projects:
1. Dictionary Project
Describes 2 Tables (TMP_EMPLOYEES and TMP_ID_GEN)
2. EJB 5 Project
Contains a stateless EJB + local business interface + Entity class.
The EJB accesses the entity class, which is mapped to a simple table (TMP_EMPLOYEES).
3. Dynamic Web Project
Contains actually only one JSP (index.jsp) which allows to the local business interface for creating a new Entity.
4. Enterprise Application Project (EAR)
Creates a package from 2. and 3.
I have successfully deployed both the Dictionary Project and the EAR (all to the same server).
But If I call the corresponding URL via web browser I get the following error:
500 Internal Server Error
"Error in compiling [/EmployeeWeb/index.jsp] in application [sap.com/EmployeeEar]."
Details: "The WebApplicationException log ID is [005056841108002A00000070000007AC0139C8D8862D3EED]."
In the "Log Viewer" of the "SAP NetWeaver Administrator" (via browser...) I have found the following:
Message: Processing HTTP request to servlet [jsp] finished with error.
The error is: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error in executing the compilation process: [ Compilation Failed! Exit Code=1
Command line executed: D:\usr\sap\CED\J00\exe\sapjvm_5\bin\\javac -source 1.5 -target 1.5 -encoding UTF-8 -d "D:\usr\sap\CED\J00\j2ee\cluster\apps\sap.com\EmployeeEar\servlet_jsp\EmployeeWeb\work" -sourcepath "D:\usr\sap\CED\J00\j2ee\cluster\apps\sap.com\EmployeeEar\servlet_jsp\EmployeeWeb\work\;" -classpath ".;D:\usr\sap\CED\J00\exe\jstartup.jar;D:\usr\sap\CED\J00\exe\sapjvm_5\lib\jvmx.jar;D:\usr\sap\CED\J00\exe\jre\lib\iqlib.jar;D:\usr\sap\CED\J00\exe\sapjvm_5\lib\tools.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\boot\jaas.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\boot\memoryanalyzer.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\jperflib.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\jta.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~cache_api~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~frame~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~gui~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~iqlib~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~jdsr~jdsr.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~jkernel_cache~frame.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~jkernel_classload~frame.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~jkernel_cluster~frame.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~jkernel_configuration~frame.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~jkernel_database~frame.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~jkernel_licensing~frame.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~jkernel_locking~frame.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~jkernel_log~api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~jkernel_pool~frame.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~jkernel_service~frame.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~jkernel_thread~frame.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~jkernel_util~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~bl~opensqlkernel~implOpenSQLFrame.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~exception~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~je~sessionmgmt~api_assembly.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~logging~java~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\sap.com~tc~logging~java~implPerf.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\system\vmc_storage_provider.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\timeout\sap.com~tc~je~timeout~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\servlet\servlet.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\cross_api\sap.com~tc~je~cross_api~API.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\core_lib\sap.com~tc~antlr~runtime.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\core_lib\sap.com~tc~bl~config~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\core_lib\sap.com~tc~bl~cpt~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\core_lib\sap.com~tc~bl~jarm~jarm.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\core_lib\sap.com~tc~bl~opensqlkernel~implOpenSQL.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\core_lib\sap.com~tc~bl~opensqlkernel~implOpenSQLPort.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\core_lib\sap.com~tc~dd~db~dictionarydatabase~implDictionaryDatabase.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\core_lib\sap.com~tc~je~bootstrap_core_lib~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\core_lib\sap.com~tc~sec~secstorefs~java~core.jar;D:\usr\sap\CED\J00\exe\mssjdbc\sqljdbc.jar;D:\usr\sap\CED\SYS\global\security\lib\engine\iaik_jce.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\log\sap.com~tc~je~log_api~API.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\mail-activation-iaik\mail.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\mail-activation-iaik\sap.com~tc~je~javamail_lib~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\mail-activation-iaik\activation.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\mail-activation-iaik\iaik_jsse.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\mail-activation-iaik\iaik_smime.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\mail-activation-iaik\iaik_ssl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\mail-activation-iaik\w3c_http.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\com.sap.security.api.sda\sap.com~tc~sec~ume~api~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\com.sap.security.api.sda\sap.com~tc~sec~ume~perm~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\security_api\sap.com~tc~je~security_api~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\shell\sap.com~tc~je~shell_api~API.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\cross\sap.com~tc~je~cross~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\visual_administration\sap.com~tc~bl~visual_administration~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\shell\sap.com~tc~je~shell~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\p4\sap.com~tc~je~p4~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\sapxmltoolkit\sap.com~tc~sapxmltoolkit~sapxmltoolkit.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\jts\jts.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~jmx\sap.com~tc~bl~pj_jmx~Impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~mmodel~lib\sap.com~tc~je~mmodel~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\appcontext_api\sap.com~tc~je~appcontext_api~API.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\naming\sap.com~tc~je~naming~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\j2eeca\connector.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\idl\idl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\resourceset_api\sap.com~tc~bl~resourceset~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\resourcecontext_api\sap.com~tc~bl~resourcecontext~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~bl~txmanager~plb\sap.com~tc~bl~txmanagerimpl~plb~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\transactionext_api\sap.com~tc~bl~transactionext~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\ts\sap.com~tc~je~ts~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\csiv2_api\sap.com~tc~bl~csiv2~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\iiop\sap.com~tc~je~iiop~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\file\sap.com~tc~je~file~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\com.sap.tc.Logging\sap.com~tc~logging~standard~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~bcanalysis\sap.com~tc~je~bcanalysis~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~bl~reference_graph\lib\tc~bl~reference_graph_api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\container_api\sap.com~tc~je~container_api~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\webservices\sap.com~tc~je~webservices_api~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\com.sap.util.monitor.jarm\sap.com~tc~bl~jarmsat~jarmsat.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~i18n~verify~intf\sap.com~tc~i18n~verify~intf~jar~IMPL.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~i18n~cp\sap.com~tc~i18n~cp~jar~IMPL.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~i18n~decfloat\sap.com~tc~i18n~decfloat~jar~IMPL.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~com.sap.conn.jco\sap.com~tc~bl~jco_sapj2ee~runtime.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\com.sap.mw.jco\sap.com~tc~bl~jrfc~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\keystore_api\sap.com~tc~je~keystore_api~API.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\tc~sec~certrevoc~interface\sap.com~tc~sec~certrevoc~interface~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\security.class\sap.com~tc~sec~https~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\security.class\sap.com~tc~sec~compat~core.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\security.class\sap.com~tc~sec~ssf~core.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\security.class\sap.com~tc~sec~jaas~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\security.class\sap.com~tc~sec~saml~toolkit~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\security.class\sap.com~tc~sec~csi~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\security.class\sap.com~tc~sec~util0~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\security.class\sap.com~tc~sec~userstore~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\security.class\sap.com~tc~sec~xmlbind~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\security.class\sap.com~tc~sec~destinations~lib~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\com.sap.guid\sap.com~tc~bl~guidgenerator~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\stax_api\jsr173_1.0_api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\stax_api\sjsxp.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\jaxb20\jaxb-api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\jaxb20\jaxb-xjc.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\jaxb20\jaxb-impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\saaj13\saaj-api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\saaj13\saaj-impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\jaxws_api\jaxws-api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\jws_api\jsr181-api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\javax~annotation~api\annotation-api-1.0.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\compilation_lib\sap.com~tc~bl~compilation~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~bl~base_webservices_lib\sap.com~tc~bl~base_webservices_lib.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~bl~base_webservices_lib\jaxm-api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~bl~base_webservices_lib\jaxrpc-api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~bl~base_webservices_lib\jaxr-api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~bl~base_webservices_lib\jaxws-rt.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~bl~base_webservices_lib\jaxws-tools.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~j2eedescriptors~lib\sap.com~tc~je~j2eedescriptors~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~ejb~metadata~model\lib\sap.com~tc~bl~ejb~metadata~model.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\javax~persistence~api\persistence-api-1.0.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\ejbormapping_api\sap.com~tc~je~ejbormapping_api~API.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~orpersistence~metadata~model\sap.com~tc~bl~orpersistence~metadata~model.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~jlinee~lib\sap.com~tc~jtools~util.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~jlinee~lib\sap.com~tc~jtools~jlin~core.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~jlinee~lib\sap.com~tc~jtools~jlinee~lib.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~jlinee~lib\sap.com~tc~jtools~jlinee~ear.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~jlinee~lib\sap.com~tc~jtools~jlinee~connector.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~jlinee~lib\sap.com~tc~jtools~jlinee~web.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~jlinee~lib\sap.com~tc~jtools~jlinee~ejb.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~jlinee~lib\sap.com~tc~jtools~jlinee~appclient.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~jlinee~lib\sap.com~tc~jtools~jlinee~orpersistence.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\deploy\sap.com~tc~je~deploy~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\jmx_notification\sap.com~tc~je~jmx_notification~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\runtimeinfo\sap.com~tc~je~runtimeinfo~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\jmx\sap.com~tc~je~jmx~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\jmx\sap.com~tc~je~jmx~impl~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\http\sap.com~tc~je~httpserver~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~exprlang~plb\jee5_el.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\ec~java~jstl\jstl-1_2.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~injection~lib\lib\private\tc~je~injection.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\ec~java~jsf\lib\ec~java~jsf_api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\ec~java~jsf\lib\ec~java~jsf~tld.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\ec~java~jsf\lib\private\com-sun-commons-beanutils.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\ec~java~jsf\lib\private\com-sun-commons-collections.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\ec~java~jsf\lib\private\com-sun-commons-digester.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\ec~java~jsf\lib\private\com-sun-commons-logging-api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\ec~java~jsf\lib\private\ec~java~jsf_core.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~je~jacc~plb\jacc-1_1-fr-class.zip;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\classpath_resolver\sap.com~tc~je~classpath_resolver~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\com.sap.ip.basecomps\sap.com~tc~bl~basecomps~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\sdo\lib\sap.com~sdo.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\sdo\lib\sap.com~sdo~api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\sdo\lib\sap.com~sdo~api~extension.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\ejb_api\ejb-3_0-api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\webservices_lib\sap.com~tc~je~webservices_lib~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~i18n~saptimezone\sap.com~tc~i18n~saptimezone~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~i18n~cpbase\sap.com~tc~i18n~cpbase~jar~IMPL.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\com.sap.security.core.sda\sap.com~tc~sec~ume~core~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\com.sap.security.core.sda\sap.com~tc~sec~ume~tpd~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\jms\jms.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\jms\jmsclient.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\com.sap~tc~je~jmsapi\sap.com~tc~je~jmsapi~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\userstore\sap.com~tc~je~userstore~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~SL~utility\sap.com~tc~bl~sl~utility~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\com.sap.exception\sap.com~tc~exception~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc~bl~jarsap~sda\sap.com~tc~bl~jarsap~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\tc~bl~deploy_api\sap.com~tc~bl~deploy~api.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\tc.httpclient\sap.com~tc~clients~http~all.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\tc~sec~destinations~interface\sap.com~tc~sec~destinations~interface_api~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\endpoint_api\sap.com~tc~bl~endpoint~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\connector\sap.com~tc~je~connector~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\antlr\sap.com~tc~antlr~runtime.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\dbpool\sap.com~tc~je~dbpool~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\tc~sec~destinations~provider\sap.com~tc~sec~destinations~provider~java~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\com.sap.security.core.ume.service\sap.com~tc~sec~ume~service~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\sap.com~tc~je~constants~lib\lib\tc~je~constants.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\schemaprocessor~srv\sap.com~tc~je~schemaprocessor.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\tc~je~webcontainer~api\sap.com~tc~je~webcontainer~webcontainer_api_impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\servlet_jsp\sap.com~tc~je~webcontainer~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\objectProfiler\sap.com~tc~bl~objectProfiler~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\tc~je~cachemgmt~srv\sap.com~tc~je~cachemgmt~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\locking\sap.com~tc~je~locking~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\configuration\sap.com~tc~je~configuration~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\basicadmin\sap.com~tc~je~basicadmin~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\basicadmin\jstartupapi.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\basicadmin\jstartupimpl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\adminadapter\sap.com~tc~je~adminadapter~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\security\sap.com~tc~je~security~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\applocking\sap.com~tc~je~applocking~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\ejb20\ejb20.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\ejbqlparser\sap.com~tc~bl~ejbqlparser~lib.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\ejbqlparser\sap.com~tc~bl~ejbqlparser_3_0~lib.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\sqlmapper\sap.com~tc~bl~ejbsqlmapper~implCommonSQLMapper.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\sqlmapper\sap.com~tc~bl~ejbsqlmapper~implSQLMapperAPI.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\interfaces\ejbmonitor_api\sap.com~tc~bl~ejbmonitor~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\services\ejb\sap.com~tc~je~ejb~impl.jar;D:\usr\sap\CED\J00\j2ee\cluster\bin\ext\orpersistence_client_lib\lib\orpersistence_client_lib_api.jar;D:\usr\sap\CED\J00\j2ee\cluster\apps\sap.com\EmployeeEar\orpersistence\jars\EmployeeEjb.jar;D:\usr\sap\CED\J00\j2ee\cluster\apps\sap.com\EmployeeEar\EJBContainer\applicationjars\EmployeeEjb.jar;D:\usr\sap\CED\J00\j2ee\cluster\apps\sap.com\EmployeeEar\servlet_jsp\EmployeeWeb\work;;" -nowarn -g ["D:\usr\sap\CED\J00\j2ee\cluster\apps\sap.com\EmployeeEar\servlet_jsp\EmployeeWeb\work\JEE_jsp_index_8832250_1231538390011_1231538444324.java"]
Error stream contains:"D:\usr\sap\CED\J00\j2ee\cluster\apps\sap.com\EmployeeEar\servlet_jsp\EmployeeWeb\work\JEE_jsp_index_8832250_1231538390011_1231538444324.java:16: 'class' or 'interface' expected
import javax.servlet.*;
^
D:\usr\sap\CED\J00\j2ee\cluster\apps\sap.com\EmployeeEar\servlet_jsp\EmployeeWeb\work\JEE_jsp_index_8832250_1231538390011_1231538444324.java:17: 'class' or 'interface' expected
import javax.servlet.http.*;
^
D:\usr\sap\CED\J00\j2ee\cluster\apps\sap.com\EmployeeEar\servlet_jsp\EmployeeWeb\work\JEE_jsp_index_8832250_1231538390011_1231538444324.java:18: 'class' or 'interface' expected
import javax.servlet.jsp.*;
^
3 errors
"].005056841108002A00000070000007AC0139C8D8862D3EED Date: 2009-01-09 Time: 23:00:45:042 Category: /System/Server/WebRequests Location: com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl Application: sap.com/EmployeeEar Thread: HTTP Worker [4] Data Source: j2ee\cluster\server0\log\system\server_00.log Correlator ID: 88322500000038637 Argument Objects: Arguments: DSR Component: n.a. DSR Transaction: 10c493a0de9311dd9631005056841108 DSR User: Message Code: Session: 979 Transaction: User: Guest Host: IMGNWCED System: CED Instance: J00 Node: server0
As you can see there is some compilation error, it says 3 times "'class' or 'interface' expected". If i remove all the relevant EJB java code from my index.jsp everything works fine. So I guess there must be some problem with finding the resources. Unfortunately this "logging" is not helpful at all (thank you SAP!). In NWDS everything is fine no problems at all!!!
Who can help me here with this?
Thanks in AdvanceI have found the issue.
in the index.jsp I have the following lines:
<!-- Import Statements -->
<%@ page import="javax.naming.InitialContext" %>
<%@ page import="com.sap.demo.session.EmployeeServicesLocal;" %>
Now check the end of the second import ==> ;
Removing the semicolon solves the issue. But the SAP error message is still not very helpful to me. -
An XJC compilation error - Could not load class (..) for type cvsversion
I've got a strange compilation error using NetBeans 4.0 (I'd guess the version does not matter here) and Ant 1.6.2. When the following task is executed,
<target name="compile_ofx_schema">
<antcall target="clean-ofx"/>
<delete dir="${ofx-jaxb-src.dir}"/>
<mkdir dir="${ofx-jaxb-src.dir}" />
<xjc schema="${schema.dir}/ofx102.xsd" package="com.xxx.ofx102" target="${ofx-jaxb-src.dir}">
<arg value="-nv" />
<arg value="-extension" />
</xjc>
</target>
I get the error from NetBeans console,
Class org.xml.sax.SAXException loaded from parent loader (parentFirst)
Class java.io.IOException loaded from parent loader (parentFirst)
D:\appserver\build.xml:797: unable to parse the schema. Error messages should have been provided
at com.sun.tools.xjc.XJCTask._doXJC(XJCTask.java:334)
at com.sun.tools.xjc.XJCTask.doXJC(XJCTask.java:283)
at com.sun.tools.xjc.XJCTask.execute(XJCTask.java:227)
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 org.apache.tools.ant.Project.executeTargets(Project.java:1062)
at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:217)
at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:236)
at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:125)
BUILD FAILED (total time: 4 seconds)
Could not load class (org.apache.tools.ant.tasksdefs.cvslib.CvsVersion) for type cvsversion
Could not load class (org.apache.tools.ant.tasksdefs.cvslib.CvsVersion) for type cvsversion
And when I run the Ant task from the command line, I don't get the error at all.
Any help is greatly appreciated.That was a great finding from you. Thank you.
I followed your alternative approach and updated the ant.jar file. The "Could not load class..." error went away but the stack trace still remains. Now I am clueless again since I have ant on the debug mode and can't find any more useful info.
Class com.sun.tools.xjc.reader.internalizer.LocatorTable loaded from ant loader (parentFirst)
Class java.util.HashSet loaded from parent loader (parentFirst)
Class javax.xml.parsers.DocumentBuilderFactory loaded from parent loader (parentFirst)
Couldn't load Resource org/netbeans/core/xml/DOMFactoryImpl.class
Couldn't load ResourceStream for META-INF/services/javax.xml.parsers.DocumentBuilderFactory
Class org.apache.crimson.jaxp.DocumentBuilderFactoryImpl loaded from parent loader (parentFirst)
Class javax.xml.parsers.SAXParserFactory loaded from parent loader (parentFirst)
Couldn't load Resource org/netbeans/core/xml/SAXFactoryImpl.class
Couldn't load ResourceStream for META-INF/services/javax.xml.parsers.SAXParserFactory
Class org.apache.crimson.jaxp.SAXParserFactoryImpl loaded from parent loader (parentFirst)
Class javax.xml.parsers.DocumentBuilder loaded from parent loader (parentFirst)
Class java.util.Map loaded from parent loader (parentFirst)
Class javax.xml.parsers.SAXParser loaded from parent loader (parentFirst)
Finding class com.sun.tools.xjc.reader.xmlschema.parser.XMLSchemaInternalizationLogic$ReferenceFinder
Loaded from D:\bbw\build\Common_3.6\Packaged\appserver\lib\jaxb\jaxb-xjc.jar com/sun/tools/xjc/reader/xmlschema/parser/XMLSchemaInternalizationLogic$ReferenceFinder.class
Finding class com.sun.tools.xjc.reader.internalizer.AbstractReferenceFinderImpl
Loaded from D:\bbw\build\Common_3.6\Packaged\appserver\lib\jaxb\jaxb-xjc.jar com/sun/tools/xjc/reader/internalizer/AbstractReferenceFinderImpl.class
Class org.xml.sax.helpers.XMLFilterImpl loaded from parent loader (parentFirst)
Class com.sun.tools.xjc.reader.internalizer.AbstractReferenceFinderImpl loaded from ant loader (parentFirst)
Class com.sun.tools.xjc.reader.xmlschema.parser.XMLSchemaInternalizationLogic$ReferenceFinder loaded from ant loader (parentFirst)
Class org.xml.sax.XMLFilter loaded from parent loader (parentFirst)
Finding class com.sun.tools.xjc.reader.internalizer.VersionChecker
Loaded from D:\bbw\build\Common_3.6\Packaged\appserver\lib\jaxb\jaxb-xjc.jar com/sun/tools/xjc/reader/internalizer/VersionChecker.class
Class com.sun.tools.xjc.reader.internalizer.VersionChecker loaded from ant loader (parentFirst)
Finding class com.sun.tools.xjc.reader.internalizer.DOMBuilder
Loaded from D:\bbw\build\Common_3.6\Packaged\appserver\lib\jaxb\jaxb-xjc.jar com/sun/tools/xjc/reader/internalizer/DOMBuilder.class
Finding class com.sun.xml.bind.marshaller.SAX2DOMEx
Loaded from D:\bbw\build\Common_3.6\Packaged\appserver\lib\jaxb\jaxb-impl.jar com/sun/xml/bind/marshaller/SAX2DOMEx.class
Class org.xml.sax.ContentHandler loaded from parent loader (parentFirst)
Class com.sun.xml.bind.marshaller.SAX2DOMEx loaded from ant loader (parentFirst)
Class com.sun.tools.xjc.reader.internalizer.DOMBuilder loaded from ant loader (parentFirst)
Class java.util.Stack loaded from parent loader (parentFirst)
Class org.w3c.dom.Document loaded from parent loader (parentFirst)
Class org.xml.sax.XMLReader loaded from parent loader (parentFirst)
Class org.w3c.dom.Node loaded from parent loader (parentFirst)
Class org.w3c.dom.Element loaded from parent loader (parentFirst)
Class javax.xml.parsers.ParserConfigurationException loaded from parent loader (parentFirst)
Class org.xml.sax.SAXException loaded from parent loader (parentFirst)
Class java.io.IOException loaded from parent loader (parentFirst)
D:\bbw\build\Common_3.6\Packaged\appserver\build.xml:799: unable to parse the schema. Error messages should have been provided
at com.sun.tools.xjc.XJCTask._doXJC(XJCTask.java:334)
at com.sun.tools.xjc.XJCTask.doXJC(XJCTask.java:283)
at com.sun.tools.xjc.XJCTask.execute(XJCTask.java:227)
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 org.apache.tools.ant.Project.executeTargets(Project.java:1062)
at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:217)
at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:236)
at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:125)
BUILD FAILED (total time: 1 second)
Any suggestions? BTW, I did not upgrade NetBeans to v5.5 due that my code is still JDK1.4 based. -
JAXB validation error with sample applications
Hi,
When trying to generate the java from po.xsd in the first example I get two compile errors in the result :
"PurchaseOrderImpl.java": Error #: 454 : class {deleted root}.generated.impl.PurchaseOrderImpl should be declared abstract; it does not define method validateThis() in interface javax.xml.bind.Element at line 11, column 8
"CommentImpl.java": Error #: 454 : class {deleted root}.generated.impl.CommentImpl should be declared abstract; it does not define method validateThis() in interface javax.xml.bind.Element at line 11, column 8
where {deleted root} represents parent packages in our source tree.
Anyone else seen this?
I'm using Ant1.51 to kick off the build, with the patch referred to in Apache bug 14640. (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14640)
The target to do the build is defined as follows :-
<target name="schema" depends="init"
description="Compile schema">
<echo message="Compiling the schema..."/>
<jaxb destDir="${src}"
readOnly="true"
strictValidation="true"
xjcjar="${JAXB_HOME}\lib\jaxb-xjc.jar">
<schemas dir="${basedir}" includes="po.xsd"/>
<targetPackageMapper type="regexp"
from="(.*)\.xsd" to="{deleted root}.generated"/>
</jaxb>
</target>
where ${src} is the root of the source tree and ${basedir} is the parent directory of "generated", containing the build.xml.More precisely, this is a compile time error for the generated Java classes. The methods
void invalidate()
void validate()
void validate(Validator v)
void validateThis()
defined in
com.sun.xml.bind.validator.ValidatableObject
are not being built for
generated.impl/XTypeImpl.java
which extends
generated.impl/XImpl.java -
JAXB Compiler Interface generation problem
I have a schema where two different elements extend the same base type. The JAXB compiler throws the following error. How do I fix this?
parsing a schema...
An interface with the same name "generated.FooType" is generated from more than one schema component.
line 10 of sample.xsd
(Relevant to above error) another one is generated from this schema component.
line 23 of sample.xsd
Failed to parse a schema.
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" > <xsd:element name="Sample" type="Sample_Type"/>
<xsd:complexType name="Sample_Type">
<xsd:sequence>
<xsd:element ref="Foo"/>
<xsd:element ref="Bar"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="Foo">
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="Foo_Type"/>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="Bar">
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="Foo_Type"/>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="Foo_Type">
<xsd:sequence>
<xsd:element ref="FooBar"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="FooBar" type="FooBar_Type"/>
<xsd:simpleType name="FooBar_Type">
<xsd:restriction base="xsd:long"/>
</xsd:simpleType>
</xsd:schema>The problem is because of you have a complex type Foo_Type
Solution:
=============
Replace all occurences of Foo_Type with something else say "Some_Type"
It should work
Explaination:
=============
Basically you were getting FooType generated from 2 cases. You have an element "Foo" inside which you have an anonymous complex type. So the java class for the anonymous complex type would be "FooType"
Then you had a named complex type Foo_Type and the java class would be "FooType" again because "_" is removed when generating classes
Hence the compiler reported the error
For more explaination see Section 5.7.2 of the spec Also Table 3.2 of the spec
Also you seem to be using xjc <schemafile>
Hence the code by default gets generated in package "generated"
Recommendation
=============
Use xjc -p com.something <schemafile>
to get the package com.something -
Compilation error while calling static method from another class
Hi,
I am new to Java Programming. I have written two class files Dummy1 and Dummy2.java in the same package Test.
In Dummy1.java I have declared a static final variable and a static method as you can see it below.
package Test;
import java.io.*;
public class Dummy1
public static final int var1= 10;
public static int varDisp(int var2)
return(var1+var2);
This is program is compiling fine.
I have called the static method varDisp from the class Dummy2 and it is as follows
package Test;
import java.io.*;
public class Dummy2
public int var3=15;
public int test=0;
test+=Dummy1.varDisp(var3);
and when i compile Dummy2.java, there is a compilation error <identifier > expected.
Please help me in this program.public class Dummy2
public int var3=15;
public int test=0;
test+=Dummy1.varDisp(var3);
}test+=Dummy1.varDisplay(var3);
must be in a method, it cannot just be out somewhere in the class! -
Compile Error: "schema 'name' does not exist
Im trying to build a program that quereys a table in a database but i keep getting this error. Am i missing a link between the files or am i missing a line of code in my program??
Apologies. I receive a compiler error which reads as follows;
java.lang.ClassNotFoundException: org.apache.derby.jdbc.EmbeddedDriver
java.sql.SQLSyntaxErrorException: Schema 'DEMO' does not exist
Heres the main body of code i am trying to execute.
public class Main {
* @param args the command line arguments
public static void main(String[] args) {
// TODO code application logic here
try{
Class.forName("org.apache.derby.jdbc.EmbeddedDriver");
}catch(ClassNotFoundException e){
System.out.println(e);
try{
Connection con = DriverManager.getConnection("jdbc:derby://localhost:1527/SimpleDBDemo", "demo", "demo");
Statement stmt = con.createStatement();
ResultSet rs = stmt.executeQuery("SELECT * FROM DEMO.Table1");
while (rs.next()) {
String s = rs.getString("Name");
float n = rs.getFloat("Age");
System.out.println(s + " " + n);
}catch(SQLException e){
System.err.println(e);
I am using NetBeans IDE and have created a database under: Services->Databases-> Java DB->SimpleDBDemo.
I have a database connection in which theres a simple table (called "TABLE1") created which contains the names and ages of two people.
Hope this makes the problem a bit clearer.
Any help would be greatly appreciated. -
I am just starting to implement a new user login authentication process wherein after prompting user for username & password, I hope to authenticate them againts our company Active Directory user data. Since I am just starting, I only have very few things
done at this point which is how I wanted to work on this so that my development environment is still at its simplest state.
I am using the following for development:
MS-Visual Studios Professional 2013 Version 12.0.30501.00 Update 2, and
MS .NET Framework Version 4.5.50938.
Here are my project solution's current items:
Web.config:
<?xml version="1.0"?>
<!--
For more information on how to configure your ASP.NET application, please visit
http://go.microsoft.com/fwlink/?LinkId=169433
-->
<configuration>
<system.web>
<compilation debug="true" targetFramework="4.5" />
<httpRuntime targetFramework="4.5" />
</system.web>
<system.webServer>
<defaultDocument enabled="true">
<files>
<add value="Login.aspx" />
</files>
</defaultDocument>
</system.webServer>
</configuration>
Web.Debug.config:
<?xml version="1.0" encoding="utf-8"?>
<!-- For more information on using web.config transformation visit http://go.microsoft.com/fwlink/?LinkId=125889 -->
<configuration xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform">
<!--
In the example below, the "SetAttributes" transform will change the value of
"connectionString" to use "ReleaseSQLServer" only when the "Match" locator
finds an attribute "name" that has a value of "MyDB".
<connectionStrings>
<add name="MyDB"
connectionString="Data Source=ReleaseSQLServer;Initial Catalog=MyReleaseDB;Integrated Security=True"
xdt:Transform="SetAttributes" xdt:Locator="Match(name)"/>
</connectionStrings>
-->
<system.web>
<compilation xdt:Transform="RemoveAttributes(debug)" />
<!--
In the example below, the "Replace" transform will replace the entire
<customErrors> section of your web.config file.
Note that because there is only one customErrors section under the
<system.web> node, there is no need to use the "xdt:Locator" attribute.
<customErrors defaultRedirect="GenericError.htm"
mode="RemoteOnly" xdt:Transform="Replace">
<error statusCode="500" redirect="InternalError.htm"/>
</customErrors>
-->
</system.web>
</configuration>
Web.Assemblies.config:
<?xml version="1.0"?>
<configuration>
<system.web>
<compilation debug="false" targetFramework="4.5" />
<httpRuntime targetFramework="4.5" />
<assemblies>
<add assembly="System.DirectoryServices, Version=4.0.0.0, Culture=neutral PublicKeyToken=b03f5f7f11d50a3a"/>
</assemblies>
</system.web>
</configuration>
Login.aspx:
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Login.aspx.cs" Inherits="Login" %>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
</head>
<body>
<form id="form1" runat="server">
<div id="loginForm" style="height: 562px; width: 399px; margin-left: 0px" title="Login Form">
<asp:Label ID="loginPageLabel" runat="server" Font-Bold="True" Font-Names="Arial Black" Font-Size="Large" Text="Please Log In"></asp:Label>
<br />
<br />
<asp:Label ID="loginUsernameLabel" runat="server" Text="Username:"></asp:Label>
<asp:TextBox ID="loginUserNameTextBox" runat="server" OnTextChanged="loginUserNameTextBox_TextChanged" Width="213px" Wrap="False" AutoPostBack="True" TabIndex="1"></asp:TextBox>
<br />
<br />
<asp:Label ID="loginPasswordLabel" runat="server" Text="Password:"></asp:Label>
<asp:TextBox ID="loginPasswordTextBox" runat="server" OnTextChanged="loginPasswordTextBox_TextChanged" Width="212px" Wrap="False" AutoPostBack="True" TabIndex="2"></asp:TextBox>
<br />
<br />
<asp:RadioButton ID="loginUAradioButton" runat="server" Font-Bold="True" OnCheckedChanged="loginUAradioButton_CheckedChanged" Text="TUPSS Associate" AutoPostBack="True" TabIndex="3" />
<asp:RadioButton ID="loginAFradioButton" runat="server" Font-Bold="True" OnCheckedChanged="loginAFradioButton_CheckedChanged" Text="Area Franchisee" AutoPostBack="True" TabIndex="4" />
<br />
<br />
<br />
<asp:Button ID="loginSubmitButton" runat="server" Font-Bold="True" OnClick="loginSubmitButton_Click" Text="Log In" TabIndex="5" />
<asp:Button ID="loginCancelButton" runat="server" Font-Bold="True" OnClick="loginCancelButton_Click" Text="Cancel" TabIndex="6" />
<br />
<br />
<asp:Label ID="loginStatusInstructionLabel" runat="server" Text="Status/Instruction:"></asp:Label>
<br />
<asp:TextBox ID="loginStatusInstructionTextBox" runat="server" Height="230px" MaxLength="100" Rows="12" TextMode="MultiLine" Width="360px" EnableViewState="False" OnTextChanged="loginStatusInstructionTextBox_TextChanged" ReadOnly="True" TabIndex="-1"></asp:TextBox>
</div>
</form>
</body>
</html>
Login.aspx.cs:
using System;
using System.DirectoryServices;
public partial class Login : System.Web.UI.Page
private string uName; // user-entered username
private string pWord; // user-entered password
private int loginLoadCycles; // just keeping track of how many times Page_Load is called
protected void Page_Load(object sender, EventArgs e)
if (this.loginUserNameTextBox.Text == String.Empty &&
this.loginPasswordTextBox.Text == String.Empty &&
this.loginUAradioButton.Checked == false &&
this.loginAFradioButton.Checked == false)
this.loginInit();
this.setLoginVisibilityAndFocus();
this.loginLoadCycles += 1;
private void loginInit()
this.uName = String.Empty;
this.pWord = String.Empty;
this.loginLoadCycles = 0;
private void setLoginVisibilityAndFocus()
// Decide on whether or not the Login submit & cancel buttons should be enabled or not
if ( this.loginUserNameTextBox.Text == String.Empty ||
(this.loginUAradioButton.Checked == false && this.loginAFradioButton.Checked == false) )
this.loginSubmitButton.Enabled = false;
this.loginCancelButton.Enabled = false;
this.loginStatusInstructionTextBox.Text = "Please specify if you are a TUPSS Associate or an Area Franchisee by checking either the 'TUPSS Associate' or 'Area Franchisee' checkbox.";
else
this.loginSubmitButton.Enabled = true;
this.loginCancelButton.Enabled = true;
if (this.loginPasswordTextBox.Text == String.Empty)
this.loginStatusInstructionTextBox.Text = "Now that you have entered your username & type, please enter your password.";
else
this.loginStatusInstructionTextBox.Text = "When you are ready, please select either the Log In button to login, or the Cancel button to abort.";
if (this.loginUAradioButton.Checked == false && this.loginAFradioButton.Checked == false)
this.SetFocus(this.loginUAradioButton);
else if (this.loginUserNameTextBox.Text == String.Empty)
this.SetFocus(this.loginUserNameTextBox);
else if (this.loginPasswordTextBox.Text == String.Empty)
this.SetFocus(this.loginPasswordTextBox);
else
this.SetFocus(this.loginSubmitButton);
protected void loginUserNameTextBox_TextChanged(object sender, EventArgs e)
protected void loginPasswordTextBox_TextChanged(object sender, EventArgs e)
// For some reason, after specifying that the password entry box's textmode to 'Password' setting,
// the UI's password textbox is emptied
this.loginStatusInstructionTextBox.Text = "NOTICE:\nThis application is still under development.\n\n" +
"This is why the password you entered is visible. Once this portion of the application is ready, it will be masked.\n\n" +
"Also, still need to figure out why when changing this to Password entry mode to mask its entered data, password is getting reset.";
protected void loginSubmitButton_Click(object sender, EventArgs e)
this.loginLoadCycles = 0;
this.uName = this.loginUserNameTextBox.Text;
this.pWord = this.loginPasswordTextBox.Text;
if (this.loginUAradioButton.Checked == true && this.loginAFradioButton.Checked == false)
this.loginLADPauthenticate('U'); // authenticate UPS Associates against UPS Corp's Active Directory
else if (this.loginUAradioButton.Checked == false && this.loginAFradioButton.Checked == true)
this.loginLADPauthenticate('A'); // authenticate Area Franchisees against UPS Store's iNet Active Directory
else
// set colors to show that this is an error instead of a status message or instruction
this.loginStatusInstructionTextBox.Text = "ERROR: Cannot log in without specifying if you are an UPS Associate or an Area Franchisee!";
protected void loginCancelButton_Click(object sender, EventArgs e)
this.loginStatusInstructionTextBox.Text = "You have selected to cancel from logging in...";
// Still need to plan what to do when user cancels out of logging in. For now, just initialize class attributes
this.loginInit();
protected void loginUAradioButton_CheckedChanged(object sender, EventArgs e)
String msg = String.Empty;
if (this.loginUAradioButton.Checked == true)
this.loginAFradioButton.Checked = false;
msg = "Thanks for specifying that you are a TUPSS Associate. ";
if (this.loginUserNameTextBox.Text == String.Empty)
msg += "Now please specify your username.";
else if (this.loginPasswordTextBox.Text == String.Empty)
msg += "Now please enter your password.";
this.loginStatusInstructionTextBox.Text = msg;
protected void loginAFradioButton_CheckedChanged(object sender, EventArgs e)
String msg = String.Empty;
if (this.loginAFradioButton.Checked == true)
this.loginUAradioButton.Checked = false;
msg = "Thanks for specifying that you are an Area Franchisee. ";
if (this.loginUserNameTextBox.Text == String.Empty)
msg += "Now please specify your username.";
else if (this.loginPasswordTextBox.Text == String.Empty)
msg += "Now please enter your password.";
this.loginStatusInstructionTextBox.Text = msg;
private void loginLADPauthenticate(char whichActiveDirectory)
String msg = "Authenticating user '" + this.uName + "' with password '" + this.pWord + "' against ";
if (whichActiveDirectory == 'U')
msg += "UPS Corp's Active Directory...";
else if (whichActiveDirectory == 'A')
msg += "The UPS Store's Franchisee Active Directory...";
msg += "\n\nNOTICE:\nThis is still under development.\n\nAt this point, this application is supposed to do something else now but is not yet ready.";
this.loginStatusInstructionTextBox.Text = msg;
this.loginStatusInstructionTextBox.AutoPostBack = true;
// Authenticate using LDAP
protected void loginStatusInstructionTextBox_TextChanged(object sender, EventArgs e)
I confirmed that I have System.DirectoryServices.dll located in
C:\Windows\Microsoft.NET\assembly\GAC_MSIL\v4.0_4.0.0.0__b03f5f7f11d50a3a\ folder and that I as well as System have read as well as read&execute privileges
not only to all folders in its path but also to the DLL file itself.
I would appreciate any help in trying to resolve this compilation error so that I can proceed with implementing LDAP features for this endeavor.
Thanks so much,
hguico @ The UPS StoreHi,
For web application problem, please post your thread in
ASP.NET forum.
Best Wishes!
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. Thanks<br/> MSDN Community Support<br/> <br/> Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and
makes it easier for other visitors to find the resolution later. -
PL/SQL Procedure Compilation error
Hi,
<br><br>
I have wrote a PL/SQL Stored Procedure to read a couple of table values and then output some data to a file, when I create the procedure on the database I get the following compilation error:
<br><br>
LINE/COL ERROR<br>
-------- -----------------------------------------------------------------<br>
25/7 PLS-00103: Encountered the symbol ")" when expecting one of the<br>
following:<br>
( - + case mod new null <an identifier><br>
<a double-quoted delimited-identifier> <a bind variable> avg<br>
count current max min prior sql stddev sum variance execute<br>
forall merge time timestamp interval date<br>
<a string literal with character set specification>
<a number> <a single-quoted SQL string> pipe<br>
The symbol "null" was substituted for ")" to continue.<br>
<br>
The script is below: <br><br>
CREATE OR REPLACE <br>
PROCEDURE TDF_EXTRACT AS<br>
v_file UTL_FILE.FILE_TYPE;<br>
YEAR number(4);<br>
Q1_VALUE NUMBER(7);<br><br>
BEGIN<br><br>
SELECT PERSON_VALUE<br>
INTO Q1_VALUE<br>
FROM PERSON<br>
WHERE ID = 79;<br><br>
SELECT EXTRACT(YEAR FROM SYSDATE)<br>
INTO YEAR <br>
FROM DUAL;<br><br>
v_file := UTL_FILE.FOPEN(location => '/tmp',<br>
filename => 'extratced_values.txt',<br>
open_mode => 'W',<br>
max_linesize => 32767);<br><br>
UTL_FILE.PUT_LINE(v_file,<br>
'Q1' || YEAR || '23' || Q1_VALUE || '\r\n' ||<br>
);<br><br>
UTL_FILE.FCLOSE(v_file);<br><br>
END TDF_EXTRACT;'Q1' || YEAR || '23' || Q1_VALUE || '\r\n' ||
);Syntax error during concatenation, maybe?
C.
Message was edited by:
cd -
Can't Export Movie - Unknown Compile Error - Help!
I edited a 32 minute movie in Premiere Elements 10, and now I'm trying to export it. At some point during the export, and it seems to vary, I get an unknown compile error. I've been trying to export the movie for the past week and all I get is failure despite trying just about everything I've found written about how to solve this.
I have Win 7 Ultimate SP 1 running on a Lenovo desktop machine with an Intel Core 2 Quad CPU at 2.67 GHz, 4GB of RAM, 32 bit proc.
Premiere is installed on system C drive with 6 GB of free space.
Project and scrach disks are on D drive with 165 GB of free space.
Media files are on 2nd E drive with 50GB of free space.
Project and most source material is NTSC DV -- there are quite a few photos with motion, plus some iPhone HD video on the timeline, hundreds of clips in all plus narration, a few titles, etc.
Export destination folder is on D drive.
Everything will render to green lines atop timeline (sometimes it quits during render and I have to keep hitting Enter to continue rendering, but eventually it's all green)
So far I've tried:
- Reinstalling PE 10
- Reinstalling Quicktime
- Copying all the photos to their own separate folder
- Editing each photo slightly (outside of PE 10) and resaving to make sure none of the photos are corrupted
- Emptying the temp folder
- Deleting all the renders and cache files and letting them rebuild
- Exporting small pieces of the timeline to try to identify a bad clip -- this is a maddening process and I did find one clip that would generate the error, but I managed to export that to AVI and reimport and replace on timeline. It would be awfully nice if PE would just TELL ME which clip it doesn't like if in fact it's a clip error.
- Turning off the shadow / highlight feature I had on some clips, but this wasn't the issue, smaller sections with these clips exported fine
- Tried exporting to various formats: Vimeo SD, MPEG DV Standard, iPad Standard High Quality, AVI -- all result in the same error (the format I want by the way is Vimeo SD)
- Rebooting the machine and turning everything off that might possibly consume memory
This machine has never had problems exporting in the past. One thing I did try that worked -- installed PE 10 on another (less capable) Win 7 machine, and fed it all the media via an external drive. The other machine did the export fine (though it took a while given it is underpowered). This is nothing more than a work around though as I don't normally have access to this machine and I'm not done editing.
I'm at my wits' end! What else can I do to get this movie file to export?
Appreciate any help or clues you can provide to solve this mystery.Oh, that is tragic!
I never had any issues with mine. Maybe it knew how respectful I was, having come from manual rewinds and a sync block? The Moviola was a godsend, at least for me. I am glad that I got to edit film, and on many setups, as some of that translated well to digital Video. Back when I was in film school, Video was 2" tape, and the only editing was by cutting at a 45 degree angle, and splicing the tape. There was not even deck-to-deck editing, way back then. Also, Video looked like crap, at least to my eyes. We could only use a switcher, to "edit," or do a feed to air. Looked like crap!
As for the Lexus, I can imagine all sorts of problems. My new LX-570 requires me to "Accept," when I put it into reverse, on the rear-view monitor! At least my wife's MB does not require that, but it is a 2011 model, so maybe the 2013 models will require that the user sign off on all sorts of "stuff."
Now, I can play Finding Nemo, for my rear-seat passengers, while driving, but the front-seat passengers cannot see it, which is just fine. When driving, I am not even a fan of hands-free calls, and declined most of the streaming stock quotes, etc. for XM/Sirius radio. NOT while I am driving. I will save that for reading the WSJ in the club at the airport.
Some years ago, our driver in London got a new BMW 7-series, and it allowed the playing of DVD's, even in the front, while driving. Not sure that I would want that, but such is life. At least his seats' ventilation system was "well-chilled," where ours' are just air. He almost froze my bum, showing off his new auto.
Now, working with PS, or PrE in an auto, or even on a mobile device, is just not something that I can wrap my old head around. I want a fast computer, with a big display, and cannot imagine editing Images, or Video, on any handheld (or auto) device.
Hunt
Maybe you are looking for
-
Issue with opening PDF file...
Hi All, We are facing one issue in which when we try to open PDF file in the new window, it hangs up with a blank screen. Above functionalitiy is implemented in WebDynPro. On reviewing the logs we found few PDF related statements: 1. ComponentClassLo
-
Firefox no longer works for Yahoo comments
Firefox no longer works with the Yahoo News comments section. I am forced to use Internet Explorer for this purpose which is really irritating! Please fix this!!!
-
GL account marked for deletion
Hi , I am trying to do MIGO and I am getting this error "G/L account marked for deletion" . Pls help to reolve .
-
HT1926 This version of itunes is meant for 32bit windows not 64bit windows. Please download 64bit.
Ok so I have downloaded it on three different browsers and disabled popup blocker and restarted and this is still coming up with this version is meant for 32 bit windows, please download 64bit windows version. how do i fix this?
-
Hi, I'm working with JSP and want to include some EJB. I dont know how can I access EJB through JSP. I dont know if I use the right code in JSP for calling EJB. Did someone know how to use that? Can someone tell me if is the right code in JSP in my e