[
https://jira.jboss.org/jira/browse/JBIDE-4859?page=com.atlassian.jira.plu...
]
John Verhaeg commented on JBIDE-4859:
-------------------------------------
Wrt the numbered items in my last post:
1) Ah, didn't realize that. That blows.
2) For this and most of the remaining items, I'm looking at this from a data services
perspective (even though that won't be a part of JBT until a post-3.1 release).
I'm not suggesting web development not related to Java EE, but that some web
development are useful to work with in the tooling without any need for a server. For
instance, Teiid has the ability to create web services mapped to back-end (usually
relational) data without the need for the user to ever touch an actual server; we simply
need a WSDL and access to the backend data. Having said that, this is probably the
"weakest" suggestion I had for a possible change.
3) The multiple categories idea seems like it might have merit, but I completely disagree
with your assessment of the purpose of Hibernate/JPA and Drools. We've used both
technologies in conjunction with Teiid, Teiid Designer, and ModeShape, and none of our
scenarios had anything to do with a server or J2EE. I understand that the JPA spec is
technically defined within the scope of the Java EE spec, but 1) that going to change
shortly, and 2) there has never been any requirement to have J2EE. Similarly, drools is
really just a rules engine and has no direct tie-in to web services or SOA. jBPM does,
but not drools. And again, we've made use of drools within ModeShape in areas that
had nothing to do with SOA.
4) Smooks is by definition a tool for transforming data to and from XML, so I don't
understand why it wouldn't intuitively be found by the user under an XML category.
I guess ignore the DTP reference for now; I'm thinking of future JBT extensions we had
in mind for DTP, not DTP proper. However, wrt Hibernate, even as an organization, we now
manage Teiid, ModeShape, and Hibernate all under the Data Services umbrella.
So I guess maybe none of my suggestions are necessarily important immediately since there
isn't yet a set of data services tool within JBT, I just thought it might help us
transition a bit in that direction.
Create new categories for JBT/JBDS update sites
-----------------------------------------------
Key: JBIDE-4859
URL:
https://jira.jboss.org/jira/browse/JBIDE-4859
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.1.0.M3
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 3.1.0.CR2
Attachments: jbtupdatesitesuggestion.png, screenshot-1.jpg, Screenshot-1.png,
Screenshot-2.png, site.xml
Renamed to capture current thrust of issue: should we have more categories than we
currently do on the update site? Expose more/less features? This is a
branding/marketing/ease of use question, so for now I'm bouncing it over to Max for
comments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira