The Artima Developer Community
Articles | News | Weblogs | Books | Forums
Artima Forums | Articles | Weblogs | Java Answers | News
Sponsored Link •

Java Buzz Forum
Controlling JAD/MF Metadata in Orca TDD BuildFramework

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Fred Grott

Posts: 4361
Nickname: shareme
Registered: Jan, 2003

Fred Grott is Lead Developer-CEO of ShareMe Technologies LLC -The Mobile Future
Controlling JAD/MF Metadata in Orca TDD BuildFramework Posted: Feb 9, 2005 4:06 PM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by Fred Grott.
Original Post: Controlling JAD/MF Metadata in Orca TDD BuildFramework
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology. 		Latest Java Buzz Posts
Latest Java Buzz Posts by Fred Grott
Latest Posts From ShareMe Technologies LLC-The Mobile Future

Advertisement
It may not appear obvious that introducing the Sterilizer tool into the Orca TDD Build Framework amoung the Antenna JAD info and the JReleaseInfo JAD metadata is accomplising what may be desired. But, remember there are two types of JAD/MF metadata.

We of course have the metadata needed for the JAD/MF often optional or additional prameters per Mobile Operator Network or DRM platform which in this case can flow through a JADANme.xml from Sterilizer, JReleaseinfo task, and etc. The other type of Metadata of the JAD information is in the class that JReleaseinfo produces.

Because this metadata is in a class it becomes exposed to preprocessing and thus can help eliminate code porting headaches as we have method return values to quantify that indicate which deviecs the code base was developed for before we start adding major preprocessing to adopt to the new device. Now for the nice trick.

We have to have a way to manage this metadata as one point of configuration instead of many. Thus we put all metadata parameters from Sterilizer into JReleaseinfo's ant task as properties and we add to that task to generate the Sterilizer JADName.xml metadata configuration file that Sterilizer will use when its ant task is executed.

Read: Controlling JAD/MF Metadata in Orca TDD BuildFramework

Topic: More Advanced Synth Previous Topic   Next Topic Topic: EclipseWork - Eclipse Plugin for WebWork
Sponsored Links


Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use