Hi Darryl,
You shouldn't keep your custom components in /deploy yourself. This is where GeoEvent deploys .jars when you use Manager's "Add Local..." workflows. If you are placing something in /deploy yourself, then GeoEvent is going to attempt to use it right away (if you're familiar with Tomcat, it's like copying a .war into /webapps - Tomcat will "hot deploy" it).
Note that you can place .jar's in /deploy yourself -- which does the same thing as Manager's "Add Local..." workflows -- it's just that you should do one or the other. To keep things clean, and myself sane, I keep my compiled .jar's in my NetBeans /dist folder, then deploy them to GeoEvent using Manager's "Add Local..." workflows. Manager then places the .jar in /deploy and GeoEvent picks it up and registers it for use. So I leave GeoEvent entirely in control of my /deploy folder when it comes time to deploying new components.
Deleting is a different story, as Manager does not have an equivalent workflow for removing custom components. In the case of deleting custom components, just simply delete the .jar from /deploy yourself. GeoEvent will detect the file's deletion and unregister that custom component. Note that if you do this, 1) any existing inputs, outputs, or services that used your component will be in an error state and 2) any custom connectors that used a custom transport or adapter will then have their transport or adapter re-assigned to one that still exists in the list. This is most likely not desired, so you should also delete the custom connector that used the custom transport or adapter.
Mark
