MailBoxList가 최상위 노드가 되고 하위에 MailBox들이 들어가는 형식으로

xsd 생성에 도전!!

MailBoxes.java
package com.idstrust.vicki; import java.util.ArrayList; import java.util.List; import javax.xml.bind.annotation.XmlAccessType; import javax.xml.bind.annotation.XmlAccessorType; import javax.xml.bind.annotation.XmlRootElement; import javax.xml.bind.annotation.XmlType; @XmlAccessorType(XmlAccessType.FIELD) @XmlType(name = "", propOrder = { "mailBox" }) @XmlRootElement(name = "mailBoxes") public class MailBoxes { private List<MailBox> mailBox; public List<MailBox> getMailBox() { if (mailBox == null) { mailBox = new ArrayList<MailBox>(); } return mailBox; } }
MailBox.java
package com.idstrust.vicki; import javax.xml.bind.annotation.XmlAccessType; import javax.xml.bind.annotation.XmlAccessorType; import javax.xml.bind.annotation.XmlElement; import javax.xml.bind.annotation.XmlRootElement; import javax.xml.bind.annotation.XmlType; @XmlAccessorType(XmlAccessType.FIELD) @XmlType(name = "", propOrder = { "id", "name", "parentId" }) @XmlRootElement(name = "mailBox") public class MailBox { @XmlElement private String id; @XmlElement private String name; @XmlElement private String parentId; public String getId() { return id; } public void setId(String id) { this.id = id; } public String getName() { return name; } public void setName(String name) { this.name = name; } public String getParentId() { return parentId; } public void setParentId(String parentId) { this.parentId = parentId; } }
build.xml
<?xml version="1.0" standalone="yes"?> <!-- Copyright 2004 Sun Microsystems, Inc. All rights reserved. --> <project basedir="." default="schemagen"> <taskdef name="schemagen" classname="com.sun.tools.jxc.SchemaGenTask"> <classpath> <fileset dir="./lib" includes="*.jar" /> </classpath> </taskdef> <property name="jaxb.home" value="." /> <property name="build.dir" value="build" /> <property name="schema.dir" value="build/schemas" /> <path id="classpath"> <pathelement path="src" /> <pathelement path="classes" /> <pathelement path="schemas" /> <fileset dir="${jaxb.home}" includes="lib/*.jar" /> </path> <target name="init"> <delete dir="${build.dir}" /> <mkdir dir="${build.dir}" /> <mkdir dir="${schema.dir}" /> </target> <target name="schemagen" depends="init"> <schemagen destdir="${schema.dir}"> <src path="src" /> <include name="com/idstrust/vicki/**/*.java" /> </schemagen> </target> </project>

ant를 실행시키면 다음과 같은 결과가 나오게됩니다.
init:
   [delete] Deleting directory E:\Development\workspaceNew\JAXBTest\build
    [mkdir] Created dir: E:\Development\workspaceNew\JAXBTest\build
    [mkdir] Created dir: E:\Development\workspaceNew\JAXBTest\build\schemas
schemagen:
[schemagen] Generating schema from 2 source files
[schemagen] Note: Writing schema1.xsd
BUILD SUCCESSFUL
Total time: 1 second

ant를 실행시킨 디렉토리를 확인하게 되면 schema1.xsd가 생성되었습니다.
schema1.xsd
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <xs:schema version="1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="mailBox"> <xs:complexType> <xs:sequence> <xs:element name="id" type="xs:string" minOccurs="0"/> <xs:element name="name" type="xs:string" minOccurs="0"/> <xs:element name="parentId" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="mailBoxes"> <xs:complexType> <xs:sequence> <xs:element name="mailBox" nillable="true" maxOccurs="unbounded" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="id" type="xs:string" minOccurs="0"/> <xs:element name="name" type="xs:string" minOccurs="0"/> <xs:element name="parentId" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>

블로그에 사진올려서 트랙백걸어 놓으면 선물준다는 말에 그만...
옥회장님 재치꾼~

이전다음

0123

signjar로 인증처리까지 했는데 저런 오류가 뜬다면...

이미 다른 인증이 있기 때문입니다.

예를 들어서 eclipse에 jface jar를 직접만든 프로젝트에서 웹스타트를 통해

배포한다면 문제가 발생할 것입니다.

해당 jar원본의 압축을 풀어서 META-INF 폴더를 보게되면

ECLIPSE.RSA와 ECLIPSE.SF 파일이 있는데 이걸 지우고 다시 jar로 묶은 후에

signjar로 인증처리를 하고 webstart로 올리면 문제가 해결될 것입니다~~

-------------
추가적으로... plugin 속성을 가지고 있는 것을 처리하려면 META-INF 폴더는 빼고

jar로 묶습니다.

Junction v1.05

By Mark Russinovich

Introduction

Windows 2000 and higher supports directory symbolic links, where a directory serves as a symbolic link to another directory on the computer. For example, if the directory D:\SYMLINK specified C:\WINNT\SYSTEM32 as its target, then an application accessing D:\SYMLINK\DRIVERS would in reality be accessing C:\WINNT\SYSTEM32\DRIVERS. Directory symbolic links are known as NTFS junctions in Windows. Unfortunately, Windows comes with no tools for creating junctions - you have to purchase the Win2K Resource Kit, which comes with the linkd program for creating junctions. I therefore decided to write my own junction-creating tool: Junction. Junction not only allows you to create NTFS junctions, it allows you to see if files or directories are actually reparse points. Reparse points are the mechanism on which NTFS junctions are based, and they are used by Windows' Remote Storage Service (RSS), as well as volume mount points.

Please read this Microsoft KB article for tips on using junctions.

Note that Windows does not support junctions to directories on remote shares.

If you want to view reparse information, the usage for Junction is the following:

Usage: junction [-s] <directory or file name>

-s

Recurse subdirectories.

If you want to create or delete a junction, use Junction like this:

Usage: junction [-d] <junction directory> [<junction target>]

To delete a junction specify the -d switch and the junction name.


원문:  http://www.microsoft.com/technet/sysinternals/FileAndDisk/Junction.mspx