10:28 p.m.
New Server Runtime for SOA Platform 5.2 needed
----------------------------------------------
Key: JBDS-1346
URL: https://jira.jboss.org/browse/JBDS-1346
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Affects Versions: 4.0.0.M2
Environment: SOA-P 5.2 and JBDS 4 M2
Reporter: Gary Lamperillo
In the ESB Project creation , We need a EAP 5.1 or SOA-P 5.2. I prefer a SOA-P 5.2 in the
runtime list, the advantage of a SOA-P 5.2 is that all of the ESB Project specific
internals are known and the wizard would not need to have the subsequent screens if SOA-P
5.2 is selected instead of the community release.
Without a EAP 5.1 or SOA-P 5.2, the following warning appears :
This server type expects a version of 5.0 but the server directory is of version 5.1.0.
see screen attachments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:30 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1346) New Server Runtime for SOA Platform 5.2 needed
[
https://jira.jboss.org/browse/JBDS-1346?page=com.atlassian.jira.plugin.sy...
]
Gary Lamperillo updated JBDS-1346:
----------------------------------
Attachment: EAP5.1Needed.png
5.1needed2.png
New Server Runtime for SOA Platform 5.2 needed
----------------------------------------------
Key: JBDS-1346
URL: https://jira.jboss.org/browse/JBDS-1346
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Affects Versions: 4.0.0.M2
Environment: SOA-P 5.2 and JBDS 4 M2
Reporter: Gary Lamperillo
Attachments: 5.1needed2.png, EAP5.1Needed.png
In the ESB Project creation , We need a EAP 5.1 or SOA-P 5.2. I prefer a SOA-P 5.2 in
the runtime list, the advantage of a SOA-P 5.2 is that all of the ESB Project specific
internals are known and the wizard would not need to have the subsequent screens if SOA-P
5.2 is selected instead of the community release.
Without a EAP 5.1 or SOA-P 5.2, the following warning appears :
This server type expects a version of 5.0 but the server directory is of version 5.1.0.
see screen attachments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:23 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1346) New Server Runtime for SOA Platform 5.2 needed
[
https://jira.jboss.org/browse/JBDS-1346?page=com.atlassian.jira.plugin.sy...
]
Max Andersen updated JBDS-1346:
-------------------------------
Assignee: Rob Stryker
Fix Version/s: 4.0.0.Beta2
Component/s: servers
For now we can add an EAP 5.1 (surprised we didn't already have one).
Adding a SOA-P triggers all kind of sideeffects (i.e. there will also have to be a SOA-P
5.1 server which would not have differnces but we would have to maintain the list of
facets still.)
Rob - any comments on what we can do ?
New Server Runtime for SOA Platform 5.2 needed
----------------------------------------------
Key: JBDS-1346
URL: https://jira.jboss.org/browse/JBDS-1346
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: servers
Affects Versions: 4.0.0.M2
Environment: SOA-P 5.2 and JBDS 4 M2
Reporter: Gary Lamperillo
Assignee: Rob Stryker
Fix For: 4.0.0.Beta2
Attachments: 5.1needed2.png, EAP5.1Needed.png
In the ESB Project creation , We need a EAP 5.1 or SOA-P 5.2. I prefer a SOA-P 5.2 in
the runtime list, the advantage of a SOA-P 5.2 is that all of the ESB Project specific
internals are known and the wizard would not need to have the subsequent screens if SOA-P
5.2 is selected instead of the community release.
Without a EAP 5.1 or SOA-P 5.2, the following warning appears :
This server type expects a version of 5.0 but the server directory is of version 5.1.0.
see screen attachments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:25 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1346) New Server Runtime for EAP 5.1 (maybe also SOA Platform) needed
[
https://jira.jboss.org/browse/JBDS-1346?page=com.atlassian.jira.plugin.sy...
]
Max Andersen updated JBDS-1346:
-------------------------------
Summary: New Server Runtime for EAP 5.1 (maybe also SOA Platform) needed (was: New
Server Runtime for SOA Platform 5.2 needed)
New Server Runtime for EAP 5.1 (maybe also SOA Platform) needed
---------------------------------------------------------------
Key: JBDS-1346
URL: https://jira.jboss.org/browse/JBDS-1346
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: servers
Affects Versions: 4.0.0.M2
Environment: SOA-P 5.2 and JBDS 4 M2
Reporter: Gary Lamperillo
Assignee: Rob Stryker
Fix For: 4.0.0.Beta2
Attachments: 5.1needed2.png, EAP5.1Needed.png
In the ESB Project creation , We need a EAP 5.1 or SOA-P 5.2. I prefer a SOA-P 5.2 in
the runtime list, the advantage of a SOA-P 5.2 is that all of the ESB Project specific
internals are known and the wizard would not need to have the subsequent screens if SOA-P
5.2 is selected instead of the community release.
Without a EAP 5.1 or SOA-P 5.2, the following warning appears :
This server type expects a version of 5.0 but the server directory is of version 5.1.0.
see screen attachments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:03 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1346) New Server Runtime for EAP 5.1 (maybe also SOA Platform) needed
[
https://jira.jboss.org/browse/JBDS-1346?page=com.atlassian.jira.plugin.sy...
]
Gary Lamperillo commented on JBDS-1346:
---------------------------------------
Hi Max,
Would be great if the customer only needs to know they are using a SOA-P version
release, without knowledge of ESB version and EAP version. Are we going with this
approach in the wizard? Is there a link available to test this out?
Thanks,
Gary
New Server Runtime for EAP 5.1 (maybe also SOA Platform) needed
---------------------------------------------------------------
Key: JBDS-1346
URL: https://jira.jboss.org/browse/JBDS-1346
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: servers
Affects Versions: 4.0.0.M2
Environment: SOA-P 5.2 and JBDS 4 M2
Reporter: Gary Lamperillo
Assignee: Rob Stryker
Fix For: 4.0.0.Beta2
Attachments: 5.1needed2.png, EAP5.1Needed.png
In the ESB Project creation , We need a EAP 5.1 or SOA-P 5.2. I prefer a SOA-P 5.2 in
the runtime list, the advantage of a SOA-P 5.2 is that all of the ESB Project specific
internals are known and the wizard would not need to have the subsequent screens if SOA-P
5.2 is selected instead of the community release.
Without a EAP 5.1 or SOA-P 5.2, the following warning appears :
This server type expects a version of 5.0 but the server directory is of version 5.1.0.
see screen attachments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:02 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1346) New Server Runtime for EAP 5.1 (maybe also SOA Platform) needed
[
https://jira.jboss.org/browse/JBDS-1346?page=com.atlassian.jira.plugin.sy...
]
Rob Stryker commented on JBDS-1346:
-----------------------------------
I don't think we can possibly make a soa-p type and an epp type and all these types
without some changes upstream to servertools to allow configurations of some sort.
I already know servertools team hates making big changes so I'm not even sure if
it'd be worth my time to try to code it up. The servertools code isn't that
complicated though, and it's very neat, so I suspect i could do it without much
trouble, but the problem would be getting servertools to accept it.
To be clear, the change I'd be making is allowing a group of supported modules in the
plugin.xml, and then creating a new server type based on this module configuration. Right
now, every server type i create, I have to list it's full list of supported modules
and it makes hte overhead just a gigantic pain in the ass.
New Server Runtime for EAP 5.1 (maybe also SOA Platform) needed
---------------------------------------------------------------
Key: JBDS-1346
URL: https://jira.jboss.org/browse/JBDS-1346
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: servers
Affects Versions: 4.0.0.M2
Environment: SOA-P 5.2 and JBDS 4 M2
Reporter: Gary Lamperillo
Assignee: Rob Stryker
Fix For: 4.0.0.Beta2
Attachments: 5.1needed2.png, EAP5.1Needed.png
In the ESB Project creation , We need a EAP 5.1 or SOA-P 5.2. I prefer a SOA-P 5.2 in
the runtime list, the advantage of a SOA-P 5.2 is that all of the ESB Project specific
internals are known and the wizard would not need to have the subsequent screens if SOA-P
5.2 is selected instead of the community release.
Without a EAP 5.1 or SOA-P 5.2, the following warning appears :
This server type expects a version of 5.0 but the server directory is of version 5.1.0.
see screen attachments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:39 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1346) New Server Runtime for EAP 5.1 (maybe also SOA Platform) needed
[
https://jira.jboss.org/browse/JBDS-1346?page=com.atlassian.jira.plugin.sy...
]
Max Andersen updated JBDS-1346:
-------------------------------
Fix Version/s: 4.0.0.CR1
(was: 4.0.0.Beta2)
New Server Runtime for EAP 5.1 (maybe also SOA Platform) needed
---------------------------------------------------------------
Key: JBDS-1346
URL: https://jira.jboss.org/browse/JBDS-1346
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: servers
Affects Versions: 4.0.0.M2
Environment: SOA-P 5.2 and JBDS 4 M2
Reporter: Gary Lamperillo
Assignee: Rob Stryker
Fix For: 4.0.0.CR1
Attachments: 5.1needed2.png, EAP5.1Needed.png
In the ESB Project creation , We need a EAP 5.1 or SOA-P 5.2. I prefer a SOA-P 5.2 in
the runtime list, the advantage of a SOA-P 5.2 is that all of the ESB Project specific
internals are known and the wizard would not need to have the subsequent screens if SOA-P
5.2 is selected instead of the community release.
Without a EAP 5.1 or SOA-P 5.2, the following warning appears :
This server type expects a version of 5.0 but the server directory is of version 5.1.0.
see screen attachments.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:31 a.m.
New subject: [JBoss JIRA] Resolved: (JBDS-1346) New Server Runtime for EAP 5.1 (maybe also SOA Platform) needed
[
https://jira.jboss.org/browse/JBDS-1346?page=com.atlassian.jira.plugin.sy...
]
Rob Stryker resolved JBDS-1346.
-------------------------------
Fix Version/s: 4.0.0.Beta2
(was: 4.0.0.CR1)
Resolution: Done
This was solved in beta2
New Server Runtime for EAP 5.1 (maybe also SOA Platform) needed
---------------------------------------------------------------
Key: JBDS-1346
URL: https://jira.jboss.org/browse/JBDS-1346
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: servers
Affects Versions: 4.0.0.M2
Environment: SOA-P 5.2 and JBDS 4 M2
Reporter: Gary Lamperillo
Assignee: Rob Stryker
Fix For: 4.0.0.Beta2
Attachments: 5.1needed2.png, EAP5.1Needed.png
In the ESB Project creation , We need a EAP 5.1 or SOA-P 5.2. I prefer a SOA-P 5.2 in
the runtime list, the advantage of a SOA-P 5.2 is that all of the ESB Project specific
internals are known and the wizard would not need to have the subsequent screens if SOA-P
5.2 is selected instead of the community release.
Without a EAP 5.1 or SOA-P 5.2, the following warning appears :
This server type expects a version of 5.0 but the server directory is of version 5.1.0.
see screen attachments.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:36 a.m.
New subject: [JBoss JIRA] Closed: (JBDS-1346) New Server Runtime for EAP 5.1 (maybe also SOA Platform) needed
[
https://jira.jboss.org/browse/JBDS-1346?page=com.atlassian.jira.plugin.sy...
]
Vlado Pakan closed JBDS-1346.
-----------------------------
Verified on JBDS 4.0.0.v201012070137R-H33-Beta2.
New Server Runtime for EAP 5.1 (maybe also SOA Platform) needed
---------------------------------------------------------------
Key: JBDS-1346
URL: https://jira.jboss.org/browse/JBDS-1346
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: servers
Affects Versions: 4.0.0.M2
Environment: SOA-P 5.2 and JBDS 4 M2
Reporter: Gary Lamperillo
Assignee: Rob Stryker
Fix For: 4.0.0.Beta2
Attachments: 5.1needed2.png, EAP5.1Needed.png
In the ESB Project creation , We need a EAP 5.1 or SOA-P 5.2. I prefer a SOA-P 5.2 in
the runtime list, the advantage of a SOA-P 5.2 is that all of the ESB Project specific
internals are known and the wizard would not need to have the subsequent screens if SOA-P
5.2 is selected instead of the community release.
Without a EAP 5.1 or SOA-P 5.2, the following warning appears :
This server type expects a version of 5.0 but the server directory is of version 5.1.0.
see screen attachments.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5049
days inactive
5118
days old
jbosstools-issues@lists.jboss.org
8 comments
4 participants
participants (4)
-
Gary Lamperillo (JIRA) -
Max Andersen (JIRA)
-
Rob Stryker (JIRA)
-
Vlado Pakan (JIRA)