Return-Path: X-Original-To: apmail-ace-users-archive@minotaur.apache.org Delivered-To: apmail-ace-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E040010C54 for ; Fri, 25 Oct 2013 10:15:02 +0000 (UTC) Received: (qmail 17479 invoked by uid 500); 25 Oct 2013 10:14:38 -0000 Delivered-To: apmail-ace-users-archive@ace.apache.org Received: (qmail 17339 invoked by uid 500); 25 Oct 2013 10:14:20 -0000 Mailing-List: contact users-help@ace.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@ace.apache.org Delivered-To: mailing list users@ace.apache.org Received: (qmail 17301 invoked by uid 99); 25 Oct 2013 10:14:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Oct 2013 10:14:17 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [217.24.201.142] (HELO mx.bosch-si.com) (217.24.201.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Oct 2013 10:14:13 +0000 X-ASG-Debug-ID: 1382696031-040b7f73fe12c110001-YNn92h Received: from immpwimx01.innoimm.local ([10.55.67.25]) by mx.bosch-si.com with ESMTP id ioSFRlekMivDBngI (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 25 Oct 2013 12:13:51 +0200 (CEST) X-Barracuda-Envelope-From: Wilfried.Sibla@bosch-si.com X-Barracuda-RBL-Trusted-Forwarder: 10.55.67.25 X-ASG-Whitelist: Client Received: from IMBVW2EXC00.bosch-si.com ([10.55.66.140]) by immpwimx01.innoimm.local over TLS secured channel with Microsoft SMTPSVC(7.5.7601.17514); Fri, 25 Oct 2013 12:13:51 +0200 Received: from IMBPW2EXD01.bosch-si.com ([fe80::d052:f355:928e:e5ba]) by IMBVW2EXC00 ([10.55.1.51]) with mapi id 14.02.0342.003; Fri, 25 Oct 2013 12:13:50 +0200 X-Barracuda-BWL-IP: 10.55.66.140 X-Barracuda-RBL-IP: 10.55.66.140 From: Sibla Wilfried To: "users@ace.apache.org" Subject: AW: Uploading a configuration file Thread-Topic: Uploading a configuration file X-ASG-Orig-Subj: AW: Uploading a configuration file Thread-Index: AQHOy20hBHHGSsp5+0an29rypxRj7Jn5JJgAgACSrwCAAOnjgIAESdfAgAYtwgCAACWGoA== Date: Fri, 25 Oct 2013 10:13:49 +0000 Message-ID: <83CCD4C6D2018F4A9E31ABD2C253281C0B08DD@imbpw2exd01.bosch-si.com> References: <1382037241.8264.YahooMailNeo@web125005.mail.ne1.yahoo.com> <1382069364.27849.YahooMailNeo@web125002.mail.ne1.yahoo.com> <4DBA8EAE-C02E-468B-BCF3-4545CAC73FB8@luminis.nl> <83CCD4C6D2018F4A9E31ABD2C253281C0AF684@imbpw2exd01.bosch-si.com> <875FF824-85CA-4BED-AB7C-D85E7FE3BEE3@luminis.nl> In-Reply-To: <875FF824-85CA-4BED-AB7C-D85E7FE3BEE3@luminis.nl> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.55.35.103] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 25 Oct 2013 10:13:51.0277 (UTC) FILETIME=[E7029DD0:01CED16A] X-Barracuda-Connect: UNKNOWN[10.55.67.25] X-Barracuda-Start-Time: 1382696031 X-Barracuda-Encrypted: AES128-SHA X-Barracuda-URL: http://217.24.201.142:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at bosch-si.com X-Virus-Checked: Checked by ClamAV on apache.org Hi Marcel Thx for your reply. OK, that could help. But then I must not use the maven-bundle-plugin for th= e Manifest generation. I think there are alternatives (possible the maven-jar-plugin)... Or I possibly can suppress adding the Bundle-SymbolicName. Will try this. Thx and Greetings Wilfried -----Urspr=FCngliche Nachricht----- Von: Marcel Offermans [mailto:marcel.offermans@luminis.nl]=20 Gesendet: Freitag, 25. Oktober 2013 11:57 An: users@ace.apache.org Betreff: Re: Uploading a configuration file Hello Wilfried, As far as I can see your experience is correct, if you make a custom resour= ce type that is a "special kind of bundle" then you will have the problem t= hat the BundleHelper will identify your artifact as a bundle. Taken from Bu= ndleHelperImpl.recognize(.): public String recognize(ArtifactResource artifact) { /* * Tries to find out whether this artifact is a bundle by (a) tryin= g to open it as a jar, (b) trying to extract * the manifest, and (c) checking whether that manifest contains a = Bundle-SymbolicName header. */ But what you state is not 100% true, a jar is only a bundle if it also has = a symbolic name header. Maybe you can use that to your advantage and leave = out that header for your custom content? Greetings, Marcel On Oct 21, 2013, at 11:44 , Sibla Wilfried wr= ote: > Hello Marcel, >=20 > After reading this topic I would like to make a short remark to this. >=20 > I tried to define a custom resource type and also implement a ArtifactRec= ognizer and ArtifactHelper. >=20 > First I thought I could implement the resource as a jar file and embed my= custom content and to recognize my resource by using certain Manifest attr= ibutes. > After first tests I had to switch from a jar to a zip archive (used the m= aven-assembly-plugin). > The reason was that jars including Manifests are catched by the default B= undleHelper and identified as bundles. Thus not the correct custom resource= processor is assigned to such a customized resources jar. > As a consequence the resource processor isn't deployed etc. >=20 > Is the experience I made with this correct or are some other mistakes mor= e obvious? >=20 > Greetings > Wilfried >=20 > -----Urspr=FCngliche Nachricht----- > Von: Marcel Offermans [mailto:marcel.offermans@luminis.nl]=20 > Gesendet: Freitag, 18. Oktober 2013 20:07 > An: users@ace.apache.org; ghania ferrag > Betreff: Re: Uploading a configuration file >=20 > Hello Ghania, >=20 > I fixed the link and added some documentation that hopefully gets you sta= rted implementing your own artifact type. Take a look at: >=20 > http://ace.apache.org/dev-doc/adding-custom-artifact-types.html >=20 > Please let me know what you think and if there's anything we can improve = on that page. >=20 > Greetings, Marcel >=20 >=20 > On Oct 18, 2013, at 6:09 AM, ghania ferrag wrote: >=20 >> Hi Marcel, >>=20 >> Thank you very much for your prompt and quick response.For sure, I'll se= arch and read more about the ArtifactHelper and ArtifactRecognizer and impl= ement them to be able to add our configuration files to ACE. >> For the broken link I was reading the user guide from this link : http:/= /ace.apache.org/user-doc/user-guide.html, and in the section Uploading arti= facts, there is a link for adding support for new types of artifacts which = is not working. >>=20 >> Thank you very much and my best Regards, Ghania >>=20 >>=20 >>=20 >> ________________________________ >> De : Marcel Offermans =C0 :=20 >> users@ace.apache.org; ghania ferrag Envoy=E9 le :=20 >> jeudi 17 octobre 2013 15h24 Objet : Re: Uploading a configuration file >>=20 >>=20 >> Hello Ghania, >>=20 >> On Oct 17, 2013, at 21:14 PM, ghania ferrag wrote: >>=20 >>> When I tried to add configuration files (which are PDF and XML files) a= n error is displayed : noting that particular artifact is not uploaded.=20 >>> In the Apache Ace user guide it said that an artifact is anything from = an OSGi bundle to a configuration file. >>> How we can upload a configuration file using ACE server UI? >>=20 >> Out of the box, ACE supports bundles and XML configuration files that fo= llow the Auto Configuration specification (chapter 115 in the OSGi compendi= um). >>=20 >> If you want to add support for other file types, you need to implement a= n ArtifactHelper and ArtifactRecognizer and add those to ACE. Furthermore, = you need to create a resource processor bundle, add it as an artifact to AC= E and then you can add your new files. >>=20 >> I really need to find some time to document that more elaborately and co= me up with an example. For now, the best examples are in the ACE sourcecode= .=20 >>=20 >>=20 >>> Also in the Ace user guide, the following link http://ace.apache.org/d= ev-doc/adding-artifact-recognizers.html( adding support for new types of ar= tifacts in ACE ) seems to be broken. >>=20 >> On what page exactly did you find that link? I could not find it. You ca= n raise an issue for that so we won't forget to fix it. >>=20 >> Greetings, Marcel >=20