Web and WebWorks Development

[mohunt]

I have configured the barcode extension as so:

The library.xml is in C:\Program Files (x86)\Research In Motion\BlackBerry WebWorks SDK 2.3.1.5\ext\webworks.media.barcode

The UI directory and java files are in C:\Program Files (x86)\Research In Motion\BlackBerry WebWorks SDK 2.3.1.5\ext\webworks.media.barcode\webworks\media\barcode

The app config.xml looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<widget xmlns="http://www.w3.org/ns/widgets" xmlns:rim="http://www.blackberry.com/ns/widgets" version="1.0.0.0">
  <name>Solider Barcode App</name>
  <description>DemoBarCode demonstrates using native barcode libraries within BlackBerry Application.</description>
  <feature id="webworks.media.barcode"/>
  <feature id="blackberry.app" required="true" version="1.0.0.0"/>
  <feature id="blackberry.app.event" required="true" version="1.0.0.0"/>
  <feature id="blackberry.find" required="true" version="1.0.0.0"/>
  <feature id="blackberry.identity" required="true" version="1.0.0.0"/>
  <feature id="blackberry.identity.phone" required="true" version="1.0.0.0"/>
  <feature id="blackberry.invoke" required="true" version="1.0.0.0"/>
  <feature id="blackberry.message" required="true" version="1.0.0.0"/>
  <feature id="blackberry.system" required="true" version="1.0.0.0"/>
  <feature id="blackberry.system.event" required="true" version="1.0.0.0"/>
  <feature id="blackberry.ui.menu" required="true" version="1.0.0.0"/>
  <feature id="blackberry.utils" required="true" version="1.0.0.0"/>
  <feature id="blackberry.invoke.BrowserArguments" required="true" version="1.0.0.0"/>
  <feature id="blackberry.invoke.MessageArguments" required="true" version="1.0.0.0"/>
  <access subdomains="true" uri="*"/>
  <icon rim:hover="false" src="images/icon.png"/>
  <content src="index.htm"/>
</widget>

When I try to package this I get the following error:

C:\Program Files (x86)\Research In Motion\BlackBerry WebWorks SDK 2.3.1.5>bbwp C:\UID\SMBA\SoldierBarcodeAppTOSIGN.zip -o C:\UID\SMBA\output
[INFO]                  Parsing command line options
[INFO]                  Parsing bbwp.properties
[INFO]                  Validating application archive
[INFO]                  Parsing config.xml
[WARNING]               Failed to find the <author> element
[INFO]                  Populating application source
[Fatal Error] library.xml:16:6: The processing instruction target matching "[xX][mM][lL]" is not allowed.
[ERROR]                 Feature cannot be found in any extension(webworks.media.barcode)

Help!

[26filip]

You must add in config.xml after name:

	<author>app_author</author>

[mohunt]

Thank you. The warning error was not the problem I was trying to solve.  It  Fatal Error below that is causing the problem:

[Fatal Error] library.xml:16:6: The processing instruction target matching "[xX]
[mM][lL]" is not allowed.
[ERROR] Feature cannot be found in any extension(webworks.media.barcode)

[The_Anomaly]

I think your UI directory is wrong.  Check out point number 6 on this link:

https://github.com/blackberry/WebWorks-Community-APIs/tree/master/Smartphone/Barcode

Copy the downloaded Smartphone\Barcode\src\blackberry directory to your new ext\webworks.media.barcode\blackberry directory

It looks like you have:

C:\Program Files (x86)\Research In Motion\BlackBerry WebWorks SDK 2.3.1.5\ext\webworks.media.barcode\webworks\media\barcode

HOWEVER I think that documentation is also wrong because there is no BLACKBERRY folder in the github directory.  Try creating a Blackberry folder in your webworks.media.barcode folder and then copying all the files into there.  Check out the other folders for the EXT folder for some direction.

[mohunt]

Thank you for your reply.  I have already attempted this without success. :-(

[mohunt · Accepted solution]

 I found the problem was caused by the library.xml file of the webworks.media.barcode extension.   The comments precede  the <?xml version="1.0" encoding="utf-8"?> tag.  When I moved the  <?xml version="1.0" encoding="utf-8"?> tag to the first line of the file everything worked.

Thanks to Jeff Bentley of RIM for assistance in resolving this problem.