JPD
From Wikipedia, the free encyclopedia
| This article may not meet the general notability guideline or one of the following specific guidelines for inclusion on Wikipedia: Biographies, Books, Companies, Fiction, Music, Neologisms, Numbers, Web content, or several proposals for new guidelines. If you are familiar with the subject matter, please expand or rewrite the article to establish its notability. The best way to address this concern is to reference published, third-party sources about the subject. If notability cannot be established, the article is more likely to be considered for redirection, merge or ultimately deletion, per Wikipedia:Guide to deletion. This article has been tagged since October 2007. |
| This article or section is written like an advertisement. Please help rewrite this article from a neutral point of view. Mark blatant advertising which would require a fundamental rewrite in order to become encyclopedic for speedy deletion, using {{db-spam}}. (December 2007) |
| The introduction to this article provides insufficient context for those unfamiliar with the subject. Please help improve the article with a good introductory style. |
| This article does not cite any references or sources. (October 2007) Please help improve this article by adding citations to reliable sources. Unverifiable material may be challenged and removed. |
JPD is a file format that stands for Java Process Definition. It is a Java file used in the BEA WebLogic product family.
[edit] Overview
JPD builds on Java Language Metadata technology (JSR-175) to provide an easy-to-use syntax for describing a business process at the source code level for the J2EE platform. Metadata will bind data and tasks within the process definition to variables, classes, and tasks in the source code. The metadata will be amenable to manipulation by tools.
Java Process Definitions behave as regular java files but are available only to BEA WebLogic. Not only do they behave as regular java but they can access regular java classes as well and all the same object-oriented programming principles and practices apply to these jpd files. Since they are not reusable only process specific code should be placed in there and the rest in specific java classes.
Process definitions should only be used for a specific process and their use for writing business logic is a grave violation of the separation of concerns principle. Process definitions by no means are a substitute of business logic. Process definitions are designed to serve as an integration point for the communication between various business logic components.
[edit] External links
http://e-docs.bea.com/workshop/docs81/doc/en/core/index.html
http://e-docs.bea.com/workshop/docs81/doc/en/integration/wfguide/wfguidePerform.html?skipReload=true
Example: http://www.ftponline.com/javapro/2005_06/magazine/features/akrishnaswamy/page2.aspx 189.15.75.17 (talk) 05:35, 24 November 2007 (UTC)VJRANCO - Brazil189.15.75.17 (talk) 05:35, 24 November 2007 (UTC)

