From markcarl@sac.sfbay.sun.com Mon Apr 13 12:52:04 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3DJq3VM023351 for ; Mon, 13 Apr 2009 12:52:03 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3DJpweK008586; Mon, 13 Apr 2009 12:52:02 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KI200E051UPQT00@brm-avmta-1.central.sun.com>; Mon, 13 Apr 2009 13:52:01 -0600 (MDT) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KI200B8H1UPE920@brm-avmta-1.central.sun.com>; Mon, 13 Apr 2009 13:52:01 -0600 (MDT) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3DJpwSN055791; Mon, 13 Apr 2009 12:51:58 -0700 (PDT) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3DJpvs3023304; Mon, 13 Apr 2009 12:51:57 -0700 (PDT) Received: (from markcarl@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n3DJpvEC023300; Mon, 13 Apr 2009 12:51:57 -0700 (PDT) Date: Mon, 13 Apr 2009 12:51:57 -0700 (PDT) From: Mark Carlson Subject: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009] To: LSARC-ext@sun.com Cc: Arvind.Samptur@sun.com, Bharath.Madakatte@sun.com Message-id: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 2808 I am sponsoring this familiarity case for Bharath Kumar, requesting minor binding and timing out 04/20/2009. -- mark Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: JAXB 1.2. Name of Document Author/Supplier: Author: Bharath Kumar 1.3 Date of This Document: 13 April, 2009 2. Project Summary 2.1 Project Description This project introduces the package of Jaxb2.1 into the SFW consolidation. 4. Technical Description: Java Architecture for XML Binding (JAXB) provides an API and tool that allow automatic two-way mapping between XML documents and Java objects. With a given Document Type Definition (DTD) and a schema definition, the JAXB compiler can generate a set of Java classes that allow developers to build applications that can read, manipulate and recreate XML documents without writing any logic to process XML elements. 5. Interfaces Exported interfaces ------------------- Interface Name Classification Comments --------------------------- ---------------- --------------------------- SUNWJaxb Uncommitted Jaxb Package Jaxb API Uncommitted Jaxb Classes JSR ID 222 Committed Java Specification Requests /usr/share/lib/java/jaxb-impl.jar Uncommitted Jaxb runtime jar /usr/share/lib/java/jaxb1-impl.jar Uncommitted Jaxb runtime jar /usr/share/lib/java/jaxb-api.jar Uncommitted Jaxb runtime jar /usr/share/lib/java/jsr173_1.0_api.jar Uncommitted Jaxb runtime jar /usr/share/lib/java/jaxb-xjc.jar Uncommitted Jaxb compiler jar /usr/bin/schemagen.sh Uncommitted Jaxb schema generation script /usr/bin/xjc.sh Uncommitted Jaxb script to start xjc /usr/share/doc/jaxb uncommitted Jaxb doc directory /usr/share/man/man3/jaxb.3 Uncommitted Manpage 4.2 Imported Interfaces Interface Name Classification Comments ------------------------ ------------------ -------------------------- jdk1.5 committed Java Development Kit activation.jar Uncommitted JavaBeans Activation Framework JSr details are available here: http://jcp.org/en/jsr/detail?id=222 Javadocs are available here : https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From Danek.Duvall@sun.com Mon Apr 13 13:22:59 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3DKMvi0024444 for ; Mon, 13 Apr 2009 13:22:58 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3DKMsgR010242 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 14 Apr 2009 04:22:56 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KI200L013A6MA00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 13 Apr 2009 13:22:54 -0700 (PDT) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KI200DRQ3A6PCE0@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 13 Apr 2009 13:22:54 -0700 (PDT) Received: from mumak.SFBay.Sun.COM (mumak.SFBay.Sun.COM [129.146.229.4]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3DKMpdC009618; Mon, 13 Apr 2009 13:22:52 -0700 (PDT) Received: from mumak.SFBay.Sun.COM (loghost [127.0.0.1]) by mumak.SFBay.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n3DKPDH0009412; Mon, 13 Apr 2009 13:25:13 -0700 (PDT) Received: (from dduvall@localhost) by mumak.SFBay.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n3DKPDUY009411; Mon, 13 Apr 2009 13:25:13 -0700 (PDT) Date: Mon, 13 Apr 2009 13:25:13 -0700 From: Danek Duvall Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009] In-reply-to: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com> To: Mark Carlson Cc: LSARC-ext@sun.com, Arvind.Samptur@sun.com, Bharath.Madakatte@sun.com Message-id: <20090413202513.GU7978@mumak.SFBay.Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 2182 On Mon, Apr 13, 2009 at 12:51:57PM -0700, Mark Carlson wrote: > Java Architecture for XML Binding (JAXB) provides an API and tool > that allow automatic two-way mapping between XML documents and > Java objects. With a given Document Type Definition (DTD) and a > schema definition, the JAXB compiler can generate a set of Java > classes that allow developers to build applications that can read, > manipulate and recreate XML documents without writing any logic to > process XML elements. Are there plans for Cacao and Sun Connection Network (to name the two that are in the Solaris WOS) to switch to using this JAXB, rather than continue using their own copies? Looks like netbeans has a copy as well. > 5. Interfaces > > Exported interfaces > ------------------- > Interface Name Classification Comments > --------------------------- ---------------- --------------------------- > SUNWJaxb Uncommitted Jaxb Package The capital J is a bit jarring (so to speak). Was "SUNWjaxb" already taken? > Jaxb API Uncommitted Jaxb Classes > JSR ID 222 Committed Java Specification Requests > /usr/share/lib/java/jaxb-impl.jar Uncommitted Jaxb runtime jar > /usr/share/lib/java/jaxb1-impl.jar Uncommitted Jaxb runtime jar One of these two is a symlink to the other? > /usr/share/lib/java/jaxb-api.jar Uncommitted Jaxb runtime jar > /usr/share/lib/java/jsr173_1.0_api.jar Uncommitted Jaxb runtime jar Ditto here? > /usr/share/lib/java/jaxb-xjc.jar Uncommitted Jaxb compiler jar > /usr/bin/schemagen.sh Uncommitted Jaxb schema generation script > /usr/bin/xjc.sh Uncommitted Jaxb script to start xjc No ".sh" extensions in /usr/bin. > /usr/share/doc/jaxb uncommitted Jaxb doc directory > /usr/share/man/man3/jaxb.3 Uncommitted Manpage Man pages for xjc and schemagen? Are they documented in jaxb(3)? Danek From John.Fischer@sun.com Mon Apr 13 13:23:46 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3DKNjJq024489 for ; Mon, 13 Apr 2009 13:23:45 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3DKNixp034915 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 13 Apr 2009 14:23:45 -0600 (MDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KI200H033BLWN00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 13 Apr 2009 14:23:45 -0600 (MDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KI200B1N3BLE740@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 13 Apr 2009 14:23:45 -0600 (MDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3DKNiwO003609 for ; Mon, 13 Apr 2009 20:23:44 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KI200G0032HVQ00@mail-amer.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 13 Apr 2009 14:23:44 -0600 (MDT) Received: from [192.168.10.7] ([unknown] [76.20.56.47]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KI200AYY3BCYL90@mail-amer.sun.com>; Mon, 13 Apr 2009 14:23:36 -0600 (MDT) Date: Mon, 13 Apr 2009 13:22:39 -0700 From: John Fischer Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009] In-reply-to: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com> Sender: John.Fischer@sun.com To: Mark Carlson Cc: LSARC-ext@sun.com, Arvind.Samptur@sun.com, Bharath.Madakatte@sun.com Reply-to: John.Fischer@sun.com Message-id: <49E39F0F.8020201@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090323) Status: RO Content-Length: 3328 Bharath, Will there be man pages provided for these 2 new /usr/bin commands? schemagen.sh seems a little to generic for my tastes. Is this name dictated by the JSR specification? If not perhaps changing the name to xjc-schemagen.sh might be better. Thanks, John Mark Carlson wrote: > I am sponsoring this familiarity case for Bharath Kumar, requesting minor binding and timing out 04/20/2009. > > -- mark > > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > JAXB > 1.2. Name of Document Author/Supplier: > Author: Bharath Kumar > 1.3 Date of This Document: > 13 April, 2009 > > 2. Project Summary > 2.1 Project Description > This project introduces the package of Jaxb2.1 into the SFW consolidation. > > 4. Technical Description: > Java Architecture for XML Binding (JAXB) provides an API and tool that allow automatic two-way mapping between XML documents and Java objects. With a given Document Type Definition (DTD) and a schema definition, the JAXB compiler can generate a set of Java classes that allow developers to build applications that can read, manipulate and recreate XML documents without writing any logic to process XML elements. > > 5. Interfaces > > Exported interfaces > ------------------- > Interface Name Classification Comments > --------------------------- ---------------- --------------------------- > SUNWJaxb Uncommitted Jaxb Package > Jaxb API Uncommitted Jaxb Classes > JSR ID 222 Committed Java Specification Requests > /usr/share/lib/java/jaxb-impl.jar Uncommitted Jaxb runtime jar > /usr/share/lib/java/jaxb1-impl.jar Uncommitted Jaxb runtime jar > /usr/share/lib/java/jaxb-api.jar Uncommitted Jaxb runtime jar > /usr/share/lib/java/jsr173_1.0_api.jar Uncommitted Jaxb runtime jar > /usr/share/lib/java/jaxb-xjc.jar Uncommitted Jaxb compiler jar > /usr/bin/schemagen.sh Uncommitted Jaxb schema generation script > /usr/bin/xjc.sh Uncommitted Jaxb script to start xjc > /usr/share/doc/jaxb uncommitted Jaxb doc directory > /usr/share/man/man3/jaxb.3 Uncommitted Manpage > > 4.2 Imported Interfaces > Interface Name Classification Comments > ------------------------ ------------------ -------------------------- > jdk1.5 committed Java Development Kit > activation.jar Uncommitted JavaBeans Activation Framework > > JSr details are available here: > http://jcp.org/en/jsr/detail?id=222 > Javadocs are available here : > https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > SFW > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc@opensolaris.org From carlsonj@phorcys.east.sun.com Mon Apr 13 13:32:38 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3DKWcvH024695 for ; Mon, 13 Apr 2009 13:32:38 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3DKWbat026814 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@Sun.COM>; Mon, 13 Apr 2009 13:32:37 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KI200M0B3QBW400@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Mon, 13 Apr 2009 13:32:35 -0700 (PDT) Received: from dm-east-01.east.sun.com ([129.148.9.192]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KI200LGZ3QBT710@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Mon, 13 Apr 2009 13:32:35 -0700 (PDT) Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143]) by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3DKWVWq053446; Mon, 13 Apr 2009 16:32:31 -0400 (EDT) Received: from phorcys.east.sun.com (phorcys.local [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n3DKW3LS011620; Mon, 13 Apr 2009 16:32:03 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n3DKW3we011617; Mon, 13 Apr 2009 16:32:03 -0400 (EDT) Date: Mon, 13 Apr 2009 16:32:03 -0400 From: James Carlson Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009] In-reply-to: <49E39F0F.8020201@sun.com> To: John.Fischer@sun.com Cc: Mark Carlson , Arvind.Samptur@sun.com, Bharath.Madakatte@sun.com, LSARC-ext@sun.com Message-id: <18915.41283.448431.848127@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com> <49E39F0F.8020201@sun.com> Status: RO Content-Length: 596 John Fischer writes: > Will there be man pages provided for these 2 new /usr/bin commands? > schemagen.sh seems a little to generic for my tastes. Is this name > dictated by the JSR specification? If not perhaps changing the name > to xjc-schemagen.sh might be better. Ew. Does the implementation language have to leak through to the user interface like that (".sh")? -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Bharath.Madakatte@sun.com Tue Apr 14 02:15:46 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3E9FkHI004662 for ; Tue, 14 Apr 2009 02:15:46 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3E9Fhd3016987 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 14 Apr 2009 02:15:46 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KI300H07328DJ00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Tue, 14 Apr 2009 02:15:44 -0700 (PDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KI300AOH326QWC0@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Tue, 14 Apr 2009 02:15:43 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3E9Fgwa027511 for ; Tue, 14 Apr 2009 09:15:42 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KI300D002ZZP800@mail-amer.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Tue, 14 Apr 2009 03:15:42 -0600 (MDT) Received: from [10.114.58.92] ([unknown] [203.91.196.62]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KI300GP3320WC80@mail-amer.sun.com>; Tue, 14 Apr 2009 03:15:41 -0600 (MDT) Date: Tue, 14 Apr 2009 14:45:48 +0530 From: Bharath Kumar Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009] In-reply-to: <18915.41283.448431.848127@gargle.gargle.HOWL> Sender: Bharath.Madakatte@sun.com To: LSARC-ext@sun.com Cc: Mark Carlson , Arvind.Samptur@sun.com, John.Fischer@sun.com, Danek.Duvall@sun.com, Bharath.Madakatte@sun.com Reply-to: Bharath.Madakatte@sun.com Message-id: <49E45444.20907@Sun.Com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_Mf9zJsSDrv+McFDwD2FX/A)" X-PMX-Version: 5.4.1.325704 References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com> <49E39F0F.8020201@sun.com> <18915.41283.448431.848127@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) Status: RO Content-Length: 29362 This is a multi-part message in MIME format. --Boundary_(ID_Mf9zJsSDrv+McFDwD2FX/A) Content-type: multipart/alternative; boundary="Boundary_(ID_h13uE0SUjuaX58S3qEwHtw)" --Boundary_(ID_h13uE0SUjuaX58S3qEwHtw) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Hi, Please see comments in-lined. Danek Duvall wrote: > On Mon, Apr 13, 2009 at 12:51:57PM -0700, Mark Carlson wrote: > > >> Java Architecture for XML Binding (JAXB) provides an API and tool >> that allow automatic two-way mapping between XML documents and >> Java objects. With a given Document Type Definition (DTD) and a >> schema definition, the JAXB compiler can generate a set of Java >> classes that allow developers to build applications that can read, >> manipulate and recreate XML documents without writing any logic to >> process XML elements. >> > > Are there plans for Cacao and Sun Connection Network (to name the two that > are in the Solaris WOS) to switch to using this JAXB, rather than continue > using their own copies? Looks like netbeans has a copy as well. > > I would let Mark answer this question. >> 5. Interfaces >> >> Exported interfaces >> ------------------- >> Interface Name Classification Comments >> --------------------------- ---------------- --------------------------- >> SUNWJaxb Uncommitted Jaxb Package >> > > The capital J is a bit jarring (so to speak). Was "SUNWjaxb" already > taken? > > I have changed the package name to SUNWjaxb. >> Jaxb API Uncommitted Jaxb Classes >> JSR ID 222 Committed Java Specification Requests >> /usr/share/lib/java/jaxb-impl.jar Uncommitted Jaxb runtime jar >> /usr/share/lib/java/jaxb1-impl.jar Uncommitted Jaxb runtime jar >> > > One of these two is a symlink to the other? > > >> /usr/share/lib/java/jaxb-api.jar Uncommitted Jaxb runtime jar >> /usr/share/lib/java/jsr173_1.0_api.jar Uncommitted Jaxb runtime jar >> > > Ditto here? > > No they are separate jars. The jaxb1-impl.jar is used by older applications that used earlier versions of JAXB. For 2.x runtime, Jars required to deploy a JAXB 2.x client are jaxb-api.jar, jaxb-impl.jar, jsr173_1.0_api.jar For 1.x runtime, Jars required to deploy an older JAXB 1.0 client are 2.x Runtime + jaxb1-impl.jar Explanations about jars are also at: https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html. >> /usr/share/lib/java/jaxb-xjc.jar Uncommitted Jaxb compiler jar >> /usr/bin/schemagen.sh Uncommitted Jaxb schema generation script >> /usr/bin/xjc.sh Uncommitted Jaxb script to start xjc >> > > No ".sh" extensions in /usr/bin. I have modified them to be installed in /opt/SUNWjaxb/bin. John Fischer wrote: > Bharath, > > Will there be man pages provided for these 2 new /usr/bin commands? I have updated the manpage with details on scripts and pointer to https://jaxb.dev.java.net/nonav/2.1.10/docs/ Detailed help is available in the form of javadocs(html pages). They will be installed at /usr/share/doc/jaxb/ . > schemagen.sh seems a little to generic for my tastes. Is this name > dictated by the JSR specification? If not perhaps changing the name > to xjc-schemagen.sh might be better. Yes these names are dictated by JSR specifications. Attached are the updated ARC doc, FOSS checklist and manpage. Thanks Bharath --Boundary_(ID_h13uE0SUjuaX58S3qEwHtw) Content-type: text/html; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Hi,

Please see comments in-lined.

Danek Duvall wrote: 
On Mon, Apr 13, 2009 at 12:51:57PM -0700, Mark Carlson wrote:

  
	 Java Architecture for XML Binding (JAXB) provides an API and tool
	 that allow automatic two-way mapping between XML documents and
	 Java objects. With a given Document Type Definition (DTD) and a
	 schema definition, the JAXB compiler can generate a set of Java
	 classes that allow developers to build applications that can read,
	 manipulate and recreate XML documents without writing any logic to
	 process XML elements.
    

Are there plans for Cacao and Sun Connection Network (to name the two that
are in the Solaris WOS) to switch to using this JAXB, rather than continue
using their own copies?  Looks like netbeans has a copy as well.

I would let Mark answer this question.

5. Interfaces

   Exported interfaces
   -------------------
    Interface Name				Classification      	Comments
    --------------------------- 		----------------	---------------------------
    SUNWJaxb                                    Uncommitted     	Jaxb Package
    

The capital J is a bit jarring (so to speak).  Was "SUNWjaxb" already
taken?

I have changed the package name to SUNWjaxb.

    Jaxb API    		   		Uncommitted	    	Jaxb Classes
    JSR ID 222                                  Committed               Java Specification Requests
    /usr/share/lib/java/jaxb-impl.jar         	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jaxb1-impl.jar         	Uncommitted   	   	Jaxb runtime jar
    

One of these two is a symlink to the other?

  
    /usr/share/lib/java/jaxb-api.jar         	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jsr173_1.0_api.jar     	Uncommitted   	   	Jaxb runtime jar
    

Ditto here?

  

No they are separate jars. The jaxb1-impl.jar is used by older applications that used earlier versions of JAXB.
For 2.x runtime, Jars required to deploy a JAXB 2.x client are jaxb-api.jar, jaxb-impl.jar, jsr173_1.0_api.jar
For 1.x runtime, Jars required to deploy an older JAXB 1.0 client are 2.x Runtime + jaxb1-impl.jar

Explanations about jars are also at: https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html. 


    /usr/share/lib/java/jaxb-xjc.jar         	Uncommitted   	   	Jaxb compiler jar
    /usr/bin/schemagen.sh            	        Uncommitted   	   	Jaxb schema generation script
    /usr/bin/xjc.sh         	                Uncommitted   	   	Jaxb script to start xjc
    

No ".sh" extensions in /usr/bin.

I have modified them to be installed in /opt/SUNWjaxb/bin.

John Fischer wrote:
Bharath,

Will there be man pages provided for these 2 new /usr/bin commands?
I have updated the manpage with details on scripts and pointer to https://jaxb.dev.java.net/nonav/2.1.10/docs/
Detailed help is available in the form of javadocs(html pages). They will be installed at /usr/share/doc/jaxb/ .
schemagen.sh seems a little to generic for my tastes.  Is this name
dictated by the JSR specification?  If not perhaps changing the name
to xjc-schemagen.sh might be better.

Yes these names are dictated by JSR specifications.

Attached are the updated ARC doc, FOSS checklist and manpage.

Thanks
Bharath




--Boundary_(ID_h13uE0SUjuaX58S3qEwHtw)--

--Boundary_(ID_Mf9zJsSDrv+McFDwD2FX/A)
Content-type: text/plain; name=jaxb.3
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=jaxb.3

'\" t
.\"
.\" CDDL HEADER START
.\"
.\" The contents of this file are subject to the terms of the
.\" Common Development and Distribution License (the "License").
.\" You may not use this file except in compliance with the License.
.\"
.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
.\" or http://www.opensolaris.org/os/licensing.
.\" See the License for the specific language governing permissions
.\" and limitations under the License.
.\"
.\" When distributing Covered Code, include this CDDL HEADER in each
.\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
.\" If applicable, add the following below this CDDL HEADER, with the
.\" fields enclosed by brackets "[]" replaced with your own identifying
.\" information: Portions Copyright [yyyy] [name of copyright owner]
.\"
.\" CDDL HEADER END
.\"
.\" Copyright 2009 Sun Microsystems, Inc.  All rights reserved.
.\" Use is subject to license terms.
.\"
.\" ident	"@(#)jaxb.3	1.1	09/04/13 SMI"
.\"
.TH "jaxb" "3" "" "" ""
.SH NAME
jaxb - Java Architecture for XML Binding is a standard extension to the Java platform.
.SH SYNOPSIS
.B Add relevant jaxb jar to the classpath.

.SH DESCRIPTION
JAXB is an acronym derived from Java Architecture for XML Binding. It constitutes a convenient framework for processing XML documents, providing significant benefits as compared to previously available methods such as the one following the Document Object Model (DOM).In the DOM approach, the parser creates a tree of objects that represents the content and organization of data in the document. The application can then navigate through the tree in memory to access the data it needs. DOM data, however, is contained in objects of a single type, linked according to the XML document's structure, with individual node objects containing an element, an attribute, a CDATA section, etc. Values are invariably provided as strings.JAXB provides a convenient way to process XML content using Java objects by binding its XML schema to Java representation.
.PP
For more details about Java Architecture for XML Binding(JAXB), please see
.br
.B https://jaxb.dev.java.net web page.

.SH FILES
By default, all jaxb jars  are installed into /usr/share/lib/java directory.
For more details about jars installed by jaxb, please see
.br
.B https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html

The XML binding compiler can be launched using the xjc shell script in the bin directory /opt/SUNWjaxb/bin
.br
The schema generator can be launched using the schemagen shell script in the bin directory /opt/SUNWjaxb/bin
.br
For more details on using the scripts, please see
.br
.B  https://jaxb.dev.java.net/nonav/2.1.10/docs

HTML-based documentation is located in jaxb's doc directory, /usr/share/doc/jaxb.

.SH ENVIRONMENT
JAVA_HOME variable must point to the directory where Java is installed.

.RE
.SH ATTRIBUTES
See
.BR attributes (5)
for descriptions of the following attributes:
.sp
.TS
box;
cbp-1 | cbp-1
l | l .
ATTRIBUTE TYPE	ATTRIBUTE VALUE
=
Availability	SUNWjaxb
=
Interface Stability	Uncommitted
.TE
.PP
.SH NOTES
Source for jaxb is available on http://opensolaris.org.


--Boundary_(ID_Mf9zJsSDrv+McFDwD2FX/A)
Content-type: text/plain; name=jaxb-Arc.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=jaxb-Arc.txt

1. Introduction
   1.1. Project/Component Working Name:
        Jaxb

   1.2. Name of Document Author/Supplier:
        Author: Bharath Kumar

   1.3. Date of This Document:
        02 April 2009

2. Project Summary
   2.1 Project Description
       This project introduces the package of Jaxb2.1 into the SFW consolidation.

4. Technical Description:
	 Java Architecture for XML Binding (JAXB) provides an API and tool that allow automatic two-way mapping between XML documents and Java objects. With a given Document Type Definition (DTD) and a schema definition, the JAXB compiler can generate a set of Java classes that allow developers to build applications that can read, manipulate and recreate XML documents without writing any logic to process XML elements.

5. Interfaces

   Exported interfaces
   -------------------
    Interface Name				Classification      	Comments
    --------------------------- 		----------------	---------------------------
    SUNWjaxb                                    Uncommitted     	Jaxb Package
    Jaxb API    		   		Uncommitted	    	Jaxb Classes
    JSR ID 222                                  Committed               Java Specification Requests
    /usr/share/lib/java/jaxb-impl.jar         	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jaxb1-impl.jar         	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jaxb-api.jar         	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jsr173_1.0_api.jar     	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jaxb-xjc.jar         	Uncommitted   	   	Jaxb compiler jar
    /opt/SUNWjaxb/bin/schemagen.sh    	        Uncommitted   	   	Jaxb schema generation script
    /opt/SUNWjaxb/bin/xjc.sh                    Uncommitted   	   	Jaxb script to start xjc
    /usr/share/doc/jaxb  	   		uncommitted             Jaxb doc directory
    /usr/share/man/man3/jaxb.3                  Uncommitted             Manpage
    
  4.2 Imported Interfaces
    Interface Name		Classification       	Comments
    ------------------------    ------------------  	--------------------------
    jdk1.5 	                committed		Java Development Kit
    activation.jar              Uncommitted		JavaBeans Activation Framework

    JSr details are available here: 
		http://jcp.org/en/jsr/detail?id=222
    Details about jaxb jars are available here:
		https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html
    Javadocs are available here : 
		https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html

6. Resources and Schedule:
   6.4. Product Approval Committee requested information:
   	6.4.1. Consolidation or Component Name:
	       SFW
   6.5. ARC review type: Automatic

   6.6. ARC Exposure: open

--Boundary_(ID_Mf9zJsSDrv+McFDwD2FX/A)
Content-type: text/plain; name=jaxb-FOSS.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=jaxb-FOSS.txt

FCL--FOSS Check List
1.0 Project Information
1.1 Name of project/component
    Jaxb

1.2 Author of document
    Bharath Kumar Madakatte

2.0 Project Summary
  2.1 Project Description
	 Java Architecture for XML Binding (JAXB) provides an API and tool that allow automatic two-way mapping between XML documents and Java objects. With a given Document Type Definition (DTD) and a schema definition, the JAXB compiler can generate a set of Java classes that allow developers to build applications that can read, manipulate and recreate XML documents without writing any logic to process XML elements.  

  2.2 Release binding
      What is is the release binding?
      (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
      [ ] Major
      [X] Minor
      [ ] Patch or Micro
      [ ] Unknown -- ARC review required

  2.3 Type of project
      Is this case a Linux Familiarity project?
      [X] Yes
      [ ] No

  2.4 Originating Community
    2.4.1 Community Name
          https://jaxb.dev.java.net/
    2.4.2 Community Involvement
      Indicate Sun's involvement in the community
      [ ] Maintainer
      [ ] Contributor
      [X] Monitoring
      
      Will the project team work with the upstream community to resolve
      architectural issues of interest to Sun?
      [X] Yes 
      [ ] No - briefly explain
      
      Will we or are we forking from the community?
      [ ] Yes - ARC review required prior to forking
      [X] No
      
3.0 Technical Description
  3.1 Installation & Sharable
    3.1.1S Solaris Installation - section only required for Solaris Software
      (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details)
      Does this project follow the Install Locations best practice?
      [X] Yes 
      [ ] No - ARC review required
      
      Does this project install into /usr under [sbin|bin|lib|include|man|share]?
      [X] Yes
      [ ] No or N/A
      
      Does this project install into /opt?
      [ ] Yes - explain below
      [X] No or N/A
      
      Does this project install into a different directory structure?
      [ ] Yes - ARC review required
      [X] No or N/A
      
      Do any of the components of this project conflict with anything under /usr?
      (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details)
      [ ] Yes - explain below
      [X] No
      
      If conflicts exist then will this project install under /usr/gnu?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
      
      Is this project installing into /usr/sfw?
      [ ] Yes - ARC review required
      [X] No
      
    3.1.1W Windows Installation - section only required for Windows Software
      (see http://sac.sfbay/WSARC/2002/494 for details)
      Does this project install software into a 
      :\Program Files\Sun\ or :\Sun\
      directory?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use the Windows registry?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use 
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\
      for the registry key?
      [ ] Yes
      [ ] No - ARC review required
      
      Is the project's stored location
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path?
      [ ] Yes
      [ ] No - ARC review required
      
    3.1.2 Share and Sharable
      Does the module include any components that are used or shared by 
      other projects?
      [ ] Yes
      [X] No
    
      If yes are these components packaged to be shared with the other FOSS?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
    
      Are these components already in the Solaris WOS?
      [ ] Yes
      [X] No - continue with next section (section 3.2)
    
      If yes are these newer versions being delivered?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes are the newer versions replacing the existing versions?
      [ ] Yes
      [ ] No - ARC review required

  3.2 Exported Libraries
      Are libraries being delivered by this project?
      [X] Yes
      [ ] No - continue with next section (section 3.3)
      
      Are 64-bit versions of the libraries being delivered?
      [X] Yes
      [ ] No - ARC review required 
          Since these are Java jar libraries, there are no separate 64 bit jars.
    
      Are static versions of the libraries being delivered?
      [ ] Yes - ARC review required
      [X] No 
      
  3.3 Services and the /etc Directory
      (see http://opensolaris.org/os/community/arc/policies/SMF-policy/)
      Does the project integrate anything into /etc/init.d or /etc/rc?.d?
      [ ] Yes - ARC review required
      [X] No
      
      Does the project integrate any new entries into /etc/inittab or
      /etc/inetd.conf?
      [ ] Yes - ARC review required
      [X] No
      
      Does the project integrate any private non-public files into /etc/default
      or /etc/ configuration files?
      [ ] Yes - ARC review required
      [X] No
      
      Does the service manifests method context grant rights above that
      of the noaccess user and basic privilege set?
      [ ] Yes - ARC review required
      [X] No
        
  3.4 Security
    3.4.1 Secure By Default 
      (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details)
      (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details)
      (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for
       addtional details)
      Are there any network services provided by this project?
      [ ] Yes
      [X] No - continue with the next section (section 3.4.2)
      
      Are network services enabled by default?
      [ ] Yes - ARC review required
      [ ] No
      [ ] N/A
      
      Are network services automatically enabled by the project during installation?
      [ ] Yes - ARC review required
      [ ] No
      [ ] N/A
      
      Are inbound network communications denied by default?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is inbound data checked to prevent content-based attacks?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is the outbound receiver authenticated?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is the receiver authenticated prior to receiving any sensitive outbound communication?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
    3.4.2 Authorization
      (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/
           for details)
      Are there any setuid/setgid privileged binaries in the project?
      [ ] Yes - ARC review required
      [X] No - continue with next section (section 3.4.3)
      
      If yes then are the setuid/setgid privileges handled by the use of roles?
      [ ] Yes
      [ ] No - ARC review required

    3.4.3 Auditing
      (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details)
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Does this component contain administrative or security enforcing software?
      [ ] Yes - ARC review required
      [X] No - continue to next section (section 3.4.4)
      
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Do the components create audit logs detailing what took place including what event
      took place, who was involved, when the event took place?
      [ ] Yes - ARC contract and Audit project team review required
      [ ] No - ARC review required
        
        
    3.4.4 Authentication
      (see http://opensolaris.org/os/community/arc/policies/PAM/)
      Do the components contain any authentication code?
      [ ] Yes
      [X] No - continue to next section (section 3.4.5)
      
      If yes do the components use PAM (plugable authentication modules) for authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes is a single PAM session maintained during authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes are the components sufficiently privileged to allow the requested 
      operations (authentication, password change, process credential manipulation, 
      audit state initialization)?
      [ ] Yes - briefly describe below
      [ ] No - ARC review required
      
    3.4.5 Passwords
      (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and
           http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details)
      Do any of the components for the project deal with passwords?
      [ ] Yes
      [X] No - continue to next section (section 3.4.6)
      
      If yes are these passwords entered via the CLI or environment?
      [ ] Yes - ARC review required
      [ ] No
      
      Are passwords stored within the file system for the component?
      [ ] Yes
      [ ] No - continue to next section (section 3.4.6)
      
      If yes are the permissions on the file such to protect exposing the password(s)?
      [ ] Yes
      [ ] No - ARC review required
      
    3.4.6 General Security Questions
      (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details)
      Are there any network protocols used by this project?
      [ ] Yes
      [X] No - continue with the next section (section 3.5)
      
      Do the components use standard network protocols?
      [ ] Yes
      [ ] No - ARC review required
      
      Do network services for the project make decisions based upon user, host or 
      service identities?
      [ ] Yes - explain below
      [ ] No
      [ ] N/A
      
      Do the components make use of secret information during authentication and/or
      authorization?
      [ ] Yes - explain below
      [ ] No
      [ ] N/A
  
  3.5 Networking
      Do the components access the network?
      [ ] Yes
      [X] No - continue with the next section (section 3.6)
      
      If yes do the components support IPv6?
      [ ] Yes 
      [ ] No - ARC review required
          
  3.6 Core Solaris Components
      Do the components of this project compete with or duplicate core 
      Solaris components?
      [ ] Yes - ARC review required
      [X] No 
      
      Examples of Core Solaris Components include but are not limited to:
      
        Secure By Default
        Authorizations
        PAM -- Plugable Authentication Module
        Privilege
        PRM -- Process Rights Management -- Privilege
        Audit
        xVm -- Virtualization
        zones / Solaris Containers
        PRM -- Process Rights Management
        RBAC -- Role Based Access Control
        TX / Trusted Extensions
        ZFS
        SMF -- Service Management Facility
        FMA -- Fault Management Architecture
        SCF -- Smart Card Facility
        IPsec
        
4.0 Interfaces
  
	See project proposal.
        Javadocs are here:
		https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html

--Boundary_(ID_Mf9zJsSDrv+McFDwD2FX/A)
Content-type: text/plain; name=jaxbmanpage.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=jaxbmanpage.txt

Introduction to Library Functions                         jaxb(3)

NAME
     jaxb - Java Architecture  for  XML  Binding  is  a  standard
     extension to the Java platform.

SYNOPSIS
     Add relevant jaxb jar to the classpath

DESCRIPTION
     JAXB is an acronym derived from Java  Architecture  for  XML
     Binding.  It constitutes a convenient framework for process-
     ing XML documents, providing significant  benefits  as  com-
     pared  to  previously available methods such as the one fol-
     lowing the Document Object Model (DOM).In the DOM  approach,
     the  parser  creates  a  tree of objects that represents the
     content and organization of data in the document. The appli-
     cation  can  then  navigate  through  the  tree in memory to
     access the data it needs. DOM data, however, is contained in
     objects  of  a  single  type,  linked  according  to the XML
     document's structure, with individual node objects  contain-
     ing  an  element, an attribute, a CDATA section, etc. Values
     are invariably provided  as  strings.JAXB  provides  a  con-
     venient  way  to  process  XML content using Java objects by
     binding its XML schema to Java representation.

     For  more  details   about   Java   Architecture   for   XML
     Binding(JAXB), please see
     https://jaxb.dev.java.net web page.

FILES
     By   default,   all   jaxb   jars    are   installed    into
     /usr/share/lib/java  directory.  For more details about jars
     installed by jaxb, please see
     https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html

     The XML binding compiler can be launched using the xjc shell
     script in the bin directory /opt/SUNWjaxb/bin
     The schema generator can be  launched  using  the  schemagen
     shell script in the bin directory /opt/SUNWjaxb/bin
     For more details on using the scripts, please see
     https://jaxb.dev.java.net/nonav/2.1.10/docs

     HTML-based documentation is located in jaxb's doc directory,
     /usr/share/doc/jaxb.

ENVIRONMENT
     JAVA_HOME variable must point to the directory where Java is
     installed.

SunOS 5.10                Last change:                          1

Introduction to Library Functions                         jaxb(3)

ATTRIBUTES
     See attributes(5) for descriptions of the  following  attri-
     butes:

     _______________________________________
    |   ATTRIBUTE TYPE   |  ATTRIBUTE VALUE|
    |____________________|_________________|
    | Availability       |  SUNWjaxb       |
    |____________________|_________________|
    | Interface Stability|  Uncommitted    |
    |____________________|_________________|

NOTES
     Source for jaxb is available on http://opensolaris.org.

SunOS 5.10                Last change:                          2

--Boundary_(ID_Mf9zJsSDrv+McFDwD2FX/A)--

From danek.duvall@sun.com Tue Apr 14 08:26:25 2009
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3EFQO2U002566
	for ; Tue, 14 Apr 2009 08:26:24 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3EFQMoT048357
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 14 Apr 2009 09:26:24 -0600 (MDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI300903K7ZTC00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 14 Apr 2009 08:26:23 -0700 (PDT)
Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI30041VK7YNHA0@nwk-avmta-1.sfbay.Sun.COM> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 14 Apr 2009 08:26:22 -0700 (PDT)
Received: from mumak.SFBay.Sun.COM (mumak.SFBay.Sun.COM [129.146.229.4])
	by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id n3EFQKDx002474; Tue, 14 Apr 2009 08:26:20 -0700 (PDT)
Received: from mumak.SFBay.Sun.COM (loghost [127.0.0.1])
	by mumak.SFBay.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n3EFSgnS002369; Tue,
 14 Apr 2009 08:28:42 -0700 (PDT)
Received: (from dduvall@localhost)
	by mumak.SFBay.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n3EFSgaJ002368; Tue,
 14 Apr 2009 08:28:42 -0700 (PDT)
Date: Tue, 14 Apr 2009 08:28:42 -0700
From: Danek Duvall 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <49E45444.20907@Sun.Com>
To: Bharath Kumar 
Cc: LSARC-ext@sun.com, Mark Carlson ,
        Arvind.Samptur@sun.com, John.Fischer@sun.com
Message-id: <20090414152842.GD7978@mumak.SFBay.Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E39F0F.8020201@sun.com> <18915.41283.448431.848127@gargle.gargle.HOWL>
 <49E45444.20907@Sun.Com>
User-Agent: Mutt/1.5.16 (2007-06-27)
Status: RO
Content-Length: 616

On Tue, Apr 14, 2009 at 02:45:48PM +0530, Bharath Kumar wrote:

>>> /usr/bin/schemagen.sh    Uncommitted   Jaxb schema generation script
>>> /usr/bin/xjc.sh          Uncommitted   Jaxb script to start xjc
>>
>> No ".sh" extensions in /usr/bin.
>
> I have modified them to be installed in /opt/SUNWjaxb/bin.

I was too specific.  No ".sh" extensions on anything delivered in a bin
directory that a user would be expected to execute.  Like Jim said, you
shouldn't be exposing the implementation details of the programming
language to the user.  *Plus* you shouldn't be delivering anything into
/opt in Solaris.

Danek

From Bharath.Madakatte@sun.com Tue Apr 14 09:20:23 2009
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3EGKNOf004637
	for ; Tue, 14 Apr 2009 09:20:23 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3EGKJKE019630
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 14 Apr 2009 09:20:23 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI300G05MPZS800@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 14 Apr 2009 09:20:23 -0700 (PDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI300CYAMPY6H30@nwk-avmta-1.sfbay.Sun.COM> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 14 Apr 2009 09:20:22 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3EGKMF0028615	for
 ; Tue, 14 Apr 2009 16:20:22 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI300M00LSG2200@mail-amer.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 14 Apr 2009 10:20:22 -0600 (MDT)
Received: from [192.168.1.18] ([unknown] [59.96.203.4])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KI300BVCMPF0ED0@mail-amer.sun.com>; Tue,
 14 Apr 2009 10:20:13 -0600 (MDT)
Date: Tue, 14 Apr 2009 21:50:01 +0530
From: Bharath 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <20090414152842.GD7978@mumak.SFBay.Sun.COM>
Sender: Bharath.Madakatte@sun.com
To: Danek Duvall 
Cc: LSARC-ext@sun.com, Mark Carlson ,
        Arvind.Samptur@sun.com, John.Fischer@sun.com
Message-id: <49E4B7B1.30606@Sun.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_1g5IRwfULD03IUvUjmg/Hg)"
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E39F0F.8020201@sun.com> <18915.41283.448431.848127@gargle.gargle.HOWL>
 <49E45444.20907@Sun.Com> <20090414152842.GD7978@mumak.SFBay.Sun.COM>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
Status: RO
Content-Length: 23540

This is a multi-part message in MIME format.

--Boundary_(ID_1g5IRwfULD03IUvUjmg/Hg)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_JHP5vcYTzTWQPuBbV+YjCw)"


--Boundary_(ID_JHP5vcYTzTWQPuBbV+YjCw)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

Hi Danek,
 
 Sorry, misread your earlier comment. Have made the modifications now 
removing the .sh extensions and left them in /usr/bin itself.
 Attached the modified drafts.

Thanks
Bharath
Danek Duvall wrote:
> On Tue, Apr 14, 2009 at 02:45:48PM +0530, Bharath Kumar wrote:
>
>   
>>>> /usr/bin/schemagen.sh    Uncommitted   Jaxb schema generation script
>>>> /usr/bin/xjc.sh          Uncommitted   Jaxb script to start xjc
>>>>         
>>> No ".sh" extensions in /usr/bin.
>>>       
>> I have modified them to be installed in /opt/SUNWjaxb/bin.
>>     
>
> I was too specific.  No ".sh" extensions on anything delivered in a bin
> directory that a user would be expected to execute.  Like Jim said, you
> shouldn't be exposing the implementation details of the programming
> language to the user.  *Plus* you shouldn't be delivering anything into
> /opt in Solaris.
>
> Danek
>   


--Boundary_(ID_JHP5vcYTzTWQPuBbV+YjCw)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT




  
  


Hi Danek,

 

 Sorry, misread your earlier comment. Have made the modifications now
removing the .sh extensions and left them in /usr/bin itself. 

 Attached
the modified drafts.



Thanks

Bharath

Danek Duvall wrote:


  
On Tue, Apr 14, 2009 at 02:45:48PM +0530, Bharath Kumar wrote:

  

  

    

      

        
/usr/bin/schemagen.sh    Uncommitted   Jaxb schema generation script
/usr/bin/xjc.sh          Uncommitted   Jaxb script to start xjc
        

      

      
No ".sh" extensions in /usr/bin.
      

    

    
I have modified them to be installed in /opt/SUNWjaxb/bin.
    

  

  

I was too specific.  No ".sh" extensions on anything delivered in a bin
directory that a user would be expected to execute.  Like Jim said, you
shouldn't be exposing the implementation details of the programming
language to the user.  *Plus* you shouldn't be delivering anything into
/opt in Solaris.

Danek
  








--Boundary_(ID_JHP5vcYTzTWQPuBbV+YjCw)--

--Boundary_(ID_1g5IRwfULD03IUvUjmg/Hg)
Content-type: text/plain; name=jaxbmanpage.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=jaxbmanpage.txt

Introduction to Library Functions                         jaxb(3)

NAME
     jaxb - Java Architecture  for  XML  Binding  is  a  standard
     extension to the Java platform.

SYNOPSIS
     Add relevant jaxb jar to the classpath

DESCRIPTION
     JAXB is an acronym derived from Java  Architecture  for  XML
     Binding.  It constitutes a convenient framework for process-
     ing XML documents, providing significant  benefits  as  com-
     pared  to  previously available methods such as the one fol-
     lowing the Document Object Model (DOM).In the DOM  approach,
     the  parser  creates  a  tree of objects that represents the
     content and organization of data in the document. The appli-
     cation  can  then  navigate  through  the  tree in memory to
     access the data it needs. DOM data, however, is contained in
     objects  of  a  single  type,  linked  according  to the XML
     document's structure, with individual node objects  contain-
     ing  an  element, an attribute, a CDATA section, etc. Values
     are invariably provided  as  strings.JAXB  provides  a  con-
     venient  way  to  process  XML content using Java objects by
     binding its XML schema to Java representation.

     For  more  details   about   Java   Architecture   for   XML
     Binding(JAXB), please see
     https://jaxb.dev.java.net web page.

FILES
     By   default,   all   jaxb   jars    are   installed    into
     /usr/share/lib/java  directory.  For more details about jars
     installed by jaxb, please see
     https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html

     The XML binding compiler can be launched using the xjc utili-
     ty in the bin directory /usr/bin
     The schema generator can be  launched  using  the  schemagen
     utility in the bin directory /usr/bin
     For more details on using the scripts, please see
     https://jaxb.dev.java.net/nonav/2.1.10/docs

     HTML-based documentation is located in jaxb's doc directory,
     /usr/share/doc/jaxb.

ENVIRONMENT
     JAVA_HOME variable must point to the directory where Java is
     installed.

SunOS 5.10                Last change:                          1

Introduction to Library Functions                         jaxb(3)

ATTRIBUTES
     See attributes(5) for descriptions of the  following  attri-
     butes:

     _______________________________________
    |   ATTRIBUTE TYPE   |  ATTRIBUTE VALUE|
    |____________________|_________________|
    | Availability       |  SUNWjaxb       |
    |____________________|_________________|
    | Interface Stability|  Uncommitted    |
    |____________________|_________________|

NOTES
     Source for jaxb is available on http://opensolaris.org.

SunOS 5.10                Last change:                          2

--Boundary_(ID_1g5IRwfULD03IUvUjmg/Hg)
Content-type: text/plain; name=jaxb.3
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=jaxb.3

'\" t
.\"
.\" CDDL HEADER START
.\"
.\" The contents of this file are subject to the terms of the
.\" Common Development and Distribution License (the "License").
.\" You may not use this file except in compliance with the License.
.\"
.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
.\" or http://www.opensolaris.org/os/licensing.
.\" See the License for the specific language governing permissions
.\" and limitations under the License.
.\"
.\" When distributing Covered Code, include this CDDL HEADER in each
.\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
.\" If applicable, add the following below this CDDL HEADER, with the
.\" fields enclosed by brackets "[]" replaced with your own identifying
.\" information: Portions Copyright [yyyy] [name of copyright owner]
.\"
.\" CDDL HEADER END
.\"
.\" Copyright 2009 Sun Microsystems, Inc.  All rights reserved.
.\" Use is subject to license terms.
.\"
.\" ident	"@(#)jaxb.3	1.1	09/04/13 SMI"
.\"
.TH "jaxb" "3" "" "" ""
.SH NAME
jaxb - Java Architecture for XML Binding is a standard extension to the Java platform.
.SH SYNOPSIS
.B Add relevant jaxb jar to the classpath.

.SH DESCRIPTION
JAXB is an acronym derived from Java Architecture for XML Binding. It constitutes a convenient framework for processing XML documents, providing significant benefits as compared to previously available methods such as the one following the Document Object Model (DOM).In the DOM approach, the parser creates a tree of objects that represents the content and organization of data in the document. The application can then navigate through the tree in memory to access the data it needs. DOM data, however, is contained in objects of a single type, linked according to the XML document's structure, with individual node objects containing an element, an attribute, a CDATA section, etc. Values are invariably provided as strings.JAXB provides a convenient way to process XML content using Java objects by binding its XML schema to Java representation.
.PP
For more details about Java Architecture for XML Binding(JAXB), please see
.br
.B https://jaxb.dev.java.net web page.

.SH FILES
By default, all jaxb jars  are installed into /usr/share/lib/java directory.
For more details about jars installed by jaxb, please see
.br
.B https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html

The XML binding compiler can be launched using the xjc utility in the bin directory /usr/bin
.br
The schema generator can be launched using the schemagen utility in the bin directory /usr/bin
.br
For more details on using the scripts, please see
.br
.B  https://jaxb.dev.java.net/nonav/2.1.10/docs

HTML-based documentation is located in jaxb's doc directory, /usr/share/doc/jaxb.

.SH ENVIRONMENT
JAVA_HOME variable must point to the directory where Java is installed.

.RE
.SH ATTRIBUTES
See
.BR attributes (5)
for descriptions of the following attributes:
.sp
.TS
box;
cbp-1 | cbp-1
l | l .
ATTRIBUTE TYPE	ATTRIBUTE VALUE
=
Availability	SUNWjaxb
=
Interface Stability	Uncommitted
.TE
.PP
.SH NOTES
Source for jaxb is available on http://opensolaris.org.


--Boundary_(ID_1g5IRwfULD03IUvUjmg/Hg)
Content-type: text/plain; name=jaxb-Arc.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=jaxb-Arc.txt

1. Introduction
   1.1. Project/Component Working Name:
        Jaxb

   1.2. Name of Document Author/Supplier:
        Author: Bharath Kumar

   1.3. Date of This Document:
        02 April 2009

2. Project Summary
   2.1 Project Description
       This project introduces the package of Jaxb2.1 into the SFW consolidation.

4. Technical Description:
	 Java Architecture for XML Binding (JAXB) provides an API and tool that allow automatic two-way mapping between XML documents and Java objects. With a given Document Type Definition (DTD) and a schema definition, the JAXB compiler can generate a set of Java classes that allow developers to build applications that can read, manipulate and recreate XML documents without writing any logic to process XML elements.

5. Interfaces

   Exported interfaces
   -------------------
    Interface Name				Classification      	Comments
    --------------------------- 		----------------	---------------------------
    SUNWjaxb                                    Uncommitted     	Jaxb Package
    Jaxb API    		   		Uncommitted	    	Jaxb Classes
    JSR ID 222                                  Committed               Java Specification Requests
    /usr/share/lib/java/jaxb-impl.jar         	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jaxb1-impl.jar         	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jaxb-api.jar         	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jsr173_1.0_api.jar     	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jaxb-xjc.jar         	Uncommitted   	   	Jaxb compiler jar
    /usr/bin/schemagen    	                Uncommitted   	   	Jaxb schema generation utility
    /usr/bin/xjc                                Uncommitted   	   	Jaxb utility to start xjc compiler
    /usr/share/doc/jaxb  	   		uncommitted             Jaxb doc directory
    /usr/share/man/man3/jaxb.3                  Uncommitted             Manpage
    
  4.2 Imported Interfaces
    Interface Name		Classification       	Comments
    ------------------------    ------------------  	--------------------------
    jdk1.5 	                committed		Java Development Kit
    activation.jar              Uncommitted		JavaBeans Activation Framework

    JSr details are available here: 
		http://jcp.org/en/jsr/detail?id=222
    Details about jaxb jars are available here:
		https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html
    Javadocs are available here : 
		https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html

6. Resources and Schedule:
   6.4. Product Approval Committee requested information:
   	6.4.1. Consolidation or Component Name:
	       SFW
   6.5. ARC review type: Automatic

   6.6. ARC Exposure: open

--Boundary_(ID_1g5IRwfULD03IUvUjmg/Hg)
Content-type: text/plain; name=jaxb-FOSS.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=jaxb-FOSS.txt

FCL--FOSS Check List
1.0 Project Information
1.1 Name of project/component
    Jaxb

1.2 Author of document
    Bharath Kumar Madakatte

2.0 Project Summary
  2.1 Project Description
	 Java Architecture for XML Binding (JAXB) provides an API and tool that allow automatic two-way mapping between XML documents and Java objects. With a given Document Type Definition (DTD) and a schema definition, the JAXB compiler can generate a set of Java classes that allow developers to build applications that can read, manipulate and recreate XML documents without writing any logic to process XML elements.  

  2.2 Release binding
      What is is the release binding?
      (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
      [ ] Major
      [X] Minor
      [ ] Patch or Micro
      [ ] Unknown -- ARC review required

  2.3 Type of project
      Is this case a Linux Familiarity project?
      [X] Yes
      [ ] No

  2.4 Originating Community
    2.4.1 Community Name
          https://jaxb.dev.java.net/
    2.4.2 Community Involvement
      Indicate Sun's involvement in the community
      [ ] Maintainer
      [ ] Contributor
      [X] Monitoring
      
      Will the project team work with the upstream community to resolve
      architectural issues of interest to Sun?
      [X] Yes 
      [ ] No - briefly explain
      
      Will we or are we forking from the community?
      [ ] Yes - ARC review required prior to forking
      [X] No
      
3.0 Technical Description
  3.1 Installation & Sharable
    3.1.1S Solaris Installation - section only required for Solaris Software
      (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details)
      Does this project follow the Install Locations best practice?
      [X] Yes 
      [ ] No - ARC review required
      
      Does this project install into /usr under [sbin|bin|lib|include|man|share]?
      [X] Yes
      [ ] No or N/A
      
      Does this project install into /opt?
      [ ] Yes - explain below
      [X] No or N/A
      
      Does this project install into a different directory structure?
      [ ] Yes - ARC review required
      [X] No or N/A
      
      Do any of the components of this project conflict with anything under /usr?
      (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details)
      [ ] Yes - explain below
      [X] No
      
      If conflicts exist then will this project install under /usr/gnu?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
      
      Is this project installing into /usr/sfw?
      [ ] Yes - ARC review required
      [X] No
      
    3.1.1W Windows Installation - section only required for Windows Software
      (see http://sac.sfbay/WSARC/2002/494 for details)
      Does this project install software into a 
      :\Program Files\Sun\ or :\Sun\
      directory?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use the Windows registry?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use 
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\
      for the registry key?
      [ ] Yes
      [ ] No - ARC review required
      
      Is the project's stored location
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path?
      [ ] Yes
      [ ] No - ARC review required
      
    3.1.2 Share and Sharable
      Does the module include any components that are used or shared by 
      other projects?
      [ ] Yes
      [X] No
    
      If yes are these components packaged to be shared with the other FOSS?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
    
      Are these components already in the Solaris WOS?
      [ ] Yes
      [X] No - continue with next section (section 3.2)
    
      If yes are these newer versions being delivered?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes are the newer versions replacing the existing versions?
      [ ] Yes
      [ ] No - ARC review required

  3.2 Exported Libraries
      Are libraries being delivered by this project?
      [X] Yes
      [ ] No - continue with next section (section 3.3)
      
      Are 64-bit versions of the libraries being delivered?
      [X] Yes
      [ ] No - ARC review required 
          Since these are Java jar libraries, there are no separate 64 bit jars.
    
      Are static versions of the libraries being delivered?
      [ ] Yes - ARC review required
      [X] No 
      
  3.3 Services and the /etc Directory
      (see http://opensolaris.org/os/community/arc/policies/SMF-policy/)
      Does the project integrate anything into /etc/init.d or /etc/rc?.d?
      [ ] Yes - ARC review required
      [X] No
      
      Does the project integrate any new entries into /etc/inittab or
      /etc/inetd.conf?
      [ ] Yes - ARC review required
      [X] No
      
      Does the project integrate any private non-public files into /etc/default
      or /etc/ configuration files?
      [ ] Yes - ARC review required
      [X] No
      
      Does the service manifests method context grant rights above that
      of the noaccess user and basic privilege set?
      [ ] Yes - ARC review required
      [X] No
        
  3.4 Security
    3.4.1 Secure By Default 
      (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details)
      (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details)
      (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for
       addtional details)
      Are there any network services provided by this project?
      [ ] Yes
      [X] No - continue with the next section (section 3.4.2)
      
      Are network services enabled by default?
      [ ] Yes - ARC review required
      [ ] No
      [ ] N/A
      
      Are network services automatically enabled by the project during installation?
      [ ] Yes - ARC review required
      [ ] No
      [ ] N/A
      
      Are inbound network communications denied by default?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is inbound data checked to prevent content-based attacks?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is the outbound receiver authenticated?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is the receiver authenticated prior to receiving any sensitive outbound communication?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
    3.4.2 Authorization
      (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/
           for details)
      Are there any setuid/setgid privileged binaries in the project?
      [ ] Yes - ARC review required
      [X] No - continue with next section (section 3.4.3)
      
      If yes then are the setuid/setgid privileges handled by the use of roles?
      [ ] Yes
      [ ] No - ARC review required

    3.4.3 Auditing
      (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details)
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Does this component contain administrative or security enforcing software?
      [ ] Yes - ARC review required
      [X] No - continue to next section (section 3.4.4)
      
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Do the components create audit logs detailing what took place including what event
      took place, who was involved, when the event took place?
      [ ] Yes - ARC contract and Audit project team review required
      [ ] No - ARC review required
        
        
    3.4.4 Authentication
      (see http://opensolaris.org/os/community/arc/policies/PAM/)
      Do the components contain any authentication code?
      [ ] Yes
      [X] No - continue to next section (section 3.4.5)
      
      If yes do the components use PAM (plugable authentication modules) for authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes is a single PAM session maintained during authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes are the components sufficiently privileged to allow the requested 
      operations (authentication, password change, process credential manipulation, 
      audit state initialization)?
      [ ] Yes - briefly describe below
      [ ] No - ARC review required
      
    3.4.5 Passwords
      (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and
           http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details)
      Do any of the components for the project deal with passwords?
      [ ] Yes
      [X] No - continue to next section (section 3.4.6)
      
      If yes are these passwords entered via the CLI or environment?
      [ ] Yes - ARC review required
      [ ] No
      
      Are passwords stored within the file system for the component?
      [ ] Yes
      [ ] No - continue to next section (section 3.4.6)
      
      If yes are the permissions on the file such to protect exposing the password(s)?
      [ ] Yes
      [ ] No - ARC review required
      
    3.4.6 General Security Questions
      (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details)
      Are there any network protocols used by this project?
      [ ] Yes
      [X] No - continue with the next section (section 3.5)
      
      Do the components use standard network protocols?
      [ ] Yes
      [ ] No - ARC review required
      
      Do network services for the project make decisions based upon user, host or 
      service identities?
      [ ] Yes - explain below
      [ ] No
      [ ] N/A
      
      Do the components make use of secret information during authentication and/or
      authorization?
      [ ] Yes - explain below
      [ ] No
      [ ] N/A
  
  3.5 Networking
      Do the components access the network?
      [ ] Yes
      [X] No - continue with the next section (section 3.6)
      
      If yes do the components support IPv6?
      [ ] Yes 
      [ ] No - ARC review required
          
  3.6 Core Solaris Components
      Do the components of this project compete with or duplicate core 
      Solaris components?
      [ ] Yes - ARC review required
      [X] No 
      
      Examples of Core Solaris Components include but are not limited to:
      
        Secure By Default
        Authorizations
        PAM -- Plugable Authentication Module
        Privilege
        PRM -- Process Rights Management -- Privilege
        Audit
        xVm -- Virtualization
        zones / Solaris Containers
        PRM -- Process Rights Management
        RBAC -- Role Based Access Control
        TX / Trusted Extensions
        ZFS
        SMF -- Service Management Facility
        FMA -- Fault Management Architecture
        SCF -- Smart Card Facility
        IPsec
        
4.0 Interfaces
  
	See project proposal.
        Javadocs are here:
		https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html

--Boundary_(ID_1g5IRwfULD03IUvUjmg/Hg)--

From carlsonj@phorcys.east.sun.com Tue Apr 14 09:56:44 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3EGuhuc006608
	for ; Tue, 14 Apr 2009 09:56:44 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3EGuF1C006434
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@Sun.COM>; Tue, 14 Apr 2009 17:56:43 +0100 (BST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI300707OEE7700@brm-avmta-1.central.sun.com> for LSARC-ext@Sun.COM
 (ORCPT LSARC-ext@Sun.COM); Tue, 14 Apr 2009 10:56:38 -0600 (MDT)
Received: from dm-east-02.east.sun.com ([129.148.13.5])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI300E42OEERIC0@brm-avmta-1.central.sun.com> for
 LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Tue,
 14 Apr 2009 10:56:38 -0600 (MDT)
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-02.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id n3EGua9A063053; Tue, 14 Apr 2009 12:56:36 -0400 (EDT)
Received: from phorcys.east.sun.com (phorcys.local [127.0.0.1])
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n3EGu8Yo015705; Tue,
 14 Apr 2009 12:56:08 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n3EGu8hS015702; Tue,
 14 Apr 2009 12:56:08 -0400 (EDT)
Date: Tue, 14 Apr 2009 12:56:08 -0400
From: James Carlson 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <49E45444.20907@Sun.Com>
To: Bharath.Madakatte@sun.com
Cc: LSARC-ext@sun.com, Arvind.Samptur@sun.com
Message-id: <18916.49192.169036.657296@gargle.gargle.HOWL>
MIME-version: 1.0
X-Mailer: VM 7.01 under Emacs 21.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E39F0F.8020201@sun.com> <18915.41283.448431.848127@gargle.gargle.HOWL>
 <49E45444.20907@Sun.Com>
Status: RO
Content-Length: 1224

Bharath Kumar writes:
> >>     /usr/share/lib/java/jaxb-xjc.jar         	Uncommitted   	   	Jaxb compiler jar
> >>     /usr/bin/schemagen.sh            	        Uncommitted   	   	Jaxb schema generation script
> >>     /usr/bin/xjc.sh         	                Uncommitted   	   	Jaxb script to start xjc
> >>     
> >
> > No ".sh" extensions in /usr/bin.
> 
> I have modified them to be installed in /opt/SUNWjaxb/bin.

There shouldn't be any ".sh" anywhere.

Is this being shipped as part of either Solaris or OpenSolaris?  If
so, then it doesn't belong in /opt at all, and should not be delivered
that way.

> John Fischer wrote:
> > schemagen.sh seems a little to generic for my tastes.  Is this name
> > dictated by the JSR specification?  If not perhaps changing the name
> > to xjc-schemagen.sh might be better.
> 
> Yes these names are dictated by JSR specifications.

The ".sh" is part of the JSR?!

How is it that the JSR process can be this far out of step with normal
system architecture?

-- 
James Carlson, Solaris Networking              
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

From Alan.Coopersmith@sun.com Tue Apr 14 10:24:34 2009
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3EHOXcE009254
	for ; Tue, 14 Apr 2009 10:24:34 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3EHOUfh061941
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 14 Apr 2009 11:24:33 -0600 (MDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI30010RPOW2M00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 14 Apr 2009 10:24:32 -0700 (PDT)
Received: from sca-es-mail-1.sun.com ([192.18.43.132])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI300CYQPOW6OD0@nwk-avmta-1.sfbay.Sun.COM> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 14 Apr 2009 10:24:32 -0700 (PDT)
Received: from fe-sfbay-10.sun.com ([192.18.43.129])
	by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n3EHOWMe007123	for
 ; Tue, 14 Apr 2009 10:24:32 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI300600P2XM400@fe-sfbay-10.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 14 Apr 2009 10:24:32 -0700 (PDT)
Received: from [10.6.102.118] ([unknown] [10.6.102.118])
 by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KI300LLKPOKC3F0@fe-sfbay-10.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 14 Apr 2009 10:24:20 -0700 (PDT)
Date: Tue, 14 Apr 2009 10:24:20 -0700
From: Alan Coopersmith 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <18916.49192.169036.657296@gargle.gargle.HOWL>
Sender: Alan.Coopersmith@sun.com
To: James Carlson 
Cc: Bharath.Madakatte@sun.com, LSARC-ext@sun.com, Arvind.Samptur@sun.com
Message-id: <49E4C6C4.1020606@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
X-Enigmail-Version: 0.95.1
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E39F0F.8020201@sun.com> <18915.41283.448431.848127@gargle.gargle.HOWL>
 <49E45444.20907@Sun.Com> <18916.49192.169036.657296@gargle.gargle.HOWL>
User-Agent: Thunderbird 2.0.0.6 (X11/20071119)
Status: RO
Content-Length: 1201



James Carlson wrote:
>> John Fischer wrote:
> Bharath Kumar writes:
>>> schemagen.sh seems a little to generic for my tastes.  Is this name
>>> dictated by the JSR specification?  If not perhaps changing the name
>>> to xjc-schemagen.sh might be better.
>> Yes these names are dictated by JSR specifications.
> 
> The ".sh" is part of the JSR?!
> 
> How is it that the JSR process can be this far out of step with normal
> system architecture?

I didn't read all 384 pages of "JSR-000222 JavaTM Architecture for XML Binding
(JAXB) 2.0 FR Specification" (jaxb-2_0-fr-spec.pdf), but a search of it did
not find the string schemagen anywhere in it, much less schemagen.sh.

It would seem strange for a Java spec to dictate a Unix shell script as part
of the spec - what would Windows or other platform users do?

At least one RPM packaging (from jpackage.org) I found in a quick google seems
to use a less  generic name:
  install -m 755 dist/bin/schemagen.sh
    $RPM_BUILD_ROOT%{_bindir}/sun-jaxb-schemagen

(from http://www.zarb.org/pipermail/jpackage-commits/2008-May/001030.html )

-- 
	-Alan Coopersmith-           alan.coopersmith@sun.com
	 Sun Microsystems, Inc. - X Window System Engineering


From margot.miller@Sun.COM Tue Apr 14 16:17:12 2009
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3ENHCDA013827
	for ; Tue, 14 Apr 2009 16:17:12 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3ENH7E2016690;
	Tue, 14 Apr 2009 16:17:10 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI400L0360LDZ00@brm-avmta-1.central.sun.com>; Tue,
 14 Apr 2009 17:17:09 -0600 (MDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI4007M360LY370@brm-avmta-1.central.sun.com>; Tue,
 14 Apr 2009 17:17:09 -0600 (MDT)
Received: from [10.7.250.251]
 (punchin-client-10-7-250-251.SFBay.Sun.COM [10.7.250.251])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n3ENH5n2169790; Tue, 14 Apr 2009 16:17:06 -0700 (PDT)
Date: Tue, 14 Apr 2009 16:12:15 -0700
From: Margot Miller 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
To: Mark Carlson 
Cc: LSARC-ext@Sun.COM, Arvind.Samptur@Sun.COM, Bharath.Madakatte@Sun.COM
Message-id: <49E5184F.9040905@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
User-Agent: Thunderbird 2.0b1 (X11/20070115)
Status: RO
Content-Length: 3148

Does this really depend upon JDK 1.5 or just the latest JDK
on the system?

Thanks
Margot


Mark Carlson wrote:
> I am sponsoring this familiarity case for Bharath Kumar, requesting minor binding and timing out 04/20/2009.
>
> -- mark
>
> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
> This information is Copyright 2009 Sun Microsystems
> 1. Introduction
>     1.1. Project/Component Working Name:
> 	 JAXB
>     1.2. Name of Document Author/Supplier:
> 	 Author:  Bharath Kumar
>     1.3  Date of This Document:
> 	13 April, 2009
>
> 2. Project Summary
>    2.1 Project Description
>        This project introduces the package of Jaxb2.1 into the SFW consolidation.
>
> 4. Technical Description:
> 	 Java Architecture for XML Binding (JAXB) provides an API and tool that allow automatic two-way mapping between XML documents and Java objects. With a given Document Type Definition (DTD) and a schema definition, the JAXB compiler can generate a set of Java classes that allow developers to build applications that can read, manipulate and recreate XML documents without writing any logic to process XML elements.
>
> 5. Interfaces
>
>    Exported interfaces
>    -------------------
>     Interface Name				Classification      	Comments
>     --------------------------- 		----------------	---------------------------
>     SUNWJaxb                                    Uncommitted     	Jaxb Package
>     Jaxb API    		   		Uncommitted	    	Jaxb Classes
>     JSR ID 222                                  Committed               Java Specification Requests
>     /usr/share/lib/java/jaxb-impl.jar         	Uncommitted   	   	Jaxb runtime jar
>     /usr/share/lib/java/jaxb1-impl.jar         	Uncommitted   	   	Jaxb runtime jar
>     /usr/share/lib/java/jaxb-api.jar         	Uncommitted   	   	Jaxb runtime jar
>     /usr/share/lib/java/jsr173_1.0_api.jar     	Uncommitted   	   	Jaxb runtime jar
>     /usr/share/lib/java/jaxb-xjc.jar         	Uncommitted   	   	Jaxb compiler jar
>     /usr/bin/schemagen.sh            	        Uncommitted   	   	Jaxb schema generation script
>     /usr/bin/xjc.sh         	                Uncommitted   	   	Jaxb script to start xjc
>     /usr/share/doc/jaxb  	   		uncommitted             Jaxb doc directory
>     /usr/share/man/man3/jaxb.3                  Uncommitted             Manpage
>     
>   4.2 Imported Interfaces
>     Interface Name		Classification       	Comments
>     ------------------------    ------------------  	--------------------------
>     jdk1.5 	                committed		Java Development Kit
>     activation.jar              Uncommitted		JavaBeans Activation Framework
>
>     JSr details are available here: 
> 		http://jcp.org/en/jsr/detail?id=222
>     Javadocs are available here : 
> 		https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html
>
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>    	6.4.1. Consolidation C-team Name:
> 		SFW
>     6.5. ARC review type: FastTrack
>     6.6. ARC Exposure: open
>
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc@opensolaris.org
>   


From Mark.Carlson@sun.com Tue Apr 14 17:34:34 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3F0YXaL014951
	for ; Tue, 14 Apr 2009 17:34:34 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3F0YQcZ028986
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 15 Apr 2009 01:34:33 +0100 (BST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI40060D9LJHB00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 14 Apr 2009 18:34:31 -0600 (MDT)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI4007WN9LJXYA0@brm-avmta-1.central.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 14 Apr 2009 18:34:31 -0600 (MDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3F0YVQv000856	for
 ; Wed, 15 Apr 2009 00:34:31 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI400500938QI00@mail-amer.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 14 Apr 2009 18:34:31 -0600 (MDT)
Received: from Macintosh-335.local ([unknown] [129.150.35.180])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KI400MJB9LIA6D0@mail-amer.sun.com>; Tue,
 14 Apr 2009 18:34:30 -0600 (MDT)
Date: Tue, 14 Apr 2009 18:34:30 -0600
From: "Mark A. Carlson" 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <49E5184F.9040905@sun.com>
Sender: Mark.Carlson@sun.com
To: Margot Miller 
Cc: Mark Carlson , Arvind.Samptur@sun.com,
        Bharath.Madakatte@sun.com, LSARC-ext@sun.com
Message-id: <49E52B96.9050704@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_aOLAcXbg01Kk1jnTgnqEDQ)"
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E5184F.9040905@sun.com>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
Status: RO
Content-Length: 13019

This is a multi-part message in MIME format.

--Boundary_(ID_aOLAcXbg01Kk1jnTgnqEDQ)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

I believe that JDK 6 and above have JAXB integrated
so you only need it if you have JDK 1.5

--- mark

Margot Miller wrote:
> Does this really depend upon JDK 1.5 or just the latest JDK
> on the system?
>
> Thanks
> Margot
>
>
> Mark Carlson wrote:
>> I am sponsoring this familiarity case for Bharath Kumar, requesting 
>> minor binding and timing out 04/20/2009.
>>
>> -- mark
>>
>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
>> This information is Copyright 2009 Sun Microsystems
>> 1. Introduction
>>     1.1. Project/Component Working Name:
>>      JAXB
>>     1.2. Name of Document Author/Supplier:
>>      Author:  Bharath Kumar
>>     1.3  Date of This Document:
>>     13 April, 2009
>>
>> 2. Project Summary
>>    2.1 Project Description
>>        This project introduces the package of Jaxb2.1 into the SFW 
>> consolidation.
>>
>> 4. Technical Description:
>>      Java Architecture for XML Binding (JAXB) provides an API and 
>> tool that allow automatic two-way mapping between XML documents and 
>> Java objects. With a given Document Type Definition (DTD) and a 
>> schema definition, the JAXB compiler can generate a set of Java 
>> classes that allow developers to build applications that can read, 
>> manipulate and recreate XML documents without writing any logic to 
>> process XML elements.
>>
>> 5. Interfaces
>>
>>    Exported interfaces
>>    -------------------
>>     Interface Name                Classification          Comments
>>     ---------------------------         ----------------    
>> ---------------------------
>>     SUNWJaxb                                    Uncommitted         
>> Jaxb Package
>>     Jaxb API                       Uncommitted            Jaxb Classes
>>     JSR ID 222                                  
>> Committed               Java Specification Requests
>>     /usr/share/lib/java/jaxb-impl.jar             
>> Uncommitted              Jaxb runtime jar
>>     /usr/share/lib/java/jaxb1-impl.jar             
>> Uncommitted              Jaxb runtime jar
>>     /usr/share/lib/java/jaxb-api.jar             
>> Uncommitted              Jaxb runtime jar
>>     /usr/share/lib/java/jsr173_1.0_api.jar         
>> Uncommitted              Jaxb runtime jar
>>     /usr/share/lib/java/jaxb-xjc.jar             
>> Uncommitted              Jaxb compiler jar
>>     /usr/bin/schemagen.sh                        
>> Uncommitted              Jaxb schema generation script
>>     /usr/bin/xjc.sh                             
>> Uncommitted              Jaxb script to start xjc
>>     /usr/share/doc/jaxb                 uncommitted             Jaxb 
>> doc directory
>>     /usr/share/man/man3/jaxb.3                  
>> Uncommitted             Manpage
>>       4.2 Imported Interfaces
>>     Interface Name        Classification           Comments
>>     ------------------------    ------------------      
>> --------------------------
>>     jdk1.5                     committed        Java Development Kit
>>     activation.jar              Uncommitted        JavaBeans 
>> Activation Framework
>>
>>     JSr details are available here:         
>> http://jcp.org/en/jsr/detail?id=222
>>     Javadocs are available here :         
>> https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html
>>
>> 6. Resources and Schedule
>>     6.4. Steering Committee requested information
>>        6.4.1. Consolidation C-team Name:
>>         SFW
>>     6.5. ARC review type: FastTrack
>>     6.6. ARC Exposure: open
>>
>> _______________________________________________
>> opensolaris-arc mailing list
>> opensolaris-arc@opensolaris.org
>>   
>
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc@opensolaris.org

-- 
 	* Mark A. Carlson *
Sr. Architect

*Systems Group*
Phone x69559 / 303-223-6139
Email Mark.Carlson@Sun.COM
	



--Boundary_(ID_aOLAcXbg01Kk1jnTgnqEDQ)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT




  


I believe that JDK 6 and above have JAXB integrated

so you only need it if you have JDK 1.5



--- mark



Margot Miller wrote:

Does this
really depend upon JDK 1.5 or just the latest JDK
  

on the system?
  

  

Thanks
  

Margot
  

  

  

Mark Carlson wrote:
  

  
I am sponsoring this familiarity case for
Bharath Kumar, requesting minor binding and timing out 04/20/2009.
    

    

-- mark
    

    

Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
    

This information is Copyright 2009 Sun Microsystems
    

1. Introduction
    

    1.1. Project/Component Working Name:
    

     JAXB
    

    1.2. Name of Document Author/Supplier:
    

     Author:  Bharath Kumar
    

    1.3  Date of This Document:
    

    13 April, 2009
    

    

2. Project Summary
    

   2.1 Project Description
    

       This project introduces the package of Jaxb2.1 into the SFW
consolidation.
    

    

4. Technical Description:
    

     Java Architecture for XML Binding (JAXB) provides an API and tool
that allow automatic two-way mapping between XML documents and Java
objects. With a given Document Type Definition (DTD) and a schema
definition, the JAXB compiler can generate a set of Java classes that
allow developers to build applications that can read, manipulate and
recreate XML documents without writing any logic to process XML
elements.
    

    

5. Interfaces
    

    

   Exported interfaces
    

   -------------------
    

    Interface Name                Classification          Comments
    

    ---------------------------         ----------------   
---------------------------
    

    SUNWJaxb                                    Uncommitted        
Jaxb Package
    

    Jaxb API                       Uncommitted            Jaxb Classes
    

    JSR ID 222                                  Committed              
Java Specification Requests
    

    /usr/share/lib/java/jaxb-impl.jar            
Uncommitted              Jaxb runtime jar
    

    /usr/share/lib/java/jaxb1-impl.jar            
Uncommitted              Jaxb runtime jar
    

    /usr/share/lib/java/jaxb-api.jar            
Uncommitted              Jaxb runtime jar
    

    /usr/share/lib/java/jsr173_1.0_api.jar        
Uncommitted              Jaxb runtime jar
    

    /usr/share/lib/java/jaxb-xjc.jar            
Uncommitted              Jaxb compiler jar
    

    /usr/bin/schemagen.sh                       
Uncommitted              Jaxb schema generation script
    

    /usr/bin/xjc.sh                            
Uncommitted              Jaxb script to start xjc
    

    /usr/share/doc/jaxb                 uncommitted             Jaxb
doc directory
    

    /usr/share/man/man3/jaxb.3                  Uncommitted            
Manpage
    

      4.2 Imported Interfaces
    

    Interface Name        Classification           Comments
    

    ------------------------    ------------------     
--------------------------
    

    jdk1.5                     committed        Java Development Kit
    

    activation.jar              Uncommitted        JavaBeans Activation
Framework
    

    

    JSr details are available here:        
http://jcp.org/en/jsr/detail?id=222
    

    Javadocs are available here :        
https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html
    

    

6. Resources and Schedule
    

    6.4. Steering Committee requested information
    

       6.4.1. Consolidation C-team Name:
    

        SFW
    

    6.5. ARC review type: FastTrack
    

    6.6. ARC Exposure: open
    

    

_______________________________________________
    

opensolaris-arc mailing list
    

opensolaris-arc@opensolaris.org
    

  

  

_______________________________________________
  

opensolaris-arc mailing list
  

opensolaris-arc@opensolaris.org
  






-- 




  
    

      
       Mark A. Carlson 

Sr. Architect

      

      Systems Group

Phone x69559 / 303-223-6139

Email Mark.Carlson@Sun.COM

      		
      
    

  












--Boundary_(ID_aOLAcXbg01Kk1jnTgnqEDQ)--

From Alan.Coopersmith@sun.com Tue Apr 14 17:41:53 2009
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3F0fqZd014966
	for ; Tue, 14 Apr 2009 17:41:52 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3F0fZNb015339
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 15 Apr 2009 08:41:51 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI4000039XP4900@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@Sun.COM); Tue, 14 Apr 2009 17:41:49 -0700 (PDT)
Received: from sca-es-mail-2.sun.com ([192.18.43.133])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI400N7U9XP2610@nwk-avmta-2.sfbay.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Tue,
 14 Apr 2009 17:41:49 -0700 (PDT)
Received: from fe-sfbay-09.sun.com ([192.18.43.129])
	by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n3F0fnVk029051	for
 ; Tue, 14 Apr 2009 17:41:49 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI4002009TNV900@fe-sfbay-09.sun.com> for LSARC-ext@Sun.COM
 (ORCPT LSARC-ext@Sun.COM); Tue, 14 Apr 2009 17:41:49 -0700 (PDT)
Received: from [10.6.102.118] ([unknown] [10.6.102.118])
 by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KI4002X69X94M80@fe-sfbay-09.sun.com>;
 Tue, 14 Apr 2009 17:41:34 -0700 (PDT)
Date: Tue, 14 Apr 2009 17:41:33 -0700
From: Alan Coopersmith 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <49E52B96.9050704@sun.com>
Sender: Alan.Coopersmith@sun.com
To: "Mark A. Carlson" 
Cc: Margot Miller ,
        Mark Carlson , Arvind.Samptur@sun.com,
        Bharath.Madakatte@sun.com, LSARC-ext@sun.com
Message-id: <49E52D3D.6030007@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
X-Enigmail-Version: 0.95.1
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E5184F.9040905@sun.com> <49E52B96.9050704@sun.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071119)
Status: RO
Content-Length: 4247

Then why are we doing this project at all, since JDK 1.6 is already
integrated and no earlier versions are provided on OpenSolaris?

	-alan-

Mark A. Carlson wrote:
> I believe that JDK 6 and above have JAXB integrated
> so you only need it if you have JDK 1.5
> 
> --- mark
> 
> Margot Miller wrote:
>> Does this really depend upon JDK 1.5 or just the latest JDK
>> on the system?
>>
>> Thanks
>> Margot
>>
>>
>> Mark Carlson wrote:
>>> I am sponsoring this familiarity case for Bharath Kumar, requesting
>>> minor binding and timing out 04/20/2009.
>>>
>>> -- mark
>>>
>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
>>> This information is Copyright 2009 Sun Microsystems
>>> 1. Introduction
>>>     1.1. Project/Component Working Name:
>>>      JAXB
>>>     1.2. Name of Document Author/Supplier:
>>>      Author:  Bharath Kumar
>>>     1.3  Date of This Document:
>>>     13 April, 2009
>>>
>>> 2. Project Summary
>>>    2.1 Project Description
>>>        This project introduces the package of Jaxb2.1 into the SFW
>>> consolidation.
>>>
>>> 4. Technical Description:
>>>      Java Architecture for XML Binding (JAXB) provides an API and
>>> tool that allow automatic two-way mapping between XML documents and
>>> Java objects. With a given Document Type Definition (DTD) and a
>>> schema definition, the JAXB compiler can generate a set of Java
>>> classes that allow developers to build applications that can read,
>>> manipulate and recreate XML documents without writing any logic to
>>> process XML elements.
>>>
>>> 5. Interfaces
>>>
>>>    Exported interfaces
>>>    -------------------
>>>     Interface Name                Classification          Comments
>>>     ---------------------------         ----------------   
>>> ---------------------------
>>>     SUNWJaxb                                    Uncommitted        
>>> Jaxb Package
>>>     Jaxb API                       Uncommitted            Jaxb Classes
>>>     JSR ID 222                                 
>>> Committed               Java Specification Requests
>>>     /usr/share/lib/java/jaxb-impl.jar            
>>> Uncommitted              Jaxb runtime jar
>>>     /usr/share/lib/java/jaxb1-impl.jar            
>>> Uncommitted              Jaxb runtime jar
>>>     /usr/share/lib/java/jaxb-api.jar            
>>> Uncommitted              Jaxb runtime jar
>>>     /usr/share/lib/java/jsr173_1.0_api.jar        
>>> Uncommitted              Jaxb runtime jar
>>>     /usr/share/lib/java/jaxb-xjc.jar            
>>> Uncommitted              Jaxb compiler jar
>>>     /usr/bin/schemagen.sh                       
>>> Uncommitted              Jaxb schema generation script
>>>     /usr/bin/xjc.sh                            
>>> Uncommitted              Jaxb script to start xjc
>>>     /usr/share/doc/jaxb                 uncommitted             Jaxb
>>> doc directory
>>>     /usr/share/man/man3/jaxb.3                 
>>> Uncommitted             Manpage
>>>       4.2 Imported Interfaces
>>>     Interface Name        Classification           Comments
>>>     ------------------------    ------------------     
>>> --------------------------
>>>     jdk1.5                     committed        Java Development Kit
>>>     activation.jar              Uncommitted        JavaBeans
>>> Activation Framework
>>>
>>>     JSr details are available here:        
>>> http://jcp.org/en/jsr/detail?id=222
>>>     Javadocs are available here :        
>>> https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html
>>>
>>> 6. Resources and Schedule
>>>     6.4. Steering Committee requested information
>>>        6.4.1. Consolidation C-team Name:
>>>         SFW
>>>     6.5. ARC review type: FastTrack
>>>     6.6. ARC Exposure: open
>>>
>>> _______________________________________________
>>> opensolaris-arc mailing list
>>> opensolaris-arc@opensolaris.org
>>>   
>>
>> _______________________________________________
>> opensolaris-arc mailing list
>> opensolaris-arc@opensolaris.org
> 
> -- 
>  	* Mark A. Carlson *
> Sr. Architect
> 
> *Systems Group*
> Phone x69559 / 303-223-6139
> Email Mark.Carlson@Sun.COM
> 	
> 
> 

-- 
	-Alan Coopersmith-           alan.coopersmith@sun.com
	 Sun Microsystems, Inc. - X Window System Engineering


From Mark.Carlson@sun.com Tue Apr 14 18:32:22 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3F1WK1e015788
	for ; Tue, 14 Apr 2009 18:32:20 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3F1WESU005783
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 15 Apr 2009 02:32:19 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI400G01C9VU500@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 14 Apr 2009 18:32:19 -0700 (PDT)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI4005YGC9UGR40@nwk-avmta-1.sfbay.Sun.COM> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 14 Apr 2009 18:32:18 -0700 (PDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3F1WIWj016493	for
 ; Wed, 15 Apr 2009 01:32:18 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI400C00BT4TH00@mail-amer.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 14 Apr 2009 19:32:18 -0600 (MDT)
Received: from Macintosh-335.local ([unknown] [129.150.35.180])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KI4009KLC9RKY60@mail-amer.sun.com>; Tue,
 14 Apr 2009 19:32:16 -0600 (MDT)
Date: Tue, 14 Apr 2009 19:32:15 -0600
From: "Mark A. Carlson" 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <49E52D3D.6030007@sun.com>
Sender: Mark.Carlson@sun.com
To: Alan Coopersmith 
Cc: Margot Miller ,
        Mark Carlson , Arvind.Samptur@sun.com,
        Bharath.Madakatte@sun.com, LSARC-ext@sun.com
Message-id: <49E5391F.5020102@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_EYhgtT7KR7jqlLUg4VjgZw)"
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E5184F.9040905@sun.com> <49E52B96.9050704@sun.com>
 <49E52D3D.6030007@sun.com>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
Status: RO
Content-Length: 10915

This is a multi-part message in MIME format.

--Boundary_(ID_EYhgtT7KR7jqlLUg4VjgZw)
Content-type: text/plain; format=flowed; charset=UTF-8
Content-transfer-encoding: 7BIT

Some projects haven't moved to JDK 6 yet and we don't want
to wait for those upstream communities to catch up.

-- mark

Alan Coopersmith wrote:
> Then why are we doing this project at all, since JDK 1.6 is already
> integrated and no earlier versions are provided on OpenSolaris?
>
> 	-alan-
>
> Mark A. Carlson wrote:
>   
>> I believe that JDK 6 and above have JAXB integrated
>> so you only need it if you have JDK 1.5
>>
>> --- mark
>>
>> Margot Miller wrote:
>>     
>>> Does this really depend upon JDK 1.5 or just the latest JDK
>>> on the system?
>>>
>>> Thanks
>>> Margot
>>>
>>>
>>> Mark Carlson wrote:
>>>       
>>>> I am sponsoring this familiarity case for Bharath Kumar, requesting
>>>> minor binding and timing out 04/20/2009.
>>>>
>>>> -- mark
>>>>
>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
>>>> This information is Copyright 2009 Sun Microsystems
>>>> 1. Introduction
>>>>     1.1. Project/Component Working Name:
>>>>      JAXB
>>>>     1.2. Name of Document Author/Supplier:
>>>>      Author:  Bharath Kumar
>>>>     1.3  Date of This Document:
>>>>     13 April, 2009
>>>>
>>>> 2. Project Summary
>>>>    2.1 Project Description
>>>>        This project introduces the package of Jaxb2.1 into the SFW
>>>> consolidation.
>>>>
>>>> 4. Technical Description:
>>>>      Java Architecture for XML Binding (JAXB) provides an API and
>>>> tool that allow automatic two-way mapping between XML documents and
>>>> Java objects. With a given Document Type Definition (DTD) and a
>>>> schema definition, the JAXB compiler can generate a set of Java
>>>> classes that allow developers to build applications that can read,
>>>> manipulate and recreate XML documents without writing any logic to
>>>> process XML elements.
>>>>
>>>> 5. Interfaces
>>>>
>>>>    Exported interfaces
>>>>    -------------------
>>>>     Interface Name                Classification          Comments
>>>>     ---------------------------         ----------------   
>>>> ---------------------------
>>>>     SUNWJaxb                                    Uncommitted        
>>>> Jaxb Package
>>>>     Jaxb API                       Uncommitted            Jaxb Classes
>>>>     JSR ID 222                                 
>>>> Committed               Java Specification Requests
>>>>     /usr/share/lib/java/jaxb-impl.jar            
>>>> Uncommitted              Jaxb runtime jar
>>>>     /usr/share/lib/java/jaxb1-impl.jar            
>>>> Uncommitted              Jaxb runtime jar
>>>>     /usr/share/lib/java/jaxb-api.jar            
>>>> Uncommitted              Jaxb runtime jar
>>>>     /usr/share/lib/java/jsr173_1.0_api.jar        
>>>> Uncommitted              Jaxb runtime jar
>>>>     /usr/share/lib/java/jaxb-xjc.jar            
>>>> Uncommitted              Jaxb compiler jar
>>>>     /usr/bin/schemagen.sh                       
>>>> Uncommitted              Jaxb schema generation script
>>>>     /usr/bin/xjc.sh                            
>>>> Uncommitted              Jaxb script to start xjc
>>>>     /usr/share/doc/jaxb                 uncommitted             Jaxb
>>>> doc directory
>>>>     /usr/share/man/man3/jaxb.3                 
>>>> Uncommitted             Manpage
>>>>       4.2 Imported Interfaces
>>>>     Interface Name        Classification           Comments
>>>>     ------------------------    ------------------     
>>>> --------------------------
>>>>     jdk1.5                     committed        Java Development Kit
>>>>     activation.jar              Uncommitted        JavaBeans
>>>> Activation Framework
>>>>
>>>>     JSr details are available here:        
>>>> http://jcp.org/en/jsr/detail?id=222
>>>>     Javadocs are available here :        
>>>> https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html
>>>>
>>>> 6. Resources and Schedule
>>>>     6.4. Steering Committee requested information
>>>>        6.4.1. Consolidation C-team Name:
>>>>         SFW
>>>>     6.5. ARC review type: FastTrack
>>>>     6.6. ARC Exposure: open
>>>>
>>>> _______________________________________________
>>>> opensolaris-arc mailing list
>>>> opensolaris-arc@opensolaris.org
>>>>   
>>>>         
>>> _______________________________________________
>>> opensolaris-arc mailing list
>>> opensolaris-arc@opensolaris.org
>>>       
>> -- 
>>  	* Mark A. Carlson *
>> Sr. Architect
>>
>> *Systems Group*
>> Phone x69559 / 303-223-6139
>> Email Mark.Carlson@Sun.COM
>> 	
>>
>>
>>     
>
>   

-- 
 	* Mark A. Carlson *
Sr. Architect

*Systems Group*
Phone x69559 / 303-223-6139
Email Mark.Carlson@Sun.COM
	



--Boundary_(ID_EYhgtT7KR7jqlLUg4VjgZw)
Content-type: text/html; charset=UTF-8
Content-transfer-encoding: 7BIT




  


Some projects haven't moved to JDK 6 yet and we don't want

to wait for those upstream communities to catch up.



-- mark



Alan Coopersmith wrote:


  
Then why are we doing this project at all, since JDK 1.6 is already
integrated and no earlier versions are provided on OpenSolaris?

	-alan-

Mark A. Carlson wrote:
  

  

    
I believe that JDK 6 and above have JAXB integrated
so you only need it if you have JDK 1.5

--- mark

Margot Miller wrote:
    

    

      
Does this really depend upon JDK 1.5 or just the latest JDK
on the system?

Thanks
Margot


Mark Carlson wrote:
      

      

        
I am sponsoring this familiarity case for Bharath Kumar, requesting
minor binding and timing out 04/20/2009.

-- mark

Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
     JAXB
    1.2. Name of Document Author/Supplier:
     Author:  Bharath Kumar
    1.3  Date of This Document:
    13 April, 2009

2. Project Summary
   2.1 Project Description
       This project introduces the package of Jaxb2.1 into the SFW
consolidation.

4. Technical Description:
     Java Architecture for XML Binding (JAXB) provides an API and
tool that allow automatic two-way mapping between XML documents and
Java objects. With a given Document Type Definition (DTD) and a
schema definition, the JAXB compiler can generate a set of Java
classes that allow developers to build applications that can read,
manipulate and recreate XML documents without writing any logic to
process XML elements.

5. Interfaces

   Exported interfaces
   -------------------
    Interface Name                Classification          Comments
    ---------------------------         ----------------   
---------------------------
    SUNWJaxb                                    Uncommitted        
Jaxb Package
    Jaxb API                       Uncommitted            Jaxb Classes
    JSR ID 222                                 
Committed               Java Specification Requests
    /usr/share/lib/java/jaxb-impl.jar            
Uncommitted              Jaxb runtime jar
    /usr/share/lib/java/jaxb1-impl.jar            
Uncommitted              Jaxb runtime jar
    /usr/share/lib/java/jaxb-api.jar            
Uncommitted              Jaxb runtime jar
    /usr/share/lib/java/jsr173_1.0_api.jar        
Uncommitted              Jaxb runtime jar
    /usr/share/lib/java/jaxb-xjc.jar            
Uncommitted              Jaxb compiler jar
    /usr/bin/schemagen.sh                       
Uncommitted              Jaxb schema generation script
    /usr/bin/xjc.sh                            
Uncommitted              Jaxb script to start xjc
    /usr/share/doc/jaxb                 uncommitted             Jaxb
doc directory
    /usr/share/man/man3/jaxb.3                 
Uncommitted             Manpage
      4.2 Imported Interfaces
    Interface Name        Classification           Comments
    ------------------------    ------------------     
--------------------------
    jdk1.5                     committed        Java Development Kit
    activation.jar              Uncommitted        JavaBeans
Activation Framework

    JSr details are available here:        
http://jcp.org/en/jsr/detail?id=222
    Javadocs are available here :        
https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html

6. Resources and Schedule
    6.4. Steering Committee requested information
       6.4.1. Consolidation C-team Name:
        SFW
    6.5. ARC review type: FastTrack
    6.6. ARC Exposure: open

_______________________________________________
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org
  
        

      

      
_______________________________________________
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org
      

    

    
-- 
<http://www.sun.com> 	* Mark A. Carlson *
Sr. Architect

*Systems Group*
Phone x69559 / 303-223-6139
Email Mark.Carlson@Sun.COM
	


    

  

  

  






-- 




  
    

      
       Mark A. Carlson 

Sr. Architect

      

      Systems Group

Phone x69559 / 303-223-6139

Email Mark.Carlson@Sun.COM

      		
      
    

  












--Boundary_(ID_EYhgtT7KR7jqlLUg4VjgZw)--

From Bharath.Madakatte@sun.com Wed Apr 15 02:09:52 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3F99p9J017190
	for ; Wed, 15 Apr 2009 02:09:52 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3F99etL029702
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 15 Apr 2009 10:09:50 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI400901XGDTN00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 15 Apr 2009 02:09:49 -0700 (PDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI40093YXGC7N20@nwk-avmta-2.sfbay.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed,
 15 Apr 2009 02:09:48 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3F99mrC026012	for
 ; Wed, 15 Apr 2009 09:09:48 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI400G00X9RGO00@mail-amer.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 15 Apr 2009 03:09:48 -0600 (MDT)
Received: from [10.114.58.92] ([unknown] [203.91.196.62])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KI400H1HXFQPS00@mail-amer.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed,
 15 Apr 2009 03:09:33 -0600 (MDT)
Date: Wed, 15 Apr 2009 14:39:39 +0530
From: Bharath Kumar 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <18916.49192.169036.657296@gargle.gargle.HOWL>
Sender: Bharath.Madakatte@sun.com
To: James Carlson 
Cc: LSARC-ext@sun.com, Arvind.Samptur@sun.com,
        Mark Carlson , Bharath.Madakatte@sun.com
Reply-to: Bharath.Madakatte@sun.com
Message-id: <49E5A453.8050805@Sun.Com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_G0uFDcGzJIxiZ0GTdK9yaw)"
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E39F0F.8020201@sun.com> <18915.41283.448431.848127@gargle.gargle.HOWL>
 <49E45444.20907@Sun.Com> <18916.49192.169036.657296@gargle.gargle.HOWL>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
Status: RO
Content-Length: 22880

This is a multi-part message in MIME format.

--Boundary_(ID_G0uFDcGzJIxiZ0GTdK9yaw)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_RW+80DNiLmEkBqyXc/+mQA)"


--Boundary_(ID_RW+80DNiLmEkBqyXc/+mQA)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

Hi James,

James Carlson wrote:
>>> schemagen.sh seems a little to generic for my tastes.  Is this name
>>> dictated by the JSR specification?  If not perhaps changing the name
>>> to xjc-schemagen.sh might be better.
>>>       
>> Yes these names are dictated by JSR specifications.
>>     
>
> The ".sh" is part of the JSR?!
>
> How is it that the JSR process can be this far out of step with normal
> system architecture?
>
>   
Sorry, my bad. You are right, it does not specify the names as such. As 
suggested, have changed the "schemagen" name to "xjc-schemagen"

Attaching the updated ARC docs.

Thanks
Bharath

--Boundary_(ID_RW+80DNiLmEkBqyXc/+mQA)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT




  


Hi James,



James Carlson wrote:


  

    

      
schemagen.sh seems a little to generic for my tastes.  Is this name
dictated by the JSR specification?  If not perhaps changing the name
to xjc-schemagen.sh might be better.
      

    

    
Yes these names are dictated by JSR specifications.
    

  

  

The ".sh" is part of the JSR?!

How is it that the JSR process can be this far out of step with normal
system architecture?

  



Sorry, my bad. You are right, it does not specify the names as such. As
suggested, have changed the "schemagen" name to "xjc-schemagen"



Attaching the updated ARC docs.



Thanks

Bharath




--Boundary_(ID_RW+80DNiLmEkBqyXc/+mQA)--

--Boundary_(ID_G0uFDcGzJIxiZ0GTdK9yaw)
Content-type: text/plain; name=jaxb.3
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=jaxb.3

'\" t
.\"
.\" CDDL HEADER START
.\"
.\" The contents of this file are subject to the terms of the
.\" Common Development and Distribution License (the "License").
.\" You may not use this file except in compliance with the License.
.\"
.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
.\" or http://www.opensolaris.org/os/licensing.
.\" See the License for the specific language governing permissions
.\" and limitations under the License.
.\"
.\" When distributing Covered Code, include this CDDL HEADER in each
.\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
.\" If applicable, add the following below this CDDL HEADER, with the
.\" fields enclosed by brackets "[]" replaced with your own identifying
.\" information: Portions Copyright [yyyy] [name of copyright owner]
.\"
.\" CDDL HEADER END
.\"
.\" Copyright 2009 Sun Microsystems, Inc.  All rights reserved.
.\" Use is subject to license terms.
.\"
.\" ident	"@(#)jaxb.3	1.1	09/04/13 SMI"
.\"
.TH "jaxb" "3" "" "" ""
.SH NAME
jaxb - Java Architecture for XML Binding is a standard extension to the Java platform.
.SH SYNOPSIS
.B Add relevant jaxb jar to the classpath.

.SH DESCRIPTION
JAXB is an acronym derived from Java Architecture for XML Binding. It constitutes a convenient framework for processing XML documents, providing significant benefits as compared to previously available methods such as the one following the Document Object Model (DOM).In the DOM approach, the parser creates a tree of objects that represents the content and organization of data in the document. The application can then navigate through the tree in memory to access the data it needs. DOM data, however, is contained in objects of a single type, linked according to the XML document's structure, with individual node objects containing an element, an attribute, a CDATA section, etc. Values are invariably provided as strings.JAXB provides a convenient way to process XML content using Java objects by binding its XML schema to Java representation.
.PP
For more details about Java Architecture for XML Binding(JAXB), please see
.br
.B https://jaxb.dev.java.net web page.

.SH FILES
By default, all jaxb jars  are installed into /usr/share/lib/java directory.
For more details about jars installed by jaxb, please see
.br
.B https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html

The XML binding compiler can be launched using the xjc tool in the bin directory /usr/bin
.br
The schema generator can be launched using the xjc-schemagen tool in the bin directory /usr/bin
.br
For more details on using the tools, please see
.br
.B  https://jaxb.dev.java.net/nonav/2.1.10/docs

HTML-based documentation is located in jaxb's doc directory, /usr/share/doc/jaxb.

.SH ENVIRONMENT
JAVA_HOME variable must point to the directory where Java is installed.

.RE
.SH ATTRIBUTES
See
.BR attributes (5)
for descriptions of the following attributes:
.sp
.TS
box;
cbp-1 | cbp-1
l | l .
ATTRIBUTE TYPE	ATTRIBUTE VALUE
=
Availability	SUNWjaxb
=
Interface Stability	Uncommitted
.TE
.PP
.SH NOTES
Source for jaxb is available on http://opensolaris.org.


--Boundary_(ID_G0uFDcGzJIxiZ0GTdK9yaw)
Content-type: text/plain; name=jaxb-Arc.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=jaxb-Arc.txt

1. Introduction
   1.1. Project/Component Working Name:
        Jaxb

   1.2. Name of Document Author/Supplier:
        Author: Bharath Kumar

   1.3. Date of This Document:
        02 April 2009

2. Project Summary
   2.1 Project Description
       This project introduces the package of Jaxb2.1 into the SFW consolidation.

4. Technical Description:
	 Java Architecture for XML Binding (JAXB) provides an API and tool that allow automatic two-way mapping between XML documents and Java objects. With a given Document Type Definition (DTD) and a schema definition, the JAXB compiler can generate a set of Java classes that allow developers to build applications that can read, manipulate and recreate XML documents without writing any logic to process XML elements.

5. Interfaces

   Exported interfaces
   -------------------
    Interface Name				Classification      	Comments
    --------------------------- 		----------------	---------------------------
    SUNWjaxb                                    Uncommitted     	Jaxb Package
    Jaxb API    		   		Uncommitted	    	Jaxb Classes
    JSR ID 222                                  Committed               Java Specification Requests
    /usr/share/lib/java/jaxb-impl.jar         	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jaxb1-impl.jar         	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jaxb-api.jar         	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jsr173_1.0_api.jar     	Uncommitted   	   	Jaxb runtime jar
    /usr/share/lib/java/jaxb-xjc.jar         	Uncommitted   	   	Jaxb compiler jar
    /usr/bin/xjc-schemagen    	                Uncommitted   	   	Jaxb schema generation utility
    /usr/bin/xjc                                Uncommitted   	   	Jaxb utility to start xjc compiler
    /usr/share/doc/jaxb  	   		uncommitted             Jaxb doc directory
    /usr/share/man/man3/jaxb.3                  Uncommitted             Manpage
    
  4.2 Imported Interfaces
    Interface Name		Classification       	Comments
    ------------------------    ------------------  	--------------------------
    jdk1.5 	                committed		Java Development Kit
    activation.jar              Uncommitted		JavaBeans Activation Framework

    JSr details are available here: 
		http://jcp.org/en/jsr/detail?id=222
    Details about jaxb jars are available here:
		https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html
    Javadocs are available here : 
		https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html

6. Resources and Schedule:
   6.4. Product Approval Committee requested information:
   	6.4.1. Consolidation or Component Name:
	       SFW
   6.5. ARC review type: Automatic

   6.6. ARC Exposure: open

--Boundary_(ID_G0uFDcGzJIxiZ0GTdK9yaw)
Content-type: text/plain; name=jaxb-FOSS.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=jaxb-FOSS.txt

FCL--FOSS Check List
1.0 Project Information
1.1 Name of project/component
    Jaxb

1.2 Author of document
    Bharath Kumar Madakatte

2.0 Project Summary
  2.1 Project Description
	 Java Architecture for XML Binding (JAXB) provides an API and tool that allow automatic two-way mapping between XML documents and Java objects. With a given Document Type Definition (DTD) and a schema definition, the JAXB compiler can generate a set of Java classes that allow developers to build applications that can read, manipulate and recreate XML documents without writing any logic to process XML elements.  

  2.2 Release binding
      What is is the release binding?
      (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
      [ ] Major
      [X] Minor
      [ ] Patch or Micro
      [ ] Unknown -- ARC review required

  2.3 Type of project
      Is this case a Linux Familiarity project?
      [X] Yes
      [ ] No

  2.4 Originating Community
    2.4.1 Community Name
          https://jaxb.dev.java.net/
    2.4.2 Community Involvement
      Indicate Sun's involvement in the community
      [ ] Maintainer
      [ ] Contributor
      [X] Monitoring
      
      Will the project team work with the upstream community to resolve
      architectural issues of interest to Sun?
      [X] Yes 
      [ ] No - briefly explain
      
      Will we or are we forking from the community?
      [ ] Yes - ARC review required prior to forking
      [X] No
      
3.0 Technical Description
  3.1 Installation & Sharable
    3.1.1S Solaris Installation - section only required for Solaris Software
      (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details)
      Does this project follow the Install Locations best practice?
      [X] Yes 
      [ ] No - ARC review required
      
      Does this project install into /usr under [sbin|bin|lib|include|man|share]?
      [X] Yes
      [ ] No or N/A
      
      Does this project install into /opt?
      [ ] Yes - explain below
      [X] No or N/A
      
      Does this project install into a different directory structure?
      [ ] Yes - ARC review required
      [X] No or N/A
      
      Do any of the components of this project conflict with anything under /usr?
      (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details)
      [ ] Yes - explain below
      [X] No
      
      If conflicts exist then will this project install under /usr/gnu?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
      
      Is this project installing into /usr/sfw?
      [ ] Yes - ARC review required
      [X] No
      
    3.1.1W Windows Installation - section only required for Windows Software
      (see http://sac.sfbay/WSARC/2002/494 for details)
      Does this project install software into a 
      :\Program Files\Sun\ or :\Sun\
      directory?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use the Windows registry?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use 
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\
      for the registry key?
      [ ] Yes
      [ ] No - ARC review required
      
      Is the project's stored location
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path?
      [ ] Yes
      [ ] No - ARC review required
      
    3.1.2 Share and Sharable
      Does the module include any components that are used or shared by 
      other projects?
      [ ] Yes
      [X] No
    
      If yes are these components packaged to be shared with the other FOSS?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
    
      Are these components already in the Solaris WOS?
      [ ] Yes
      [X] No - continue with next section (section 3.2)
    
      If yes are these newer versions being delivered?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes are the newer versions replacing the existing versions?
      [ ] Yes
      [ ] No - ARC review required

  3.2 Exported Libraries
      Are libraries being delivered by this project?
      [X] Yes
      [ ] No - continue with next section (section 3.3)
      
      Are 64-bit versions of the libraries being delivered?
      [X] Yes
      [ ] No - ARC review required 
          Since these are Java jar libraries, there are no separate 64 bit jars.
    
      Are static versions of the libraries being delivered?
      [ ] Yes - ARC review required
      [X] No 
      
  3.3 Services and the /etc Directory
      (see http://opensolaris.org/os/community/arc/policies/SMF-policy/)
      Does the project integrate anything into /etc/init.d or /etc/rc?.d?
      [ ] Yes - ARC review required
      [X] No
      
      Does the project integrate any new entries into /etc/inittab or
      /etc/inetd.conf?
      [ ] Yes - ARC review required
      [X] No
      
      Does the project integrate any private non-public files into /etc/default
      or /etc/ configuration files?
      [ ] Yes - ARC review required
      [X] No
      
      Does the service manifests method context grant rights above that
      of the noaccess user and basic privilege set?
      [ ] Yes - ARC review required
      [X] No
        
  3.4 Security
    3.4.1 Secure By Default 
      (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details)
      (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details)
      (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for
       addtional details)
      Are there any network services provided by this project?
      [ ] Yes
      [X] No - continue with the next section (section 3.4.2)
      
      Are network services enabled by default?
      [ ] Yes - ARC review required
      [ ] No
      [ ] N/A
      
      Are network services automatically enabled by the project during installation?
      [ ] Yes - ARC review required
      [ ] No
      [ ] N/A
      
      Are inbound network communications denied by default?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is inbound data checked to prevent content-based attacks?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is the outbound receiver authenticated?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is the receiver authenticated prior to receiving any sensitive outbound communication?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
    3.4.2 Authorization
      (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/
           for details)
      Are there any setuid/setgid privileged binaries in the project?
      [ ] Yes - ARC review required
      [X] No - continue with next section (section 3.4.3)
      
      If yes then are the setuid/setgid privileges handled by the use of roles?
      [ ] Yes
      [ ] No - ARC review required

    3.4.3 Auditing
      (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details)
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Does this component contain administrative or security enforcing software?
      [ ] Yes - ARC review required
      [X] No - continue to next section (section 3.4.4)
      
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Do the components create audit logs detailing what took place including what event
      took place, who was involved, when the event took place?
      [ ] Yes - ARC contract and Audit project team review required
      [ ] No - ARC review required
        
        
    3.4.4 Authentication
      (see http://opensolaris.org/os/community/arc/policies/PAM/)
      Do the components contain any authentication code?
      [ ] Yes
      [X] No - continue to next section (section 3.4.5)
      
      If yes do the components use PAM (plugable authentication modules) for authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes is a single PAM session maintained during authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes are the components sufficiently privileged to allow the requested 
      operations (authentication, password change, process credential manipulation, 
      audit state initialization)?
      [ ] Yes - briefly describe below
      [ ] No - ARC review required
      
    3.4.5 Passwords
      (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and
           http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details)
      Do any of the components for the project deal with passwords?
      [ ] Yes
      [X] No - continue to next section (section 3.4.6)
      
      If yes are these passwords entered via the CLI or environment?
      [ ] Yes - ARC review required
      [ ] No
      
      Are passwords stored within the file system for the component?
      [ ] Yes
      [ ] No - continue to next section (section 3.4.6)
      
      If yes are the permissions on the file such to protect exposing the password(s)?
      [ ] Yes
      [ ] No - ARC review required
      
    3.4.6 General Security Questions
      (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details)
      Are there any network protocols used by this project?
      [ ] Yes
      [X] No - continue with the next section (section 3.5)
      
      Do the components use standard network protocols?
      [ ] Yes
      [ ] No - ARC review required
      
      Do network services for the project make decisions based upon user, host or 
      service identities?
      [ ] Yes - explain below
      [ ] No
      [ ] N/A
      
      Do the components make use of secret information during authentication and/or
      authorization?
      [ ] Yes - explain below
      [ ] No
      [ ] N/A
  
  3.5 Networking
      Do the components access the network?
      [ ] Yes
      [X] No - continue with the next section (section 3.6)
      
      If yes do the components support IPv6?
      [ ] Yes 
      [ ] No - ARC review required
          
  3.6 Core Solaris Components
      Do the components of this project compete with or duplicate core 
      Solaris components?
      [ ] Yes - ARC review required
      [X] No 
      
      Examples of Core Solaris Components include but are not limited to:
      
        Secure By Default
        Authorizations
        PAM -- Plugable Authentication Module
        Privilege
        PRM -- Process Rights Management -- Privilege
        Audit
        xVm -- Virtualization
        zones / Solaris Containers
        PRM -- Process Rights Management
        RBAC -- Role Based Access Control
        TX / Trusted Extensions
        ZFS
        SMF -- Service Management Facility
        FMA -- Fault Management Architecture
        SCF -- Smart Card Facility
        IPsec
        
4.0 Interfaces
  
	See project proposal.
        Javadocs are here:
		https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html

--Boundary_(ID_G0uFDcGzJIxiZ0GTdK9yaw)
Content-type: text/plain; name=jaxbmanpage.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=jaxbmanpage.txt

Introduction to Library Functions                         jaxb(3)

NAME
     jaxb - Java Architecture  for  XML  Binding  is  a  standard
     extension to the Java platform.

SYNOPSIS
     Add relevant jaxb jar to the classpath

DESCRIPTION
     JAXB is an acronym derived from Java  Architecture  for  XML
     Binding.  It constitutes a convenient framework for process-
     ing XML documents, providing significant  benefits  as  com-
     pared  to  previously available methods such as the one fol-
     lowing the Document Object Model (DOM).In the DOM  approach,
     the  parser  creates  a  tree of objects that represents the
     content and organization of data in the document. The appli-
     cation  can  then  navigate  through  the  tree in memory to
     access the data it needs. DOM data, however, is contained in
     objects  of  a  single  type,  linked  according  to the XML
     document's structure, with individual node objects  contain-
     ing  an  element, an attribute, a CDATA section, etc. Values
     are invariably provided  as  strings.JAXB  provides  a  con-
     venient  way  to  process  XML content using Java objects by
     binding its XML schema to Java representation.

     For  more  details   about   Java   Architecture   for   XML
     Binding(JAXB), please see
     https://jaxb.dev.java.net web page.

FILES
     By   default,   all   jaxb   jars    are   installed    into
     /usr/share/lib/java  directory.  For more details about jars
     installed by jaxb, please see
     https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html

     The XML binding compiler can be launched using the  xjc  tool
     in the bin directory /usr/bin
     The schema generator can be  launched using the xjc-schemagen
     tool in the bin directory /usr/bin
     For more details on using the tools, please see
     https://jaxb.dev.java.net/nonav/2.1.10/docs

     HTML-based documentation is located in jaxb's doc directory,
     /usr/share/doc/jaxb.

ENVIRONMENT
     JAVA_HOME variable must point to the directory where Java is
     installed.

SunOS 5.10                Last change:                          1

Introduction to Library Functions                         jaxb(3)

ATTRIBUTES
     See attributes(5) for descriptions of the  following  attri-
     butes:

     _______________________________________
    |   ATTRIBUTE TYPE   |  ATTRIBUTE VALUE|
    |____________________|_________________|
    | Availability       |  SUNWjaxb       |
    |____________________|_________________|
    | Interface Stability|  Uncommitted    |
    |____________________|_________________|

NOTES
     Source for jaxb is available on http://opensolaris.org.

SunOS 5.10                Last change:                          2

--Boundary_(ID_G0uFDcGzJIxiZ0GTdK9yaw)--

From carlsonj@phorcys.east.sun.com Wed Apr 15 04:37:56 2009
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FBbt78014322
	for ; Wed, 15 Apr 2009 04:37:55 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3FBborJ023887
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@Sun.COM>; Wed, 15 Apr 2009 19:37:54 +0800 (SGT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI5007014B6FG00@brm-avmta-1.central.sun.com> for LSARC-ext@Sun.COM
 (ORCPT LSARC-ext@Sun.COM); Wed, 15 Apr 2009 05:37:54 -0600 (MDT)
Received: from dm-east-01.east.sun.com ([129.148.9.192])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI500FL94B5ZCA0@brm-avmta-1.central.sun.com> for
 LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Wed,
 15 Apr 2009 05:37:53 -0600 (MDT)
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id n3FBbpXi029514; Wed, 15 Apr 2009 07:37:51 -0400 (EDT)
Received: from phorcys.east.sun.com (phorcys.local [127.0.0.1])
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n3FBbLeA018020; Wed,
 15 Apr 2009 07:37:21 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n3FBbL5d018017; Wed,
 15 Apr 2009 07:37:21 -0400 (EDT)
Date: Wed, 15 Apr 2009 07:37:21 -0400
From: James Carlson 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <49E5A453.8050805@Sun.Com>
To: Bharath.Madakatte@sun.com
Cc: LSARC-ext@sun.com, Arvind.Samptur@sun.com,
        Mark Carlson 
Message-id: <18917.50929.700967.753666@gargle.gargle.HOWL>
MIME-version: 1.0
X-Mailer: VM 7.01 under Emacs 21.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E39F0F.8020201@sun.com> <18915.41283.448431.848127@gargle.gargle.HOWL>
 <49E45444.20907@Sun.Com> <18916.49192.169036.657296@gargle.gargle.HOWL>
 <49E5A453.8050805@Sun.Com>
Status: RO
Content-Length: 663

Bharath Kumar writes:
> Sorry, my bad. You are right, it does not specify the names as such. As 
> suggested, have changed the "schemagen" name to "xjc-schemagen"

Assuming that would be expected and tolerated by users, I'm happy
enough.

(It seems to exist as /usr/jdk/instances/jdk1.6.0/bin/schemagen
... not sure why it's different here for 1.5, or why there isn't
enough compatibility in Java to allow just a single delivery.  *sigh*)

-- 
James Carlson, Solaris Networking              
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

From Arieh.Markel@sun.com Wed Apr 15 05:33:05 2009
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FCX3w6015978
	for ; Wed, 15 Apr 2009 05:33:03 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3FCWvTn010207
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 15 Apr 2009 06:33:03 -0600 (MDT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI500L2J6V2W900@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 15 Apr 2009 05:33:02 -0700 (PDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI500EAP6V1IW70@nwk-avmta-2.sfbay.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed,
 15 Apr 2009 05:33:01 -0700 (PDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3FCX194019229	for
 ; Wed, 15 Apr 2009 12:33:01 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI500L006F7OS00@mail-amer.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 15 Apr 2009 06:33:01 -0600 (MDT)
Received: from [192.168.20.3] ([unknown] [79.182.123.43])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KI5003AS6UUT7E0@mail-amer.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed,
 15 Apr 2009 06:33:00 -0600 (MDT)
Date: Wed, 15 Apr 2009 15:32:53 +0300
From: Arieh Markel 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <49E5A453.8050805@Sun.Com>
Sender: Arieh.Markel@sun.com
To: Bharath.Madakatte@sun.com
Cc: James Carlson , LSARC-ext@sun.com,
        Arvind.Samptur@sun.com, Mark Carlson 
Message-id: <208C8AC8-3A98-4AD3-B6EC-68D6DF58083A@sun.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.930.3)
Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E39F0F.8020201@sun.com> <18915.41283.448431.848127@gargle.gargle.HOWL>
 <49E45444.20907@Sun.Com> <18916.49192.169036.657296@gargle.gargle.HOWL>
 <49E5A453.8050805@Sun.Com>
Status: RO
Content-Length: 21886

Shouldn't the JAXB API be committed as well ?

Can the JAXB API (and java-api.jar) which supposedly include the  
interface definitions stated in
the JSR spec not be at the same level of stability ?

Arieh

On Apr 15, 2009, at 12:09 PM, Bharath Kumar wrote:

> Hi James,
>
> James Carlson wrote:
>>
>>>> schemagen.sh seems a little to generic for my tastes.  Is this name
>>>> dictated by the JSR specification?  If not perhaps changing the  
>>>> name
>>>> to xjc-schemagen.sh might be better.
>>>>
>>> Yes these names are dictated by JSR specifications.
>>>
>> The ".sh" is part of the JSR?!
>>
>> How is it that the JSR process can be this far out of step with  
>> normal
>> system architecture?
>>
>>
> Sorry, my bad. You are right, it does not specify the names as such.  
> As suggested, have changed the "schemagen" name to "xjc-schemagen"
>
> Attaching the updated ARC docs.
>
> Thanks
> Bharath
> '\" t
> .\"
> .\" CDDL HEADER START
> .\"
> .\" The contents of this file are subject to the terms of the
> .\" Common Development and Distribution License (the "License").
> .\" You may not use this file except in compliance with the License.
> .\"
> .\" You can obtain a copy of the license at usr/src/ 
> OPENSOLARIS.LICENSE
> .\" or http://www.opensolaris.org/os/licensing.
> .\" See the License for the specific language governing permissions
> .\" and limitations under the License.
> .\"
> .\" When distributing Covered Code, include this CDDL HEADER in each
> .\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
> .\" If applicable, add the following below this CDDL HEADER, with the
> .\" fields enclosed by brackets "[]" replaced with your own  
> identifying
> .\" information: Portions Copyright [yyyy] [name of copyright owner]
> .\"
> .\" CDDL HEADER END
> .\"
> .\" Copyright 2009 Sun Microsystems, Inc.  All rights reserved.
> .\" Use is subject to license terms.
> .\"
> .\" ident	"@(#)jaxb.3	1.1	09/04/13 SMI"
> .\"
> .TH "jaxb" "3" "" "" ""
> .SH NAME
> jaxb - Java Architecture for XML Binding is a standard extension to  
> the Java platform.
> .SH SYNOPSIS
> .B Add relevant jaxb jar to the classpath.
>
> .SH DESCRIPTION
> JAXB is an acronym derived from Java Architecture for XML Binding.  
> It constitutes a convenient framework for processing XML documents,  
> providing significant benefits as compared to previously available  
> methods such as the one following the Document Object Model (DOM).In  
> the DOM approach, the parser creates a tree of objects that  
> represents the content and organization of data in the document. The  
> application can then navigate through the tree in memory to access  
> the data it needs. DOM data, however, is contained in objects of a  
> single type, linked according to the XML document's structure, with  
> individual node objects containing an element, an attribute, a CDATA  
> section, etc. Values are invariably provided as strings.JAXB  
> provides a convenient way to process XML content using Java objects  
> by binding its XML schema to Java representation.
> .PP
> For more details about Java Architecture for XML Binding(JAXB),  
> please see
> .br
> .B https://jaxb.dev.java.net web page.
>
> .SH FILES
> By default, all jaxb jars  are installed into /usr/share/lib/java  
> directory.
> For more details about jars installed by jaxb, please see
> .br
> .B https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html
>
> The XML binding compiler can be launched using the xjc tool in the  
> bin directory /usr/bin
> .br
> The schema generator can be launched using the xjc-schemagen tool in  
> the bin directory /usr/bin
> .br
> For more details on using the tools, please see
> .br
> .B  https://jaxb.dev.java.net/nonav/2.1.10/docs
>
> HTML-based documentation is located in jaxb's doc directory, /usr/ 
> share/doc/jaxb.
>
> .SH ENVIRONMENT
> JAVA_HOME variable must point to the directory where Java is  
> installed.
>
> .RE
> .SH ATTRIBUTES
> See
> .BR attributes (5)
> for descriptions of the following attributes:
> .sp
> .TS
> box;
> cbp-1 | cbp-1
> l | l .
> ATTRIBUTE TYPE	ATTRIBUTE VALUE
> =
> Availability	SUNWjaxb
> =
> Interface Stability	Uncommitted
> .TE
> .PP
> .SH NOTES
> Source for jaxb is available on http://opensolaris.org.
>
> 1. Introduction
>   1.1. Project/Component Working Name:
>        Jaxb
>
>   1.2. Name of Document Author/Supplier:
>        Author: Bharath Kumar
>
>   1.3. Date of This Document:
>        02 April 2009
>
> 2. Project Summary
>   2.1 Project Description
>       This project introduces the package of Jaxb2.1 into the SFW  
> consolidation.
>
> 4. Technical Description:
> 	 Java Architecture for XML Binding (JAXB) provides an API and tool  
> that allow automatic two-way mapping between XML documents and Java  
> objects. With a given Document Type Definition (DTD) and a schema  
> definition, the JAXB compiler can generate a set of Java classes  
> that allow developers to build applications that can read,  
> manipulate and recreate XML documents without writing any logic to  
> process XML elements.
>
> 5. Interfaces
>
>   Exported interfaces
>   -------------------
>    Interface Name				Classification      	Comments
>    ---------------------------  
> 		----------------	---------------------------
>    SUNWjaxb                                    Uncommitted     	Jaxb  
> Package
>    Jaxb API    		   		Uncommitted	    	Jaxb Classes
>    JSR ID 222                                   
> Committed               Java Specification Requests
>    /usr/share/lib/java/jaxb-impl.jar         	Uncommitted   	   	 
> Jaxb runtime jar
>    /usr/share/lib/java/jaxb1-impl.jar         	Uncommitted   	   	 
> Jaxb runtime jar
>    /usr/share/lib/java/jaxb-api.jar         	Uncommitted   	   	Jaxb  
> runtime jar
>    /usr/share/lib/java/jsr173_1.0_api.jar     	Uncommitted   	   	 
> Jaxb runtime jar
>    /usr/share/lib/java/jaxb-xjc.jar         	Uncommitted   	   	Jaxb  
> compiler jar
>    /usr/bin/xjc-schemagen    	                Uncommitted   	   	 
> Jaxb schema generation utility
>    /usr/bin/xjc                                Uncommitted   	   	 
> Jaxb utility to start xjc compiler
>    /usr/share/doc/jaxb  	   		uncommitted             Jaxb doc  
> directory
>    /usr/share/man/man3/jaxb.3                   
> Uncommitted             Manpage
>
>  4.2 Imported Interfaces
>    Interface Name		Classification       	Comments
>    ------------------------    ------------------   
> 	--------------------------
>    jdk1.5 	                committed		Java Development Kit
>    activation.jar              Uncommitted		JavaBeans Activation  
> Framework
>
>    JSr details are available here:
> 		http://jcp.org/en/jsr/detail?id=222
>    Details about jaxb jars are available here:
> 		https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html
>    Javadocs are available here :
> 		https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html
>
> 6. Resources and Schedule:
>   6.4. Product Approval Committee requested information:
>   	6.4.1. Consolidation or Component Name:
> 	       SFW
>   6.5. ARC review type: Automatic
>
>   6.6. ARC Exposure: open
> FCL--FOSS Check List
> 1.0 Project Information
> 1.1 Name of project/component
>    Jaxb
>
> 1.2 Author of document
>    Bharath Kumar Madakatte
>
> 2.0 Project Summary
>  2.1 Project Description
> 	 Java Architecture for XML Binding (JAXB) provides an API and tool  
> that allow automatic two-way mapping between XML documents and Java  
> objects. With a given Document Type Definition (DTD) and a schema  
> definition, the JAXB compiler can generate a set of Java classes  
> that allow developers to build applications that can read,  
> manipulate and recreate XML documents without writing any logic to  
> process XML elements.
>
>  2.2 Release binding
>      What is is the release binding?
>      (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
>      [ ] Major
>      [X] Minor
>      [ ] Patch or Micro
>      [ ] Unknown -- ARC review required
>
>  2.3 Type of project
>      Is this case a Linux Familiarity project?
>      [X] Yes
>      [ ] No
>
>  2.4 Originating Community
>    2.4.1 Community Name
>          https://jaxb.dev.java.net/
>    2.4.2 Community Involvement
>      Indicate Sun's involvement in the community
>      [ ] Maintainer
>      [ ] Contributor
>      [X] Monitoring
>
>      Will the project team work with the upstream community to resolve
>      architectural issues of interest to Sun?
>      [X] Yes
>      [ ] No - briefly explain
>
>      Will we or are we forking from the community?
>      [ ] Yes - ARC review required prior to forking
>      [X] No
>
> 3.0 Technical Description
>  3.1 Installation & Sharable
>    3.1.1S Solaris Installation - section only required for Solaris  
> Software
>      (see http://opensolaris.org/os/community/arc/policies/install-locations/ 
>  for details)
>      Does this project follow the Install Locations best practice?
>      [X] Yes
>      [ ] No - ARC review required
>
>      Does this project install into /usr under [sbin|bin|lib|include| 
> man|share]?
>      [X] Yes
>      [ ] No or N/A
>
>      Does this project install into /opt?
>      [ ] Yes - explain below
>      [X] No or N/A
>
>      Does this project install into a different directory structure?
>      [ ] Yes - ARC review required
>      [X] No or N/A
>
>      Do any of the components of this project conflict with anything  
> under /usr?
>      (see http://opensolaris.org/os/community/arc/caselog/2007/047/  
> for details)
>      [ ] Yes - explain below
>      [X] No
>
>      If conflicts exist then will this project install under /usr/gnu?
>      [ ] Yes
>      [ ] No - ARC review required
>      [X] N/A
>
>      Is this project installing into /usr/sfw?
>      [ ] Yes - ARC review required
>      [X] No
>
>    3.1.1W Windows Installation - section only required for Windows  
> Software
>      (see http://sac.sfbay/WSARC/2002/494 for details)
>      Does this project install software into a
>      :\Program Files\Sun\ or : 
> \Sun\
>      directory?
>      [ ] Yes
>      [ ] No - ARC review required
>
>      Does the project use the Windows registry?
>      [ ] Yes
>      [ ] No - ARC review required
>
>      Does the project use
>      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\
>      for the registry key?
>      [ ] Yes
>      [ ] No - ARC review required
>
>      Is the project's stored location
>      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\ 
> \\Path?
>      [ ] Yes
>      [ ] No - ARC review required
>
>    3.1.2 Share and Sharable
>      Does the module include any components that are used or shared by
>      other projects?
>      [ ] Yes
>      [X] No
>
>      If yes are these components packaged to be shared with the  
> other FOSS?
>      [ ] Yes
>      [ ] No - ARC review required
>      [X] N/A
>
>      Are these components already in the Solaris WOS?
>      [ ] Yes
>      [X] No - continue with next section (section 3.2)
>
>      If yes are these newer versions being delivered?
>      [ ] Yes
>      [ ] No - ARC review required
>
>      If yes are the newer versions replacing the existing versions?
>      [ ] Yes
>      [ ] No - ARC review required
>
>  3.2 Exported Libraries
>      Are libraries being delivered by this project?
>      [X] Yes
>      [ ] No - continue with next section (section 3.3)
>
>      Are 64-bit versions of the libraries being delivered?
>      [X] Yes
>      [ ] No - ARC review required
>          Since these are Java jar libraries, there are no separate  
> 64 bit jars.
>
>      Are static versions of the libraries being delivered?
>      [ ] Yes - ARC review required
>      [X] No
>
>  3.3 Services and the /etc Directory
>      (see http://opensolaris.org/os/community/arc/policies/SMF- 
> policy/)
>      Does the project integrate anything into /etc/init.d or /etc/ 
> rc?.d?
>      [ ] Yes - ARC review required
>      [X] No
>
>      Does the project integrate any new entries into /etc/inittab or
>      /etc/inetd.conf?
>      [ ] Yes - ARC review required
>      [X] No
>
>      Does the project integrate any private non-public files into / 
> etc/default
>      or /etc/ configuration files?
>      [ ] Yes - ARC review required
>      [X] No
>
>      Does the service manifests method context grant rights above that
>      of the noaccess user and basic privilege set?
>      [ ] Yes - ARC review required
>      [X] No
>
>  3.4 Security
>    3.4.1 Secure By Default
>      (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ 
>  for details)
>      (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ 
>  for details)
>      (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ 
>  for
>       addtional details)
>      Are there any network services provided by this project?
>      [ ] Yes
>      [X] No - continue with the next section (section 3.4.2)
>
>      Are network services enabled by default?
>      [ ] Yes - ARC review required
>      [ ] No
>      [ ] N/A
>
>      Are network services automatically enabled by the project  
> during installation?
>      [ ] Yes - ARC review required
>      [ ] No
>      [ ] N/A
>
>      Are inbound network communications denied by default?
>      [ ] Yes
>      [ ] No - ARC review required
>      [ ] N/A
>
>      Is inbound data checked to prevent content-based attacks?
>      [ ] Yes
>      [ ] No - ARC review required
>      [ ] N/A
>
>      Is the outbound receiver authenticated?
>      [ ] Yes
>      [ ] No - ARC review required
>      [ ] N/A
>
>      Is the receiver authenticated prior to receiving any sensitive  
> outbound communication?
>      [ ] Yes
>      [ ] No - ARC review required
>      [ ] N/A
>
>    3.4.2 Authorization
>      (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ 
>  and
> 	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ 
>  and
> 	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/
>           for details)
>      Are there any setuid/setgid privileged binaries in the project?
>      [ ] Yes - ARC review required
>      [X] No - continue with next section (section 3.4.3)
>
>      If yes then are the setuid/setgid privileges handled by the use  
> of roles?
>      [ ] Yes
>      [ ] No - ARC review required
>
>    3.4.3 Auditing
>      (see http://opensolaris.org/os/community/arc/policies/audit-policy/ 
>  for details)
>      (see http://opensolaris.org/os/community/arc/caselog/2003/397  
> for details)
>      Does this component contain administrative or security  
> enforcing software?
>      [ ] Yes - ARC review required
>      [X] No - continue to next section (section 3.4.4)
>
>      (see http://opensolaris.org/os/community/arc/caselog/2003/397  
> for details)
>      Do the components create audit logs detailing what took place  
> including what event
>      took place, who was involved, when the event took place?
>      [ ] Yes - ARC contract and Audit project team review required
>      [ ] No - ARC review required
>
>
>    3.4.4 Authentication
>      (see http://opensolaris.org/os/community/arc/policies/PAM/)
>      Do the components contain any authentication code?
>      [ ] Yes
>      [X] No - continue to next section (section 3.4.5)
>
>      If yes do the components use PAM (plugable authentication  
> modules) for authentication?
>      [ ] Yes
>      [ ] No - ARC review required
>
>      If yes is a single PAM session maintained during authentication?
>      [ ] Yes
>      [ ] No - ARC review required
>
>      If yes are the components sufficiently privileged to allow the  
> requested
>      operations (authentication, password change, process credential  
> manipulation,
>      audit state initialization)?
>      [ ] Yes - briefly describe below
>      [ ] No - ARC review required
>
>    3.4.5 Passwords
>      (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ 
>  and
>           http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ 
>  for details)
>      Do any of the components for the project deal with passwords?
>      [ ] Yes
>      [X] No - continue to next section (section 3.4.6)
>
>      If yes are these passwords entered via the CLI or environment?
>      [ ] Yes - ARC review required
>      [ ] No
>
>      Are passwords stored within the file system for the component?
>      [ ] Yes
>      [ ] No - continue to next section (section 3.4.6)
>
>      If yes are the permissions on the file such to protect exposing  
> the password(s)?
>      [ ] Yes
>      [ ] No - ARC review required
>
>    3.4.6 General Security Questions
>      (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ 
>  for details)
>      Are there any network protocols used by this project?
>      [ ] Yes
>      [X] No - continue with the next section (section 3.5)
>
>      Do the components use standard network protocols?
>      [ ] Yes
>      [ ] No - ARC review required
>
>      Do network services for the project make decisions based upon  
> user, host or
>      service identities?
>      [ ] Yes - explain below
>      [ ] No
>      [ ] N/A
>
>      Do the components make use of secret information during  
> authentication and/or
>      authorization?
>      [ ] Yes - explain below
>      [ ] No
>      [ ] N/A
>
>  3.5 Networking
>      Do the components access the network?
>      [ ] Yes
>      [X] No - continue with the next section (section 3.6)
>
>      If yes do the components support IPv6?
>      [ ] Yes
>      [ ] No - ARC review required
>
>  3.6 Core Solaris Components
>      Do the components of this project compete with or duplicate core
>      Solaris components?
>      [ ] Yes - ARC review required
>      [X] No
>
>      Examples of Core Solaris Components include but are not limited  
> to:
>
>        Secure By Default
>        Authorizations
>        PAM -- Plugable Authentication Module
>        Privilege
>        PRM -- Process Rights Management -- Privilege
>        Audit
>        xVm -- Virtualization
>        zones / Solaris Containers
>        PRM -- Process Rights Management
>        RBAC -- Role Based Access Control
>        TX / Trusted Extensions
>        ZFS
>        SMF -- Service Management Facility
>        FMA -- Fault Management Architecture
>        SCF -- Smart Card Facility
>        IPsec
>
> 4.0 Interfaces
>
> 	See project proposal.
>        Javadocs are here:
> 		https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html
> Introduction to Library Functions                         jaxb(3)
>
> NAME
>     jaxb - Java Architecture  for  XML  Binding  is  a  standard
>     extension to the Java platform.
>
> SYNOPSIS
>     Add relevant jaxb jar to the classpath
>
> DESCRIPTION
>     JAXB is an acronym derived from Java  Architecture  for  XML
>     Binding.  It constitutes a convenient framework for process-
>     ing XML documents, providing significant  benefits  as  com-
>     pared  to  previously available methods such as the one fol-
>     lowing the Document Object Model (DOM).In the DOM  approach,
>     the  parser  creates  a  tree of objects that represents the
>     content and organization of data in the document. The appli-
>     cation  can  then  navigate  through  the  tree in memory to
>     access the data it needs. DOM data, however, is contained in
>     objects  of  a  single  type,  linked  according  to the XML
>     document's structure, with individual node objects  contain-
>     ing  an  element, an attribute, a CDATA section, etc. Values
>     are invariably provided  as  strings.JAXB  provides  a  con-
>     venient  way  to  process  XML content using Java objects by
>     binding its XML schema to Java representation.
>
>     For  more  details   about   Java   Architecture   for   XML
>     Binding(JAXB), please see
>     https://jaxb.dev.java.net web page.
>
> FILES
>     By   default,   all   jaxb   jars    are   installed    into
>     /usr/share/lib/java  directory.  For more details about jars
>     installed by jaxb, please see
>     https://jaxb.dev.java.net/nonav/2.1.10/docs/ReleaseNotes.html
>
>     The XML binding compiler can be launched using the  xjc  tool
>     in the bin directory /usr/bin
>     The schema generator can be  launched using the xjc-schemagen
>     tool in the bin directory /usr/bin
>     For more details on using the tools, please see
>     https://jaxb.dev.java.net/nonav/2.1.10/docs
>
>     HTML-based documentation is located in jaxb's doc directory,
>     /usr/share/doc/jaxb.
>
> ENVIRONMENT
>     JAVA_HOME variable must point to the directory where Java is
>     installed.
>
> SunOS 5.10                Last change:                          1
>
> Introduction to Library Functions                         jaxb(3)
>
> ATTRIBUTES
>     See attributes(5) for descriptions of the  following  attri-
>     butes:
>
>     _______________________________________
>    |   ATTRIBUTE TYPE   |  ATTRIBUTE VALUE|
>    |____________________|_________________|
>    | Availability       |  SUNWjaxb       |
>    |____________________|_________________|
>    | Interface Stability|  Uncommitted    |
>    |____________________|_________________|
>
> NOTES
>     Source for jaxb is available on http://opensolaris.org.
>
> SunOS 5.10                Last change:                          2

  Arieh Markel                           Sun Microsystems, Inc.
  xVM - Virtualization Management        9 Hamenofim St. 8th Floor. MS  
ETLV04
  e-mail: arieh.markel@sun.COM           Herzliya Pituach, Israel
  http://blogs.sun.com/arieh             Phone:  +972-9-971-1291 (70)  
x12291
                                         Mobile: +972-54-238-2771





From Alan.Coopersmith@sun.com Wed Apr 15 07:32:42 2009
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FEWfUm020570
	for ; Wed, 15 Apr 2009 07:32:41 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3FEWeu4028697
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 15 Apr 2009 07:32:41 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI50022HCEGTI00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 15 Apr 2009 07:32:40 -0700 (PDT)
Received: from sca-es-mail-2.sun.com ([192.18.43.133])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI500FTJCEFWB90@nwk-avmta-1.sfbay.Sun.COM> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed,
 15 Apr 2009 07:32:39 -0700 (PDT)
Received: from fe-sfbay-09.sun.com ([192.18.43.129])
	by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n3FEWdIl027288	for
 ; Wed, 15 Apr 2009 07:32:39 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI500H00C0OA800@fe-sfbay-09.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 15 Apr 2009 07:32:39 -0700 (PDT)
Received: from [10.6.102.118] ([unknown] [10.6.102.118])
 by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KI500DS9CE4O5A0@fe-sfbay-09.sun.com>;
 Wed, 15 Apr 2009 07:32:28 -0700 (PDT)
Date: Wed, 15 Apr 2009 07:32:28 -0700
From: Alan Coopersmith 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <49E5391F.5020102@sun.com>
Sender: Alan.Coopersmith@sun.com
To: "Mark A. Carlson" 
Cc: Margot Miller ,
        Mark Carlson , Arvind.Samptur@sun.com,
        Bharath.Madakatte@sun.com, LSARC-ext@sun.com
Message-id: <49E5EFFC.2060008@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
X-Enigmail-Version: 0.95.1
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E5184F.9040905@sun.com> <49E52B96.9050704@sun.com>
 <49E52D3D.6030007@sun.com> <49E5391F.5020102@sun.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071119)
Status: RO
Content-Length: 5181

At least before build 110, JDK 1.5 and earlier couldn't run on OpenSolaris
at all - I haven't checked to see if they can run now that the Motif libraries
are provided or if they're missing other dependencies, but we certainly haven't
been catering to pre-JDK 6 projects in the OS bundled components.

	-Alan Coopersmith-           alan.coopersmith@sun.com
	 Sun Microsystems, Inc. - X Window System Engineering

Mark A. Carlson wrote:
> Some projects haven't moved to JDK 6 yet and we don't want
> to wait for those upstream communities to catch up.
> 
> -- mark
> 
> Alan Coopersmith wrote:
>> Then why are we doing this project at all, since JDK 1.6 is already
>> integrated and no earlier versions are provided on OpenSolaris?
>>
>> 	-alan-
>>
>> Mark A. Carlson wrote:
>>   
>>> I believe that JDK 6 and above have JAXB integrated
>>> so you only need it if you have JDK 1.5
>>>
>>> --- mark
>>>
>>> Margot Miller wrote:
>>>     
>>>> Does this really depend upon JDK 1.5 or just the latest JDK
>>>> on the system?
>>>>
>>>> Thanks
>>>> Margot
>>>>
>>>>
>>>> Mark Carlson wrote:
>>>>       
>>>>> I am sponsoring this familiarity case for Bharath Kumar, requesting
>>>>> minor binding and timing out 04/20/2009.
>>>>>
>>>>> -- mark
>>>>>
>>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
>>>>> This information is Copyright 2009 Sun Microsystems
>>>>> 1. Introduction
>>>>>     1.1. Project/Component Working Name:
>>>>>      JAXB
>>>>>     1.2. Name of Document Author/Supplier:
>>>>>      Author:  Bharath Kumar
>>>>>     1.3  Date of This Document:
>>>>>     13 April, 2009
>>>>>
>>>>> 2. Project Summary
>>>>>    2.1 Project Description
>>>>>        This project introduces the package of Jaxb2.1 into the SFW
>>>>> consolidation.
>>>>>
>>>>> 4. Technical Description:
>>>>>      Java Architecture for XML Binding (JAXB) provides an API and
>>>>> tool that allow automatic two-way mapping between XML documents and
>>>>> Java objects. With a given Document Type Definition (DTD) and a
>>>>> schema definition, the JAXB compiler can generate a set of Java
>>>>> classes that allow developers to build applications that can read,
>>>>> manipulate and recreate XML documents without writing any logic to
>>>>> process XML elements.
>>>>>
>>>>> 5. Interfaces
>>>>>
>>>>>    Exported interfaces
>>>>>    -------------------
>>>>>     Interface Name                Classification          Comments
>>>>>     ---------------------------         ----------------   
>>>>> ---------------------------
>>>>>     SUNWJaxb                                    Uncommitted        
>>>>> Jaxb Package
>>>>>     Jaxb API                       Uncommitted            Jaxb Classes
>>>>>     JSR ID 222                                 
>>>>> Committed               Java Specification Requests
>>>>>     /usr/share/lib/java/jaxb-impl.jar            
>>>>> Uncommitted              Jaxb runtime jar
>>>>>     /usr/share/lib/java/jaxb1-impl.jar            
>>>>> Uncommitted              Jaxb runtime jar
>>>>>     /usr/share/lib/java/jaxb-api.jar            
>>>>> Uncommitted              Jaxb runtime jar
>>>>>     /usr/share/lib/java/jsr173_1.0_api.jar        
>>>>> Uncommitted              Jaxb runtime jar
>>>>>     /usr/share/lib/java/jaxb-xjc.jar            
>>>>> Uncommitted              Jaxb compiler jar
>>>>>     /usr/bin/schemagen.sh                       
>>>>> Uncommitted              Jaxb schema generation script
>>>>>     /usr/bin/xjc.sh                            
>>>>> Uncommitted              Jaxb script to start xjc
>>>>>     /usr/share/doc/jaxb                 uncommitted             Jaxb
>>>>> doc directory
>>>>>     /usr/share/man/man3/jaxb.3                 
>>>>> Uncommitted             Manpage
>>>>>       4.2 Imported Interfaces
>>>>>     Interface Name        Classification           Comments
>>>>>     ------------------------    ------------------     
>>>>> --------------------------
>>>>>     jdk1.5                     committed        Java Development Kit
>>>>>     activation.jar              Uncommitted        JavaBeans
>>>>> Activation Framework
>>>>>
>>>>>     JSr details are available here:        
>>>>> http://jcp.org/en/jsr/detail?id=222
>>>>>     Javadocs are available here :        
>>>>> https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html
>>>>>
>>>>> 6. Resources and Schedule
>>>>>     6.4. Steering Committee requested information
>>>>>        6.4.1. Consolidation C-team Name:
>>>>>         SFW
>>>>>     6.5. ARC review type: FastTrack
>>>>>     6.6. ARC Exposure: open
>>>>>
>>>>> _______________________________________________
>>>>> opensolaris-arc mailing list
>>>>> opensolaris-arc@opensolaris.org
>>>>>   
>>>>>         
>>>> _______________________________________________
>>>> opensolaris-arc mailing list
>>>> opensolaris-arc@opensolaris.org
>>>>       
>>> -- 
>>>  	* Mark A. Carlson *
>>> Sr. Architect
>>>
>>> *Systems Group*
>>> Phone x69559 / 303-223-6139
>>> Email Mark.Carlson@Sun.COM
>>> 	
>>>
>>>
>>>     
>>
>>   
> 
> -- 
>  	* Mark A. Carlson *
> Sr. Architect
> 
> *Systems Group*
> Phone x69559 / 303-223-6139
> Email Mark.Carlson@Sun.COM
> 	
> 
> 



From margot.miller@sun.com Wed Apr 15 08:35:49 2009
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FFZnGV017849
	for ; Wed, 15 Apr 2009 08:35:49 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3FFZhUf014993;
	Wed, 15 Apr 2009 08:35:46 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI50070PFBM5200@brm-avmta-1.central.sun.com>; Wed,
 15 Apr 2009 09:35:46 -0600 (MDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI500EGXFBLXXC0@brm-avmta-1.central.sun.com>; Wed,
 15 Apr 2009 09:35:45 -0600 (MDT)
Received: from [10.7.250.251]
 (punchin-client-10-7-250-251.SFBay.Sun.COM [10.7.250.251])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n3FFZhDc270369; Wed, 15 Apr 2009 08:35:44 -0700 (PDT)
Date: Wed, 15 Apr 2009 08:30:53 -0700
From: Margot Miller 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <49E5391F.5020102@sun.com>
To: "Mark A. Carlson" 
Cc: Alan Coopersmith ,
        Mark Carlson , Arvind.Samptur@sun.com,
        Bharath.Madakatte@sun.com, LSARC-ext@sun.com
Message-id: <49E5FDAD.9070603@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E5184F.9040905@sun.com> <49E52B96.9050704@sun.com>
 <49E52D3D.6030007@sun.com> <49E5391F.5020102@sun.com>
User-Agent: Thunderbird 2.0b1 (X11/20070115)
Status: RO
Content-Length: 4951

Mark,

Does this mean that projects that can't run with JDK 1.6
install a private local version of JDK 1.5 and then use this
JAX-B?

Do you know which projects these are? 

Thanks
Margot


Mark A. Carlson wrote:
> Some projects haven't moved to JDK 6 yet and we don't want
> to wait for those upstream communities to catch up.
>
> -- mark
>
> Alan Coopersmith wrote:
>> Then why are we doing this project at all, since JDK 1.6 is already
>> integrated and no earlier versions are provided on OpenSolaris?
>>
>> 	-alan-
>>
>> Mark A. Carlson wrote:
>>   
>>> I believe that JDK 6 and above have JAXB integrated
>>> so you only need it if you have JDK 1.5
>>>
>>> --- mark
>>>
>>> Margot Miller wrote:
>>>     
>>>> Does this really depend upon JDK 1.5 or just the latest JDK
>>>> on the system?
>>>>
>>>> Thanks
>>>> Margot
>>>>
>>>>
>>>> Mark Carlson wrote:
>>>>       
>>>>> I am sponsoring this familiarity case for Bharath Kumar, requesting
>>>>> minor binding and timing out 04/20/2009.
>>>>>
>>>>> -- mark
>>>>>
>>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
>>>>> This information is Copyright 2009 Sun Microsystems
>>>>> 1. Introduction
>>>>>     1.1. Project/Component Working Name:
>>>>>      JAXB
>>>>>     1.2. Name of Document Author/Supplier:
>>>>>      Author:  Bharath Kumar
>>>>>     1.3  Date of This Document:
>>>>>     13 April, 2009
>>>>>
>>>>> 2. Project Summary
>>>>>    2.1 Project Description
>>>>>        This project introduces the package of Jaxb2.1 into the SFW
>>>>> consolidation.
>>>>>
>>>>> 4. Technical Description:
>>>>>      Java Architecture for XML Binding (JAXB) provides an API and
>>>>> tool that allow automatic two-way mapping between XML documents and
>>>>> Java objects. With a given Document Type Definition (DTD) and a
>>>>> schema definition, the JAXB compiler can generate a set of Java
>>>>> classes that allow developers to build applications that can read,
>>>>> manipulate and recreate XML documents without writing any logic to
>>>>> process XML elements.
>>>>>
>>>>> 5. Interfaces
>>>>>
>>>>>    Exported interfaces
>>>>>    -------------------
>>>>>     Interface Name                Classification          Comments
>>>>>     ---------------------------         ----------------   
>>>>> ---------------------------
>>>>>     SUNWJaxb                                    Uncommitted        
>>>>> Jaxb Package
>>>>>     Jaxb API                       Uncommitted            Jaxb Classes
>>>>>     JSR ID 222                                 
>>>>> Committed               Java Specification Requests
>>>>>     /usr/share/lib/java/jaxb-impl.jar            
>>>>> Uncommitted              Jaxb runtime jar
>>>>>     /usr/share/lib/java/jaxb1-impl.jar            
>>>>> Uncommitted              Jaxb runtime jar
>>>>>     /usr/share/lib/java/jaxb-api.jar            
>>>>> Uncommitted              Jaxb runtime jar
>>>>>     /usr/share/lib/java/jsr173_1.0_api.jar        
>>>>> Uncommitted              Jaxb runtime jar
>>>>>     /usr/share/lib/java/jaxb-xjc.jar            
>>>>> Uncommitted              Jaxb compiler jar
>>>>>     /usr/bin/schemagen.sh                       
>>>>> Uncommitted              Jaxb schema generation script
>>>>>     /usr/bin/xjc.sh                            
>>>>> Uncommitted              Jaxb script to start xjc
>>>>>     /usr/share/doc/jaxb                 uncommitted             Jaxb
>>>>> doc directory
>>>>>     /usr/share/man/man3/jaxb.3                 
>>>>> Uncommitted             Manpage
>>>>>       4.2 Imported Interfaces
>>>>>     Interface Name        Classification           Comments
>>>>>     ------------------------    ------------------     
>>>>> --------------------------
>>>>>     jdk1.5                     committed        Java Development Kit
>>>>>     activation.jar              Uncommitted        JavaBeans
>>>>> Activation Framework
>>>>>
>>>>>     JSr details are available here:        
>>>>> http://jcp.org/en/jsr/detail?id=222
>>>>>     Javadocs are available here :        
>>>>> https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html
>>>>>
>>>>> 6. Resources and Schedule
>>>>>     6.4. Steering Committee requested information
>>>>>        6.4.1. Consolidation C-team Name:
>>>>>         SFW
>>>>>     6.5. ARC review type: FastTrack
>>>>>     6.6. ARC Exposure: open
>>>>>
>>>>> _______________________________________________
>>>>> opensolaris-arc mailing list
>>>>> opensolaris-arc@opensolaris.org
>>>>>   
>>>>>         
>>>> _______________________________________________
>>>> opensolaris-arc mailing list
>>>> opensolaris-arc@opensolaris.org
>>>>       
>>> -- 
>>>  	* Mark A. Carlson *
>>> Sr. Architect
>>>
>>> *Systems Group*
>>> Phone x69559 / 303-223-6139
>>> Email Mark.Carlson@Sun.COM
>>> 	
>>>
>>>
>>>     
>>
>>   
>
> -- 
>  	* Mark A. Carlson *
> Sr. Architect
>
> *Systems Group*
> Phone x69559 / 303-223-6139
> Email Mark.Carlson@Sun.COM
> 	
>
>


From Mark.Carlson@sun.com Wed Apr 15 11:41:03 2009
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FIf38W028071
	for ; Wed, 15 Apr 2009 11:41:03 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3FIf2dO052739
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 15 Apr 2009 12:41:02 -0600 (MDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI500207NWE1900@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 15 Apr 2009 12:41:02 -0600 (MDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI500LHBNWDT340@brm-avmta-1.central.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed,
 15 Apr 2009 12:41:01 -0600 (MDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3FIf1mo017463	for
 ; Wed, 15 Apr 2009 18:41:01 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI500900N1UJY00@mail-amer.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 15 Apr 2009 12:41:01 -0600 (MDT)
Received: from boulder-dhcp-216.Central.Sun.COM ([unknown] [172.20.24.216])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KI500IQCNVVPYF0@mail-amer.sun.com>; Wed,
 15 Apr 2009 12:40:43 -0600 (MDT)
Date: Wed, 15 Apr 2009 12:40:40 -0600
From: "Mark A. Carlson" 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <49E5FDAD.9070603@sun.com>
Sender: Mark.Carlson@sun.com
To: Margot Miller 
Cc: Alan Coopersmith ,
        Mark Carlson , Arvind.Samptur@sun.com,
        Bharath.Madakatte@sun.com, LSARC-ext@sun.com
Message-id: <49E62A28.9070907@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_SC1nllNFYtnhjskE8pA1uA)"
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E5184F.9040905@sun.com> <49E52B96.9050704@sun.com>
 <49E52D3D.6030007@sun.com> <49E5391F.5020102@sun.com>
 <49E5FDAD.9070603@sun.com>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
Status: RO
Content-Length: 15588

This is a multi-part message in MIME format.

--Boundary_(ID_SC1nllNFYtnhjskE8pA1uA)
Content-type: text/plain; format=flowed; charset=UTF-8
Content-transfer-encoding: 7BIT

I think you would just do "pkg install java-dev" or make your package 
depend
on this.

My understanding of the best practice is that you pick the lowest Java 
version you
can reasonably support. Then support that version *and above* going forward.
If everybody does this, the chances that the customer would:

a) be forced to upgrade their Java version, and
b) break Java apps because of such an upgrade

are greatly minimized.

In addition, nobody should be forced to carry around their own JVM to 
install in
any case.

-- mark

Margot Miller wrote:
> Mark,
>
> Does this mean that projects that can't run with JDK 1.6
> install a private local version of JDK 1.5 and then use this
> JAX-B?
>
> Do you know which projects these are?
> Thanks
> Margot
>
>
> Mark A. Carlson wrote:
>> Some projects haven't moved to JDK 6 yet and we don't want
>> to wait for those upstream communities to catch up.
>>
>> -- mark
>>
>> Alan Coopersmith wrote:
>>> Then why are we doing this project at all, since JDK 1.6 is already
>>> integrated and no earlier versions are provided on OpenSolaris?
>>>
>>>     -alan-
>>>
>>> Mark A. Carlson wrote:
>>>  
>>>> I believe that JDK 6 and above have JAXB integrated
>>>> so you only need it if you have JDK 1.5
>>>>
>>>> --- mark
>>>>
>>>> Margot Miller wrote:
>>>>    
>>>>> Does this really depend upon JDK 1.5 or just the latest JDK
>>>>> on the system?
>>>>>
>>>>> Thanks
>>>>> Margot
>>>>>
>>>>>
>>>>> Mark Carlson wrote:
>>>>>      
>>>>>> I am sponsoring this familiarity case for Bharath Kumar, requesting
>>>>>> minor binding and timing out 04/20/2009.
>>>>>>
>>>>>> -- mark
>>>>>>
>>>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
>>>>>> This information is Copyright 2009 Sun Microsystems
>>>>>> 1. Introduction
>>>>>>     1.1. Project/Component Working Name:
>>>>>>      JAXB
>>>>>>     1.2. Name of Document Author/Supplier:
>>>>>>      Author:  Bharath Kumar
>>>>>>     1.3  Date of This Document:
>>>>>>     13 April, 2009
>>>>>>
>>>>>> 2. Project Summary
>>>>>>    2.1 Project Description
>>>>>>        This project introduces the package of Jaxb2.1 into the SFW
>>>>>> consolidation.
>>>>>>
>>>>>> 4. Technical Description:
>>>>>>      Java Architecture for XML Binding (JAXB) provides an API and
>>>>>> tool that allow automatic two-way mapping between XML documents and
>>>>>> Java objects. With a given Document Type Definition (DTD) and a
>>>>>> schema definition, the JAXB compiler can generate a set of Java
>>>>>> classes that allow developers to build applications that can read,
>>>>>> manipulate and recreate XML documents without writing any logic to
>>>>>> process XML elements.
>>>>>>
>>>>>> 5. Interfaces
>>>>>>
>>>>>>    Exported interfaces
>>>>>>    -------------------
>>>>>>     Interface Name                Classification          Comments
>>>>>>     ---------------------------         ----------------   
>>>>>> ---------------------------
>>>>>>     SUNWJaxb                                    
>>>>>> Uncommitted        Jaxb Package
>>>>>>     Jaxb API                       Uncommitted            Jaxb 
>>>>>> Classes
>>>>>>     JSR ID 222                                 
>>>>>> Committed               Java Specification Requests
>>>>>>     /usr/share/lib/java/jaxb-impl.jar            
>>>>>> Uncommitted              Jaxb runtime jar
>>>>>>     /usr/share/lib/java/jaxb1-impl.jar            
>>>>>> Uncommitted              Jaxb runtime jar
>>>>>>     /usr/share/lib/java/jaxb-api.jar            
>>>>>> Uncommitted              Jaxb runtime jar
>>>>>>     /usr/share/lib/java/jsr173_1.0_api.jar        
>>>>>> Uncommitted              Jaxb runtime jar
>>>>>>     /usr/share/lib/java/jaxb-xjc.jar            
>>>>>> Uncommitted              Jaxb compiler jar
>>>>>>     /usr/bin/schemagen.sh                       
>>>>>> Uncommitted              Jaxb schema generation script
>>>>>>     /usr/bin/xjc.sh                            
>>>>>> Uncommitted              Jaxb script to start xjc
>>>>>>     /usr/share/doc/jaxb                 uncommitted             Jaxb
>>>>>> doc directory
>>>>>>     /usr/share/man/man3/jaxb.3                 
>>>>>> Uncommitted             Manpage
>>>>>>       4.2 Imported Interfaces
>>>>>>     Interface Name        Classification           Comments
>>>>>>     ------------------------    ------------------     
>>>>>> --------------------------
>>>>>>     jdk1.5                     committed        Java Development Kit
>>>>>>     activation.jar              Uncommitted        JavaBeans
>>>>>> Activation Framework
>>>>>>
>>>>>>     JSr details are available here:        
>>>>>> http://jcp.org/en/jsr/detail?id=222
>>>>>>     Javadocs are available here :        
>>>>>> https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html
>>>>>>
>>>>>> 6. Resources and Schedule
>>>>>>     6.4. Steering Committee requested information
>>>>>>        6.4.1. Consolidation C-team Name:
>>>>>>         SFW
>>>>>>     6.5. ARC review type: FastTrack
>>>>>>     6.6. ARC Exposure: open
>>>>>>
>>>>>> _______________________________________________
>>>>>> opensolaris-arc mailing list
>>>>>> opensolaris-arc@opensolaris.org
>>>>>>           
>>>>> _______________________________________________
>>>>> opensolaris-arc mailing list
>>>>> opensolaris-arc@opensolaris.org
>>>>>       
>>>> -- 
>>>>      * Mark A. Carlson *
>>>> Sr. Architect
>>>>
>>>> *Systems Group*
>>>> Phone x69559 / 303-223-6139
>>>> Email Mark.Carlson@Sun.COM
>>>>     
>>>>
>>>>
>>>>     
>>>
>>>   
>>
>> -- 
>>      * Mark A. Carlson *
>> Sr. Architect
>>
>> *Systems Group*
>> Phone x69559 / 303-223-6139
>> Email Mark.Carlson@Sun.COM
>>     
>>
>>
>

-- 
 	* Mark A. Carlson *
Sr. Architect

*Systems Group*
Phone x69559 / 303-223-6139
Email Mark.Carlson@Sun.COM
	



--Boundary_(ID_SC1nllNFYtnhjskE8pA1uA)
Content-type: text/html; charset=UTF-8
Content-transfer-encoding: 8BIT




  


I think you would just do "pkg install java-dev" or make your package
depend 

on this.



My understanding of the best practice is that you pick the lowest Java
version you

can reasonably support. Then support that version *and above* going
forward.

If everybody does this, the chances that the customer would:



a) be forced to upgrade their Java version, and

b) break Java apps because of such an upgrade



are greatly minimized.



In addition, nobody should be forced to carry around their own JVM to
install in

any case.



-- mark



Margot Miller wrote:

Mark,
  

  

Does this mean that projects that can't run with JDK 1.6
  

install a private local version of JDK 1.5 and then use this
  

JAX-B?
  

  

Do you know which projects these are? 

Thanks
  

Margot
  

  

  

Mark A. Carlson wrote:
  

  
Some projects haven't moved to JDK 6 yet and
we don't want
    

to wait for those upstream communities to catch up.
    

    

-- mark
    

    

Alan Coopersmith wrote:
    

    
Then why are we doing this project at all,
since JDK 1.6 is already
      

integrated and no earlier versions are provided on OpenSolaris?
      

      

    -alan-
      

      

Mark A. Carlson wrote:
      

 
      
I believe that JDK 6 and above have JAXB
integrated
        

so you only need it if you have JDK 1.5
        

        

--- mark
        

        

Margot Miller wrote:
        

   
        
Does this really depend upon JDK 1.5 or
just the latest JDK
          

on the system?
          

          

Thanks
          

Margot
          

          

          

Mark Carlson wrote:
          

     
          
I am sponsoring this familiarity case
for Bharath Kumar, requesting
            

minor binding and timing out 04/20/2009.
            

            

-- mark
            

            

Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
            

This information is Copyright 2009 Sun Microsystems
            

1. Introduction
            

    1.1. Project/Component Working Name:
            

     JAXB
            

    1.2. Name of Document Author/Supplier:
            

     Author:  Bharath Kumar
            

    1.3  Date of This Document:
            

    13 April, 2009
            

            

2. Project Summary
            

   2.1 Project Description
            

       This project introduces the package of Jaxb2.1 into the SFW
            

consolidation.
            

            

4. Technical Description:
            

     Java Architecture for XML Binding (JAXB) provides an API and
            

tool that allow automatic two-way mapping between XML documents and
            

Java objects. With a given Document Type Definition (DTD) and a
            

schema definition, the JAXB compiler can generate a set of Java
            

classes that allow developers to build applications that can read,
            

manipulate and recreate XML documents without writing any logic to
            

process XML elements.
            

            

5. Interfaces
            

            

   Exported interfaces
            

   -------------------
            

    Interface Name                Classification          Comments
            

    ---------------------------         ----------------  
---------------------------
            

    SUNWJaxb                                    Uncommitted        Jaxb
Package
            

    Jaxb API                       Uncommitted            Jaxb Classes
            

    JSR ID 222                                 Committed              
Java Specification Requests
            

    /usr/share/lib/java/jaxb-impl.jar           
Uncommitted              Jaxb runtime jar
            

    /usr/share/lib/java/jaxb1-impl.jar           
Uncommitted              Jaxb runtime jar
            

    /usr/share/lib/java/jaxb-api.jar           
Uncommitted              Jaxb runtime jar
            

    /usr/share/lib/java/jsr173_1.0_api.jar       
Uncommitted              Jaxb runtime jar
            

    /usr/share/lib/java/jaxb-xjc.jar           
Uncommitted              Jaxb compiler jar
            

    /usr/bin/schemagen.sh                      
Uncommitted              Jaxb schema generation script
            

    /usr/bin/xjc.sh                            Uncommitted             
Jaxb script to start xjc
            

    /usr/share/doc/jaxb                 uncommitted             Jaxb
            

doc directory
            

    /usr/share/man/man3/jaxb.3                 Uncommitted            
Manpage
            

      4.2 Imported Interfaces
            

    Interface Name        Classification           Comments
            

    ------------------------    ------------------    
--------------------------
            

    jdk1.5                     committed        Java Development Kit
            

    activation.jar              Uncommitted        JavaBeans
            

Activation Framework
            

            

    JSr details are available here:       
http://jcp.org/en/jsr/detail?id=222
            

    Javadocs are available here :       
https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html
            

            

6. Resources and Schedule
            

    6.4. Steering Committee requested information
            

       6.4.1. Consolidation C-team Name:
            

        SFW
            

    6.5. ARC review type: FastTrack
            

    6.6. ARC Exposure: open
            

            

_______________________________________________
            

opensolaris-arc mailing list
            

opensolaris-arc@opensolaris.org
            

          

_______________________________________________
          

opensolaris-arc mailing list
          

opensolaris-arc@opensolaris.org
          

      

-- 

<http://www.sun.com>     * Mark A. Carlson *
        

Sr. Architect
        

        

*Systems Group*
        

Phone x69559 / 303-223-6139
        

Email Mark.Carlson@Sun.COM
        

    
        

        

        

    

      

  

    

-- 

<http://www.sun.com>     * Mark A. Carlson *
    

Sr. Architect
    

    

*Systems Group*
    

Phone x69559 / 303-223-6139
    

Email Mark.Carlson@Sun.COM
    

    
    

    

    

  

  






-- 




  
    

      
       Mark A. Carlson 

Sr. Architect

      

      Systems Group

Phone x69559 / 303-223-6139

Email Mark.Carlson@Sun.COM

      		
      
    

  












--Boundary_(ID_SC1nllNFYtnhjskE8pA1uA)--

From margot.miller@sun.com Wed Apr 15 16:03:33 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FN3VRL001546
	for ; Wed, 15 Apr 2009 16:03:32 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3FN3JDD029218;
	Thu, 16 Apr 2009 00:03:25 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI600I1701O7600@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 15 Apr 2009 16:03:24 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI6006FB01O0CC0@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 15 Apr 2009 16:03:24 -0700 (PDT)
Received: from [10.7.250.251]
 (punchin-client-10-7-250-251.SFBay.Sun.COM [10.7.250.251])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n3FN3K3C361592; Wed, 15 Apr 2009 16:03:21 -0700 (PDT)
Date: Wed, 15 Apr 2009 15:58:30 -0700
From: Margot Miller 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <49E62A28.9070907@sun.com>
To: "Mark A. Carlson" 
Cc: Alan Coopersmith ,
        Mark Carlson , Arvind.Samptur@sun.com,
        Bharath.Madakatte@sun.com, LSARC-ext@sun.com
Message-id: <49E66696.8080205@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <49E5184F.9040905@sun.com> <49E52B96.9050704@sun.com>
 <49E52D3D.6030007@sun.com> <49E5391F.5020102@sun.com>
 <49E5FDAD.9070603@sun.com> <49E62A28.9070907@sun.com>
User-Agent: Thunderbird 2.0b1 (X11/20070115)
Status: RO
Content-Length: 6342


Can the project team confirm that jaxb is already in JDK 1.6.
I didn't find a man page for it on a system with build 110.

How does the customer know that they need JDK 1.5 for JAXB?
Is this documented?

Is it the JES products that need JAXB with JDK 1.5?

Thanks
Margot




Mark A. Carlson wrote:
> I think you would just do "pkg install java-dev" or make your package 
> depend
> on this.
>
> My understanding of the best practice is that you pick the lowest Java 
> version you
> can reasonably support. Then support that version *and above* going 
> forward.
> If everybody does this, the chances that the customer would:
>
> a) be forced to upgrade their Java version, and
> b) break Java apps because of such an upgrade
>
> are greatly minimized.
>
> In addition, nobody should be forced to carry around their own JVM to 
> install in
> any case.
>
> -- mark
>
> Margot Miller wrote:
>> Mark,
>>
>> Does this mean that projects that can't run with JDK 1.6
>> install a private local version of JDK 1.5 and then use this
>> JAX-B?
>>
>> Do you know which projects these are?
>> Thanks
>> Margot
>>
>>
>> Mark A. Carlson wrote:
>>> Some projects haven't moved to JDK 6 yet and we don't want
>>> to wait for those upstream communities to catch up.
>>>
>>> -- mark
>>>
>>> Alan Coopersmith wrote:
>>>> Then why are we doing this project at all, since JDK 1.6 is already
>>>> integrated and no earlier versions are provided on OpenSolaris?
>>>>
>>>>     -alan-
>>>>
>>>> Mark A. Carlson wrote:
>>>>  
>>>>> I believe that JDK 6 and above have JAXB integrated
>>>>> so you only need it if you have JDK 1.5
>>>>>
>>>>> --- mark
>>>>>
>>>>> Margot Miller wrote:
>>>>>    
>>>>>> Does this really depend upon JDK 1.5 or just the latest JDK
>>>>>> on the system?
>>>>>>
>>>>>> Thanks
>>>>>> Margot
>>>>>>
>>>>>>
>>>>>> Mark Carlson wrote:
>>>>>>      
>>>>>>> I am sponsoring this familiarity case for Bharath Kumar, requesting
>>>>>>> minor binding and timing out 04/20/2009.
>>>>>>>
>>>>>>> -- mark
>>>>>>>
>>>>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
>>>>>>> This information is Copyright 2009 Sun Microsystems
>>>>>>> 1. Introduction
>>>>>>>     1.1. Project/Component Working Name:
>>>>>>>      JAXB
>>>>>>>     1.2. Name of Document Author/Supplier:
>>>>>>>      Author:  Bharath Kumar
>>>>>>>     1.3  Date of This Document:
>>>>>>>     13 April, 2009
>>>>>>>
>>>>>>> 2. Project Summary
>>>>>>>    2.1 Project Description
>>>>>>>        This project introduces the package of Jaxb2.1 into the SFW
>>>>>>> consolidation.
>>>>>>>
>>>>>>> 4. Technical Description:
>>>>>>>      Java Architecture for XML Binding (JAXB) provides an API and
>>>>>>> tool that allow automatic two-way mapping between XML documents and
>>>>>>> Java objects. With a given Document Type Definition (DTD) and a
>>>>>>> schema definition, the JAXB compiler can generate a set of Java
>>>>>>> classes that allow developers to build applications that can read,
>>>>>>> manipulate and recreate XML documents without writing any logic to
>>>>>>> process XML elements.
>>>>>>>
>>>>>>> 5. Interfaces
>>>>>>>
>>>>>>>    Exported interfaces
>>>>>>>    -------------------
>>>>>>>     Interface Name                Classification          Comments
>>>>>>>     ---------------------------         ----------------   
>>>>>>> ---------------------------
>>>>>>>     SUNWJaxb                                    
>>>>>>> Uncommitted        Jaxb Package
>>>>>>>     Jaxb API                       Uncommitted            Jaxb 
>>>>>>> Classes
>>>>>>>     JSR ID 222                                 
>>>>>>> Committed               Java Specification Requests
>>>>>>>     /usr/share/lib/java/jaxb-impl.jar            
>>>>>>> Uncommitted              Jaxb runtime jar
>>>>>>>     /usr/share/lib/java/jaxb1-impl.jar            
>>>>>>> Uncommitted              Jaxb runtime jar
>>>>>>>     /usr/share/lib/java/jaxb-api.jar            
>>>>>>> Uncommitted              Jaxb runtime jar
>>>>>>>     /usr/share/lib/java/jsr173_1.0_api.jar        
>>>>>>> Uncommitted              Jaxb runtime jar
>>>>>>>     /usr/share/lib/java/jaxb-xjc.jar            
>>>>>>> Uncommitted              Jaxb compiler jar
>>>>>>>     /usr/bin/schemagen.sh                       
>>>>>>> Uncommitted              Jaxb schema generation script
>>>>>>>     /usr/bin/xjc.sh                            
>>>>>>> Uncommitted              Jaxb script to start xjc
>>>>>>>     /usr/share/doc/jaxb                 uncommitted             
>>>>>>> Jaxb
>>>>>>> doc directory
>>>>>>>     /usr/share/man/man3/jaxb.3                 
>>>>>>> Uncommitted             Manpage
>>>>>>>       4.2 Imported Interfaces
>>>>>>>     Interface Name        Classification           Comments
>>>>>>>     ------------------------    ------------------     
>>>>>>> --------------------------
>>>>>>>     jdk1.5                     committed        Java Development 
>>>>>>> Kit
>>>>>>>     activation.jar              Uncommitted        JavaBeans
>>>>>>> Activation Framework
>>>>>>>
>>>>>>>     JSr details are available here:        
>>>>>>> http://jcp.org/en/jsr/detail?id=222
>>>>>>>     Javadocs are available here :        
>>>>>>> https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/index.html
>>>>>>>
>>>>>>> 6. Resources and Schedule
>>>>>>>     6.4. Steering Committee requested information
>>>>>>>        6.4.1. Consolidation C-team Name:
>>>>>>>         SFW
>>>>>>>     6.5. ARC review type: FastTrack
>>>>>>>     6.6. ARC Exposure: open
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> opensolaris-arc mailing list
>>>>>>> opensolaris-arc@opensolaris.org
>>>>>>>           
>>>>>> _______________________________________________
>>>>>> opensolaris-arc mailing list
>>>>>> opensolaris-arc@opensolaris.org
>>>>>>       
>>>>> -- 
>>>>>      * Mark A. Carlson *
>>>>> Sr. Architect
>>>>>
>>>>> *Systems Group*
>>>>> Phone x69559 / 303-223-6139
>>>>> Email Mark.Carlson@Sun.COM
>>>>>     
>>>>>
>>>>>
>>>>>     
>>>>
>>>>   
>>>
>>> -- 
>>>      * Mark A. Carlson *
>>> Sr. Architect
>>>
>>> *Systems Group*
>>> Phone x69559 / 303-223-6139
>>> Email Mark.Carlson@Sun.COM
>>>     
>>>
>>>
>>
>
> -- 
>  	* Mark A. Carlson *
> Sr. Architect
>
> *Systems Group*
> Phone x69559 / 303-223-6139
> Email Mark.Carlson@Sun.COM
> 	
>
>


From Jyri.Virkki@sun.com Thu Apr 16 17:30:02 2009
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3H0U15i009772
	for ; Thu, 16 Apr 2009 17:30:01 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3H0Tv2f048142;
	Thu, 16 Apr 2009 18:29:59 -0600 (MDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI700503YPYED00@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 16 Apr 2009 17:29:58 -0700 (PDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI700M9BYPYO4C0@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 16 Apr 2009 17:29:58 -0700 (PDT)
Received: from dm-usca15-11.red.iplanet.com
 (host-185-56-18-192.iplanet.com [192.18.56.185] (may be forged))
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3H0TvsL018405; Fri,
 17 Apr 2009 00:29:57 +0000 (GMT)
Received: from buye.red.iplanet.com (buye [192.18.65.224])
	by dm-usca15-11.red.iplanet.com (8.11.7p1+Sun/8.11.7/IPLANET,v1.2)
 with ESMTP id n3H0TvV11928; Thu, 16 Apr 2009 17:29:57 -0700 (PDT)
Received: from buye.red.iplanet.com (localhost [127.0.0.1])
	by buye.red.iplanet.com (8.13.7+Sun/8.13.7) with ESMTP id n3H0Tvkn007057; Thu,
 16 Apr 2009 17:29:57 -0700 (PDT)
Received: (from jyri@localhost)
	by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id n3H0TvfC007056; Thu,
 16 Apr 2009 17:29:57 -0700 (PDT)
Date: Thu, 16 Apr 2009 17:29:57 -0700
From: Jyri Virkki 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
To: Mark Carlson 
Cc: LSARC-ext@sun.com, Arvind.Samptur@sun.com, Bharath.Madakatte@sun.com
Message-id: <20090417002957.GA7030@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
User-Agent: Mutt/1.5.11
Status: RO
Content-Length: 1185

>
>  2.1 Project Description
>  This project introduces the package of Jaxb2.1 into the SFW consolidation.

Reading through the thread the following still appears unadressed:

First, if this library is only relevant to JDK5, why is it being
integrated at all? OpenSolaris, AFAIK, only has JDK6 so there's no
possible consumer of this library since JDK6 already has it.

Is this case trying the address the case where user manually downloads
JDK5 tarballs and installs them in their home dir or somewhere? Seems
odd to have a system library and commands dedicated to serve a
private JDK5 install.

Aside from odd, there is the problem with the command duplication:
The system-provided JDK6 package has xjc and schemagen in
/usr/jdk/latest/bin/
but this case proposes deliver duplicate (and possibly older) copies
of the same tools into /usr/bin for JDK5 use. Since /usr/bin is more
likely to be early in the path than the java bin dir, this means if
this package is installed a user will inadvertently get the wrong
/usr/bin/[xjc|schemagen] instead of the system-delivered ones
in /usr/jdk/latest/bin/ 
That can't be right.


-- 
Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems

From Mark.Carlson@sun.com Fri Apr 17 10:24:20 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3HHOJ0b011612
	for ; Fri, 17 Apr 2009 10:24:20 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3HHOBtS016046
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 17 Apr 2009 18:24:18 +0100 (BST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI90070R9OG7400@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Fri, 17 Apr 2009 11:24:16 -0600 (MDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI900BRI9OGT5E0@brm-avmta-1.central.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri,
 17 Apr 2009 11:24:16 -0600 (MDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3HHOGdn007674	for
 ; Fri, 17 Apr 2009 17:24:16 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI900G008Z92W00@mail-amer.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Fri, 17 Apr 2009 11:24:16 -0600 (MDT)
Received: from Macintosh-335.local ([unknown] [129.150.32.57])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KI9000OS9O4G040@mail-amer.sun.com>; Fri,
 17 Apr 2009 11:24:05 -0600 (MDT)
Date: Fri, 17 Apr 2009 11:24:01 -0600
From: "Mark A. Carlson" 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <20090417002957.GA7030@sun.com>
Sender: Mark.Carlson@sun.com
To: Jyri Virkki 
Cc: Mark Carlson , Arvind.Samptur@sun.com,
        Bharath.Madakatte@sun.com, LSARC-ext@sun.com
Message-id: <49E8BB31.4000400@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_0/4hctJkYAuv+ZR/ppShVQ)"
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <20090417002957.GA7030@sun.com>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
Status: RO
Content-Length: 5015

This is a multi-part message in MIME format.

--Boundary_(ID_0/4hctJkYAuv+ZR/ppShVQ)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT



Jyri Virkki wrote:
>>  2.1 Project Description
>>  This project introduces the package of Jaxb2.1 into the SFW consolidation.
>>     
>
> Reading through the thread the following still appears unadressed:
>
> First, if this library is only relevant to JDK5, why is it being
> integrated at all? OpenSolaris, AFAIK, only has JDK6 so there's no
> possible consumer of this library since JDK6 already has it.
>   
This version of JAXB is a later version than what is in JDK 6.
We have a project that requires this version of JAXB. That project
team has chosen to support JDK 1.5 *and above* and can compile and
run with either JDK 1.5 or JDK 6 at this point as long as this
version of JAXB is also used.

> Is this case trying the address the case where user manually downloads
> JDK5 tarballs and installs them in their home dir or somewhere? Seems
> odd to have a system library and commands dedicated to serve a
> private JDK5 install.
>   
If they have 1.5 as you suggest, the other project (Wiseman - case
to be filed soon) will use this case and will work. If they use
the JDK 6 version that comes by default in OpenSolaris, it will
also work using this case.

> Aside from odd, there is the problem with the command duplication:
> The system-provided JDK6 package has xjc and schemagen in
> /usr/jdk/latest/bin/
> but this case proposes deliver duplicate (and possibly older) copies
> of the same tools into /usr/bin for JDK5 use. Since /usr/bin is more
> likely to be early in the path than the java bin dir, this means if
> this package is installed a user will inadvertently get the wrong
> /usr/bin/[xjc|schemagen] instead of the system-delivered ones
> in /usr/jdk/latest/bin/ 
> That can't be right.
>   

We will rename this case's xjc to jaxb-xjc and the xjc-schemagen to 
jaxb-schemagen so as not to conflict
if an other project wants to use the JDK6 version. We have updated the 
case materials to reflect this.

-- mark







--Boundary_(ID_0/4hctJkYAuv+ZR/ppShVQ)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT




  






Jyri Virkki wrote:


  

    
 2.1 Project Description
 This project introduces the package of Jaxb2.1 into the SFW consolidation.
    

  

  

Reading through the thread the following still appears unadressed:

First, if this library is only relevant to JDK5, why is it being
integrated at all? OpenSolaris, AFAIK, only has JDK6 so there's no
possible consumer of this library since JDK6 already has it.
  




This version of JAXB is a later version than what is in JDK 6.
We have a project that requires this version of JAXB. That project
team has chosen to support JDK 1.5 *and above* and can compile and
run with either JDK 1.5 or JDK 6 at this point as long as this
version of JAXB is also used.



  
Is this case trying the address the case where user manually downloads
JDK5 tarballs and installs them in their home dir or somewhere? Seems
odd to have a system library and commands dedicated to serve a
private JDK5 install.
  




If they have 1.5 as you suggest, the other project (Wiseman - case
to be filed soon) will use this case and will work. If they use
the JDK 6 version that comes by default in OpenSolaris, it will
also work using this case.



  
Aside from odd, there is the problem with the command duplication:
The system-provided JDK6 package has xjc and schemagen in
/usr/jdk/latest/bin/
but this case proposes deliver duplicate (and possibly older) copies
of the same tools into /usr/bin for JDK5 use. Since /usr/bin is more
likely to be early in the path than the java bin dir, this means if
this package is installed a user will inadvertently get the wrong
/usr/bin/[xjc|schemagen] instead of the system-delivered ones
in /usr/jdk/latest/bin/ 
That can't be right.
  





We will rename this case's xjc to jaxb-xjc and the xjc-schemagen to
jaxb-schemagen so as not to conflict

if an other project wants to use the JDK6 version. We have updated the
case materials to reflect this.



-- mark






















--Boundary_(ID_0/4hctJkYAuv+ZR/ppShVQ)--

From margot.miller@sun.com Mon Apr 20 11:04:43 2009
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3KI4hYu027218
	for ; Mon, 20 Apr 2009 11:04:43 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3KI4dvQ017627;
	Mon, 20 Apr 2009 11:04:40 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIE00507VJR6I00@nwk-avmta-2.sfbay.sun.com>; Mon,
 20 Apr 2009 11:04:39 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIE000GXVJRGO70@nwk-avmta-2.sfbay.sun.com>; Mon,
 20 Apr 2009 11:04:39 -0700 (PDT)
Received: from [10.7.250.251]
 (punchin-client-10-7-250-251.SFBay.Sun.COM [10.7.250.251])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n3KI4cAx783991; Mon, 20 Apr 2009 11:04:38 -0700 (PDT)
Date: Mon, 20 Apr 2009 10:59:42 -0700
From: Margot Miller 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <49E8BB31.4000400@sun.com>
To: "Mark A. Carlson" 
Cc: Jyri Virkki , Arvind.Samptur@sun.com,
        Bharath.Madakatte@sun.com, LSARC-ext@sun.com
Message-id: <49ECB80E.2050409@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <20090417002957.GA7030@sun.com> <49E8BB31.4000400@sun.com>
User-Agent: Thunderbird 2.0b1 (X11/20070115)
Status: RO
Content-Length: 2565

So it looks like there is no dependency on JDK 1.5/
That's fine.

This is a later version of what is provided in JDK 1.6.

I have no idea of when the next JDK will be delivered or
if they do sporadic updates.  Is that team aware that Sun
projects are requiring a later version of JAXB than they
provide?

Could you please note that JDK 1.5 or above can be used
for this project in the materials.

Thanks
Margot



Mark A. Carlson wrote:
>
>
> Jyri Virkki wrote:
>>>  2.1 Project Description
>>>  This project introduces the package of Jaxb2.1 into the SFW 
>>> consolidation.
>>>     
>>
>> Reading through the thread the following still appears unadressed:
>>
>> First, if this library is only relevant to JDK5, why is it being
>> integrated at all? OpenSolaris, AFAIK, only has JDK6 so there's no
>> possible consumer of this library since JDK6 already has it.
>>   
> This version of JAXB is a later version than what is in JDK 6.
> We have a project that requires this version of JAXB. That project
> team has chosen to support JDK 1.5 *and above* and can compile and
> run with either JDK 1.5 or JDK 6 at this point as long as this
> version of JAXB is also used.
>
>> Is this case trying the address the case where user manually downloads
>> JDK5 tarballs and installs them in their home dir or somewhere? Seems
>> odd to have a system library and commands dedicated to serve a
>> private JDK5 install.
>>   
> If they have 1.5 as you suggest, the other project (Wiseman - case
> to be filed soon) will use this case and will work. If they use
> the JDK 6 version that comes by default in OpenSolaris, it will
> also work using this case.
>
>> Aside from odd, there is the problem with the command duplication:
>> The system-provided JDK6 package has xjc and schemagen in
>> /usr/jdk/latest/bin/
>> but this case proposes deliver duplicate (and possibly older) copies
>> of the same tools into /usr/bin for JDK5 use. Since /usr/bin is more
>> likely to be early in the path than the java bin dir, this means if
>> this package is installed a user will inadvertently get the wrong
>> /usr/bin/[xjc|schemagen] instead of the system-delivered ones
>> in /usr/jdk/latest/bin/ That can't be right.
>>   
>
> We will rename this case's xjc to jaxb-xjc and the xjc-schemagen to 
> jaxb-schemagen so as not to conflict
> if an other project wants to use the JDK6 version. We have updated the 
> case materials to reflect this.
>
> -- mark
>
>
>
>
>
>
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc@opensolaris.org


From Mark.Carlson@sun.com Mon Apr 20 11:12:07 2009
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3KIC6oQ027302
	for ; Mon, 20 Apr 2009 11:12:06 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3KIC4Qh021387
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 20 Apr 2009 11:12:06 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIE0040DVW3D700@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Mon, 20 Apr 2009 12:12:03 -0600 (MDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIE00CHZVW2QCA0@brm-avmta-1.central.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon,
 20 Apr 2009 12:12:02 -0600 (MDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3KIC2xK003097	for
 ; Mon, 20 Apr 2009 18:12:02 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KIE00800SOYDZ00@mail-amer.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Mon, 20 Apr 2009 12:12:02 -0600 (MDT)
Received: from boulder-dhcp-223.Central.Sun.COM ([unknown] [172.20.24.223])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KIE00GYDVVGV1D0@mail-amer.sun.com>; Mon,
 20 Apr 2009 12:11:40 -0600 (MDT)
Date: Mon, 20 Apr 2009 12:11:36 -0600
From: "Mark A. Carlson" 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <49ECB80E.2050409@sun.com>
Sender: Mark.Carlson@sun.com
To: Margot Miller 
Cc: Jyri Virkki , Arvind.Samptur@sun.com,
        Bharath.Madakatte@sun.com, LSARC-ext@sun.com
Message-id: <49ECBAD8.4040202@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_8aBO66EkL49m5GjVJDxx5w)"
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
 <20090417002957.GA7030@sun.com> <49E8BB31.4000400@sun.com>
 <49ECB80E.2050409@sun.com>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
Status: RO
Content-Length: 7992

This is a multi-part message in MIME format.

--Boundary_(ID_8aBO66EkL49m5GjVJDxx5w)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

Thanks Margot. I'll have the project team update
the materials as you suggest.

-- mark

Margot Miller wrote:
> So it looks like there is no dependency on JDK 1.5/
> That's fine.
>
> This is a later version of what is provided in JDK 1.6.
>
> I have no idea of when the next JDK will be delivered or
> if they do sporadic updates.  Is that team aware that Sun
> projects are requiring a later version of JAXB than they
> provide?
>
> Could you please note that JDK 1.5 or above can be used
> for this project in the materials.
>
> Thanks
> Margot
>
>
>
> Mark A. Carlson wrote:
>>
>>
>> Jyri Virkki wrote:
>>>>  2.1 Project Description
>>>>  This project introduces the package of Jaxb2.1 into the SFW 
>>>> consolidation.
>>>>     
>>>
>>> Reading through the thread the following still appears unadressed:
>>>
>>> First, if this library is only relevant to JDK5, why is it being
>>> integrated at all? OpenSolaris, AFAIK, only has JDK6 so there's no
>>> possible consumer of this library since JDK6 already has it.
>>>   
>> This version of JAXB is a later version than what is in JDK 6.
>> We have a project that requires this version of JAXB. That project
>> team has chosen to support JDK 1.5 *and above* and can compile and
>> run with either JDK 1.5 or JDK 6 at this point as long as this
>> version of JAXB is also used.
>>
>>> Is this case trying the address the case where user manually downloads
>>> JDK5 tarballs and installs them in their home dir or somewhere? Seems
>>> odd to have a system library and commands dedicated to serve a
>>> private JDK5 install.
>>>   
>> If they have 1.5 as you suggest, the other project (Wiseman - case
>> to be filed soon) will use this case and will work. If they use
>> the JDK 6 version that comes by default in OpenSolaris, it will
>> also work using this case.
>>
>>> Aside from odd, there is the problem with the command duplication:
>>> The system-provided JDK6 package has xjc and schemagen in
>>> /usr/jdk/latest/bin/
>>> but this case proposes deliver duplicate (and possibly older) copies
>>> of the same tools into /usr/bin for JDK5 use. Since /usr/bin is more
>>> likely to be early in the path than the java bin dir, this means if
>>> this package is installed a user will inadvertently get the wrong
>>> /usr/bin/[xjc|schemagen] instead of the system-delivered ones
>>> in /usr/jdk/latest/bin/ That can't be right.
>>>   
>>
>> We will rename this case's xjc to jaxb-xjc and the xjc-schemagen to 
>> jaxb-schemagen so as not to conflict
>> if an other project wants to use the JDK6 version. We have updated 
>> the case materials to reflect this.
>>
>> -- mark
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> opensolaris-arc mailing list
>> opensolaris-arc@opensolaris.org
>

-- 
 	* Mark A. Carlson *
Sr. Architect

*Systems Group*
Phone x69559 / 303-223-6139
Email Mark.Carlson@Sun.COM
	



--Boundary_(ID_8aBO66EkL49m5GjVJDxx5w)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT




  


Thanks Margot. I'll have the project team update

the materials as you suggest.



-- mark



Margot Miller wrote:

So it looks
like there is no dependency on JDK 1.5/
  

That's fine.
  

  

This is a later version of what is provided in JDK 1.6.
  

  

I have no idea of when the next JDK will be delivered or
  

if they do sporadic updates.  Is that team aware that Sun
  

projects are requiring a later version of JAXB than they
  

provide?
  

  

Could you please note that JDK 1.5 or above can be used
  

for this project in the materials.
  

  

Thanks
  

Margot
  

  

  

  

Mark A. Carlson wrote:
  

  


    

Jyri Virkki wrote:
    

    

      
 2.1 Project Description
        

 This project introduces the package of Jaxb2.1 into the SFW
consolidation.
        

    

      

Reading through the thread the following still appears unadressed:
      

      

First, if this library is only relevant to JDK5, why is it being
      

integrated at all? OpenSolaris, AFAIK, only has JDK6 so there's no
      

possible consumer of this library since JDK6 already has it.
      

  

This version of JAXB is a later version than what is in JDK 6.
    

We have a project that requires this version of JAXB. That project
    

team has chosen to support JDK 1.5 *and above* and can compile and
    

run with either JDK 1.5 or JDK 6 at this point as long as this
    

version of JAXB is also used.
    

    

    
Is this case trying the address the case
where user manually downloads
      

JDK5 tarballs and installs them in their home dir or somewhere? Seems
      

odd to have a system library and commands dedicated to serve a
      

private JDK5 install.
      

  

If they have 1.5 as you suggest, the other project (Wiseman - case
    

to be filed soon) will use this case and will work. If they use
    

the JDK 6 version that comes by default in OpenSolaris, it will
    

also work using this case.
    

    

    
Aside from odd, there is the problem with
the command duplication:
      

The system-provided JDK6 package has xjc and schemagen in
      

/usr/jdk/latest/bin/
      

but this case proposes deliver duplicate (and possibly older) copies
      

of the same tools into /usr/bin for JDK5 use. Since /usr/bin is more
      

likely to be early in the path than the java bin dir, this means if
      

this package is installed a user will inadvertently get the wrong
      

/usr/bin/[xjc|schemagen] instead of the system-delivered ones
      

in /usr/jdk/latest/bin/ That can't be right.
      

  

    

We will rename this case's xjc to jaxb-xjc and the xjc-schemagen to
jaxb-schemagen so as not to conflict
    

if an other project wants to use the JDK6 version. We have updated the
case materials to reflect this.
    

    

-- mark
    

    

    

    

    

    

    

_______________________________________________
    

opensolaris-arc mailing list
    

opensolaris-arc@opensolaris.org
    

  

  






-- 




  
    

      
       Mark A. Carlson 

Sr. Architect

      

      Systems Group

Phone x69559 / 303-223-6139

Email Mark.Carlson@Sun.COM

      		
      
    

  












--Boundary_(ID_8aBO66EkL49m5GjVJDxx5w)--

From Mark.Carlson@sun.com Tue Apr 21 10:41:28 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3LHfSAm006981
	for ; Tue, 21 Apr 2009 10:41:28 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3LHfLtl021641
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 21 Apr 2009 18:41:27 +0100 (BST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIG0090PP51LI00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@Sun.COM); Tue, 21 Apr 2009 11:41:25 -0600 (MDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIG000AOP51NY80@brm-avmta-1.central.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Tue,
 21 Apr 2009 11:41:25 -0600 (MDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3LHfPLO027778	for
 ; Tue, 21 Apr 2009 17:41:25 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KIG00600OBHYW00@mail-amer.sun.com> for LSARC-ext@Sun.COM
 (ORCPT LSARC-ext@Sun.COM); Tue, 21 Apr 2009 11:41:25 -0600 (MDT)
Received: from Macintosh-335.local ([unknown] [129.150.35.120])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KIG00HBLP507DC0@mail-amer.sun.com> for LSARC-ext@Sun.COM
 (ORCPT LSARC-ext@Sun.COM); Tue, 21 Apr 2009 11:41:25 -0600 (MDT)
Date: Tue, 21 Apr 2009 11:41:24 -0600
From: "Mark A. Carlson" 
Subject: Re: JAXB [LSARC/2009/237 FastTrack timeout 04/20/2009]
In-reply-to: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
Sender: Mark.Carlson@sun.com
To: LSARC-ext@sun.com
Cc: Arvind.Samptur@sun.com, Bharath.Madakatte@sun.com
Message-id: <49EE0544.5010803@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904131951.n3DJpvEC023300@sac.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
Status: RO
Content-Length: 79

This case was approved at LSARC today. The IAM file has been updated.

-- mark