[JBoss JIRA] Created: (JBIDE-2064) JBossESB graphical node/service designer
by Mark Little (JIRA)
JBossESB graphical node/service designer
----------------------------------------
Key: JBIDE-2064
URL: http://jira.jboss.com/jira/browse/JBIDE-2064
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Reporter: Mark Little
Attachments: SOA Tooling.pdf
Currently the ESB deployment descriptor is XML based but we need it to be graphically oriented. Each ESB service is a collection of actions that are re-usable components. The graphical tool would allow for the construction (within Eclipse) of a service from action chaining. The action descriptions would be storable in a repository (though that is a second level addition). We want to isolate the user from the XML as much as possible because it is prone to errors. Plus, it makes service re-usability more problematical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months
[JBoss JIRA] Created: (JBIDE-2069) SOI viewer
by Mark Little (JIRA)
SOI viewer
----------
Key: JBIDE-2069
URL: http://jira.jboss.com/jira/browse/JBIDE-2069
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Reporter: Mark Little
We need a way of viewing the running SOA-P nodes and being able to drill down into them to see the services deployed on them, the version of the services etc. Then we would like to be able to tie this into the service development and deployment lifecycle: by being able to drag a developed service onto a graphical representation of a service node and have it be deployed automatically by the tool.
Some of this may already exist in JON.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months
[JBoss JIRA] Created: (JBIDE-2068) Design-time service creator
by Mark Little (JIRA)
Design-time service creator
---------------------------
Key: JBIDE-2068
URL: http://jira.jboss.com/jira/browse/JBIDE-2068
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Reporter: Mark Little
When building services within a Service Oriented Infrastructure (SOI) you typically do so by composition of other services. Those other services are typically discovered dynamically either by browsing the registry or by broadcasting to the entire SOI. The information returned by such a search (registry or broadcast) contains service contract information (such as the SLA, type of service, work it offers etc.) and the developer can then select the right service(s) from the list. Newly created services (either composites or atomic) are then published back to the registry (or the SOI).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months
[JBoss JIRA] Created: (JBIDE-2077) "Make this class and its related classes mapped via JPA"
by Vitali Yemialyanchyk (JIRA)
"Make this class and its related classes mapped via JPA"
--------------------------------------------------------
Key: JBIDE-2077
URL: http://jira.jboss.com/jira/browse/JBIDE-2077
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Reporter: Vitali Yemialyanchyk
Assigned To: Vitali Yemialyanchyk
Priority: Minor
Denis Golovin:
>>>
Let's imagine I have several (say 10) classes that I'd like to make
persistent. The classes form completed domain model.
I decided to use hibernate and JPA annotations, I have lets say JBDS
1.1.0 or JBossTools 2.1.0 installed.
Question is what I should do to make my model persistent? It there
anything that helps me to do it?
Now I see only way. I have to go through all classes and add annotations
for class and for fields.
>>>
Max Andersen:
>>>
Having a "Make this class and its related classes mapped via JPA" would be
an interesting Refactoring to implement.
Should basically just work like this:
makePersistent(ITypeRoot clazz, Set processed) {
add @Entity
Find most likely id property and add @Id
processed.add(selectedClass);
associations = getAssociatedClasses(selectedClass);
foreach class in associations {
if(!processed.contains(class)) {
makePersistent(class, processed);
}
}
}
There then might be some exceptional cases like handling version properties, temporal values and
non-JPA supported mappings which Hibernate would be able to understand/map.
>>>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months
[JBoss JIRA] Created: (JBIDE-2118) Cleanup/unify the EL code completion used in JSF, Java, Seam completions
by Max Rydahl Andersen (JIRA)
Cleanup/unify the EL code completion used in JSF, Java, Seam completions
------------------------------------------------------------------------
Key: JBIDE-2118
URL: http://jira.jboss.com/jira/browse/JBIDE-2118
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JSF
Affects Versions: 2.1.0.beta1
Reporter: Max Rydahl Andersen
Priority: Critical
Fix For: 2.2.x
The current EL completion has a couple of issues:
1) The logic is not shared (different implementations for JSF and Seam resulting in cases where one can code complete and the other not...)
2) If a project has Seam enabled it should *add* to the current JSF completions not be something completely seperate
3) Not all of the legal JSF/jboss-el completion options are supported (e.g. #{identity.instance.getUserName()} is legal but we only have #{identity.instance.username} etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months