Bug 137924 - Allow the dynamic registration of ArtifactTypes
Summary: Allow the dynamic registration of ArtifactTypes
Status: ASSIGNED
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: wst.wsi (show other bugs)
Version: 1.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact: Keith Chong CLA
URL:
Whiteboard: enablement, Extensibility
Keywords: api
Depends on:
Blocks: 138379
  Show dependency tree
 
Reported: 2006-04-21 07:43 EDT by Craig Chaney CLA
Modified: 2010-07-20 11:34 EDT (History)
0 users

See Also:

Attachments
patch to allow registration of ArtifactTypes (2.66 KB, patch)
2006-04-21 07:44 EDT, Craig Chaney CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Craig Chaney CLA 2006-04-21 07:43:12 EDT 
The ArtifactType class contains a method newArtifactType() that returns one of four hardcoded static ArtifactType instances.

In order to allow for other profiles that define new artifact types (such as the Basic Security Profile) in other packages to reuse these base assertion classes, you should be able to register new artifact types from elsewhere.
Comment 1 Craig Chaney CLA 2006-04-21 07:44:51 EDT 
Created attachment 39157 [details]
patch to allow registration of ArtifactTypes

This patch does the following:

- Adds a private static variable to ArtifactType that holds a map containing
  the valid TAD versions
- Statically initializes this map to contain the artifact types from the Basic
  Profile
- Adds API to allow other classes to register ArtifactTypes
- Modifies the newArtifactType() method to use the new Map variable
Comment 2 Valentin Baciu CLA 2007-11-08 13:23:50 EST 
I'll try to look at this for WTP 3.0