Reassigning to "projects".

I don't undestand what the issue is about. What are the "encoders"? what do you mean by "common" project type?


closing as invalid, please reopen once you fill in the additional information requested.

Sorry for the lack of explanation, I shouldn't have assumed JCAPS knowledge.

NB 6 is the IDE for Sierra/OpenESB/Alaska/JCAPS 5.2 ...call it what you will. JCAPS 5.1.x uses NB 4.x (I think) as its IDE.
It is possible in this to create a project which will not be built but will just store common objects to be used in
other projects... for example, an encoder is a representation of a file structure to be applied to a file being read
into OpenESB via the File Binding Component in order that the file can be unmarshalled into its relevant fields.

So, what I was suggesting as an enhancement is a type of "Common" project which requires no build artefacts in which I
can store objects such as encoders to be used by possibly many other projects to save on replication. At the moment in
NB I can't see any project such as this.

Re-opening. Please contact me for more info should it be required. 

so far you seem to be the only one ever requesting such a project implementation. We definitely won't do it for 6.0 (too
late) and even for future releases, I don't see this as a priority task. 

If you really require that you are probably better off writing it yourself, however I'm not completely sure that the
right solution for your problem is a new project type. A project type is generally a set of files/sources that somehow
transfer during a process of building into something.. Your usecase is more like a storage of components for use in the
IDE (if I get it right)

You are right that it is a means of storing resources for use in other projects in the IDE.

The reason I think no-one has brought this up before now is that we have just begun performing a GAP analysis between
JCAPS 5.1.x and JCAPS 5.2/OpenESB and this process is highlighting potential problems in the way that users will use the
product.
In a collaborative development environment it is necessary to have a common project to store artefacts that will be used
in many other projects in the IDE and by many other users. Clearly I could create a project of any type and store these
artefacts at the moment, hence this is not a pressing issue, however it would be nice to have a specific project type of
"common".

As an example, a particular file may be created in one business process (BPEL project), updated in a second, and deleted
in a third, these projects all use the same file structure and hence the same custom encoder. It is normal in JCAPS
5.1.x that this custom encoder is created upfront and stored in a common project, then the developers of the BPEL
projects reference this in a central location. When the custom encoder needs changing, it is changed in only one place.

a few things are unclear to me:
1. what is the supposed UI? (Actions, Customizer, Nodes etc)
2. How are the other projects accessing the content of this project?


if this is BPEL related, it should be possibly done in BPEL support modules..

The UI would be the same as creating any new project (File -> New Project), it may be that a new Category is necessary,
but it could go under "Service Oriented Architecture"

How other projects access this is still up in the air at the moment, it is not possible currently to access an XSD in
one project from another project when creating WSDL for a binding component for example.

This is not specific to BPEL.

I'm not convinced this a general feature. It looks like something specific to BPEL or SOA only. What is the correct
category to reassign to?

I think SOA would be the correct place to re-assign it.

reassigning to "enterprise" component.