[JBoss JIRA] Created: (JBDS-1573) Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
9:22 p.m.
Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the
service is actually not deployed
-----------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Error Reporting, integration
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Priority: Critical
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:24 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1573) Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Len DiMaggio updated JBDS-1573:
-------------------------------
Attachment: JBDS-1573 - Screenshot-1.png
JBDS-1573- Screenshot-2.png
Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears
succesful - but the service is actually not deployed
-----------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Error Reporting, integration
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Priority: Critical
Attachments: JBDS-1573 - Screenshot-1.png, JBDS-1573- Screenshot-2.png
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:26 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1573) Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Len DiMaggio updated JBDS-1573:
-------------------------------
Priority: Major (was: Critical)
Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears
succesful - but the service is actually not deployed
-----------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Error Reporting, integration
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Attachments: JBDS-1573 - Screenshot-1.png, JBDS-1573- Screenshot-2.png
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:33 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1573) Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Len DiMaggio updated JBDS-1573:
-------------------------------
Attachment: helloworld.zip
Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears
succesful - but the service is actually not deployed
-----------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Error Reporting, integration
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:54 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1573) Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Len DiMaggio updated JBDS-1573:
-------------------------------
Attachment: JBDS-1573.log
Seeing this in the .log if JBDS is closed and re-opened.
Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears
succesful - but the service is actually not deployed
-----------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Error Reporting, integration
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:30 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1573) Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Marek Baluch commented on JBDS-1573:
------------------------------------
Well 4.0.0.GA is affected too (with JBT 3.2.0.GA).
Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears
succesful - but the service is actually not deployed
-----------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Error Reporting, integration
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:39 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1573) Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Marek Baluch commented on JBDS-1573:
------------------------------------
OK I found that the attached process has the following structure bpelContent/bpelContent/.
That's the reason while the deployment does not work. When the I moved the files from
bpelContent/bpelContent to bpelContent everything started to work.
This is not an issue and can be closed.
Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears
succesful - but the service is actually not deployed
-----------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Error Reporting, integration
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:41 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBDS-1573) Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Marek Baluch edited comment on JBDS-1573 at 2/18/11 3:39 AM:
-------------------------------------------------------------
OK I found that the attached process has the following structure bpelContent/bpelContent/.
That's the reason why the deployment does not work. When I moved the files from
bpelContent/bpelContent to bpelContent everything started to work.
This is not an issue and can be closed.
was (Author: mbaluch(a)redhat.com):
OK I found that the attached process has the following structure
bpelContent/bpelContent/. That's the reason why the deployment does not work. When the
I moved the files from bpelContent/bpelContent to bpelContent everything started to work.
This is not an issue and can be closed.
Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears
succesful - but the service is actually not deployed
-----------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Error Reporting, integration
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:41 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBDS-1573) Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Marek Baluch edited comment on JBDS-1573 at 2/18/11 3:39 AM:
-------------------------------------------------------------
OK I found that the attached process has the following structure bpelContent/bpelContent/.
That's the reason why the deployment does not work. When the I moved the files from
bpelContent/bpelContent to bpelContent everything started to work.
This is not an issue and can be closed.
was (Author: mbaluch(a)redhat.com):
OK I found that the attached process has the following structure
bpelContent/bpelContent/. That's the reason while the deployment does not work. When
the I moved the files from bpelContent/bpelContent to bpelContent everything started to
work.
This is not an issue and can be closed.
Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears
succesful - but the service is actually not deployed
-----------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Error Reporting, integration
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:33 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1573) Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Len DiMaggio updated JBDS-1573:
-------------------------------
Summary: Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS 4.0
appears succesful - but the service is actually not deployed (was: Deploying a BPEL
project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually
not deployed)
Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS
4.0 appears succesful - but the service is actually not deployed
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Error Reporting, integration
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:35 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1573) Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Len DiMaggio updated JBDS-1573:
-------------------------------
Issue Type: Bug (was: Feature Request)
Marek is correct - thanks! - the project defined in the attached .zip file contains an
error in that the BPEL content is one layer too deep. But - from the user's
perspective, JBDS appeared to have the project correctly deployed.
Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS
4.0 appears succesful - but the service is actually not deployed
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Error Reporting, integration
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:44 a.m.
New subject: [JBoss JIRA] Assigned: (JBDS-1573) Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Brian Fitzpatrick reassigned JBDS-1573:
---------------------------------------
Assignee: Robert (Bob) Brodt
Bob, can you take a look at this along with the rest of your deployment stuff?
Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS
4.0 appears succesful - but the service is actually not deployed
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Error Reporting, integration
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Assignee: Robert (Bob) Brodt
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:46 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1573) Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Brian Fitzpatrick updated JBDS-1573:
------------------------------------
Fix Version/s: 4.0.1
LATER
Affects Version/s: 4.0.0.CR4
Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS
4.0 appears succesful - but the service is actually not deployed
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Error Reporting, integration
Affects Versions: 4.0.0.CR4
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Assignee: Robert (Bob) Brodt
Fix For: 4.0.1, LATER
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:40 p.m.
New subject: [JBoss JIRA] Commented: (JBDS-1573) Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Robert (Bob) Brodt commented on JBDS-1573:
------------------------------------------
The real problem is that there is no deployment descriptor file (deploy.xml) in the
project's BPEL content folder. I added some code to check for this condition and to
display a warning dialog.
Deployment validation should really be handled as a WizardFragment invoked from
org.eclipse.wst.server.ui.internal.wizard.ModifyModulesWizard but there is no
WizardFragment extension point for this class.
Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS
4.0 appears succesful - but the service is actually not deployed
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Error Reporting, integration
Affects Versions: 4.0.0.CR4
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Assignee: Robert (Bob) Brodt
Fix For: 4.1.0.GA, LATER
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:40 p.m.
New subject: [JBoss JIRA] Resolved: (JBDS-1573) Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Robert (Bob) Brodt resolved JBDS-1573.
--------------------------------------
Resolution: Done
fixed
Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS
4.0 appears succesful - but the service is actually not deployed
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Error Reporting, integration
Affects Versions: 4.0.0.CR4
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Assignee: Robert (Bob) Brodt
Fix For: 4.1.0.GA, LATER
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:56 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1573) Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Robert (Bob) Brodt updated JBDS-1573:
-------------------------------------
Fix Version/s: (was: LATER)
Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS
4.0 appears succesful - but the service is actually not deployed
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Error Reporting, integration
Affects Versions: 4.0.0.CR4
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Assignee: Robert (Bob) Brodt
Fix For: 4.1.0.M1
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:41 a.m.
New subject: [JBoss JIRA] Closed: (JBDS-1573) Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Pavol Srna closed JBDS-1573.
----------------------------
Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS
4.0 appears succesful - but the service is actually not deployed
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Error Reporting, integration
Affects Versions: 4.0.0.CR4
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Assignee: Robert (Bob) Brodt
Fix For: 4.1.0.M1
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:41 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1573) Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed
[
https://issues.jboss.org/browse/JBDS-1573?page=com.atlassian.jira.plugin....
]
Pavol Srna commented on JBDS-1573:
----------------------------------
Verified on jbdevstudio-product-linux-gtk-4.1.0.v201105091943R-H400-M1.
Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS
4.0 appears succesful - but the service is actually not deployed
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1573
URL: https://issues.jboss.org/browse/JBDS-1573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Error Reporting, integration
Affects Versions: 4.0.0.CR4
Environment: JBDS 4.0 CR4
SOA-P 5.1 CR1
Reporter: Len DiMaggio
Assignee: Robert (Bob) Brodt
Fix For: 4.1.0.M1
Attachments: helloworld.zip, JBDS-1573 - Screenshot-1.png, JBDS-1573-
Screenshot-2.png, JBDS-1573.log
To recreate the problem:
1) Install this into JBDS 4.0
JBoss BPEL Editor,
1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group
2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1
'bpel_helloworld' quickstart
3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it
4) Add the BPEL project to the server
5) See screenshot 1 - the BPEL project's jar appears to be there
6) Attemmpt to access the project - at this URL:
http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl
7) And a 404 - not found error is returned
Note that nothing is written to the workspace .log file or the server.log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5464
days inactive
5545
days old
jbosstools-issues@lists.jboss.org
17 comments
5 participants
participants (5)
-
Brian Fitzpatrick (JIRA) -
Len DiMaggio (JIRA)
-
Marek Baluch (JIRA)
-
Pavol Srna (JIRA)
-
Robert (Bob) Brodt (JIRA)