3:50 p.m.
Install BPEL in all config
--------------------------
Key: JBAS-4151
URL: http://jira.jboss.com/jira/browse/JBAS-4151
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Assigned To: Alejandro Guizar
Fix For: JBossAS-4.2.0.GA
BPEL should be installed in the all config.
In the jbossws userguide we claim that we support bpel. Recent changes in AS thirdparty
(jaxen) however broke bpel support.
These changes would stay unnoticed after jbossws-2.0.0.GA is released.
Therefore jbossws now includes a bpel dependency in its component-info.xml and BPEL should
do likewise for all its dependencies.
Alejandro, I aded http://repository.jboss.com/jbpm/bpel/1.1.Beta3/component-info.xml
Please make sure that declare your dependencies appropriately. Otherwise we end up with a
sittuation that AS and JBWS are released but BPEL does not work.
--
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
5:38 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4151) Install BPEL in all config
[ http://jira.jboss.com/jira/browse/JBAS-4151?page=comments#action_12354158 ]
Alejandro Guizar commented on JBAS-4151:
----------------------------------------
Besides declaring the dependencies, what other tasks are required to install BPEL in the
all configuration?
Install BPEL in all config
--------------------------
Key: JBAS-4151
URL: http://jira.jboss.com/jira/browse/JBAS-4151
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Alejandro Guizar
Fix For: JBossAS-4.2.0.GA
BPEL should be installed in the all config.
In the jbossws userguide we claim that we support bpel. Recent changes in AS thirdparty
(jaxen) however broke bpel support.
These changes would stay unnoticed after jbossws-2.0.0.GA is released.
Therefore jbossws now includes a bpel dependency in its component-info.xml and BPEL
should do likewise for all its dependencies.
Alejandro, I aded http://repository.jboss.com/jbpm/bpel/1.1.Beta3/component-info.xml
Please make sure that declare your dependencies appropriately. Otherwise we end up with a
sittuation that AS and JBWS are released but BPEL does not work.
--
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
4:13 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4151) Install BPEL in all config
[ http://jira.jboss.com/jira/browse/JBAS-4151?page=comments#action_12354222 ]
Thomas Diesler commented on JBAS-4151:
--------------------------------------
You should unpack the sar
Install BPEL in all config
--------------------------
Key: JBAS-4151
URL: http://jira.jboss.com/jira/browse/JBAS-4151
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Alejandro Guizar
Fix For: JBossAS-4.2.0.GA
BPEL should be installed in the all config.
In the jbossws userguide we claim that we support bpel. Recent changes in AS thirdparty
(jaxen) however broke bpel support.
These changes would stay unnoticed after jbossws-2.0.0.GA is released.
Therefore jbossws now includes a bpel dependency in its component-info.xml and BPEL
should do likewise for all its dependencies.
Alejandro, I aded http://repository.jboss.com/jbpm/bpel/1.1.Beta3/component-info.xml
Please make sure that declare your dependencies appropriately. Otherwise we end up with a
sittuation that AS and JBWS are released but BPEL does not work.
--
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
4:11 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4151) Install BPEL in all config
[ http://jira.jboss.com/jira/browse/JBAS-4151?page=comments#action_12354246 ]
Dimitris Andreadis commented on JBAS-4151:
------------------------------------------
Is there *any* integration test for that?
Install BPEL in all config
--------------------------
Key: JBAS-4151
URL: http://jira.jboss.com/jira/browse/JBAS-4151
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Alejandro Guizar
Fix For: JBossAS-4.2.0.GA
BPEL should be installed in the all config.
In the jbossws userguide we claim that we support bpel. Recent changes in AS thirdparty
(jaxen) however broke bpel support.
These changes would stay unnoticed after jbossws-2.0.0.GA is released.
Therefore jbossws now includes a bpel dependency in its component-info.xml and BPEL
should do likewise for all its dependencies.
Alejandro, I aded http://repository.jboss.com/jbpm/bpel/1.1.Beta3/component-info.xml
Please make sure that declare your dependencies appropriately. Otherwise we end up with a
sittuation that AS and JBWS are released but BPEL does not work.
--
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
8:38 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4151) Install BPEL in all config
[ http://jira.jboss.com/jira/browse/JBAS-4151?page=comments#action_12354254 ]
Alejandro Guizar commented on JBAS-4151:
----------------------------------------
There is some test code and resources living in trunk. Look at
https://svn.jboss.org/repos/jbossas/trunk/testsuite/src/main/org/jboss/te...
These tests create a custom configuration. They do not work with the current BPEL version.
Updating them is just a matter of rearranging the resources, tough.
Install BPEL in all config
--------------------------
Key: JBAS-4151
URL: http://jira.jboss.com/jira/browse/JBAS-4151
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Alejandro Guizar
Fix For: JBossAS-4.2.0.GA
BPEL should be installed in the all config.
In the jbossws userguide we claim that we support bpel. Recent changes in AS thirdparty
(jaxen) however broke bpel support.
These changes would stay unnoticed after jbossws-2.0.0.GA is released.
Therefore jbossws now includes a bpel dependency in its component-info.xml and BPEL
should do likewise for all its dependencies.
Alejandro, I aded http://repository.jboss.com/jbpm/bpel/1.1.Beta3/component-info.xml
Please make sure that declare your dependencies appropriately. Otherwise we end up with a
sittuation that AS and JBWS are released but BPEL does not work.
--
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
9:03 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4151) Install BPEL in all config
[ http://jira.jboss.com/jira/browse/JBAS-4151?page=comments#action_12354256 ]
Dimitris Andreadis commented on JBAS-4151:
------------------------------------------
So they need to be ported to Branch_4_2.
Install BPEL in all config
--------------------------
Key: JBAS-4151
URL: http://jira.jboss.com/jira/browse/JBAS-4151
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Alejandro Guizar
Fix For: JBossAS-4.2.0.GA
BPEL should be installed in the all config.
In the jbossws userguide we claim that we support bpel. Recent changes in AS thirdparty
(jaxen) however broke bpel support.
These changes would stay unnoticed after jbossws-2.0.0.GA is released.
Therefore jbossws now includes a bpel dependency in its component-info.xml and BPEL
should do likewise for all its dependencies.
Alejandro, I aded http://repository.jboss.com/jbpm/bpel/1.1.Beta3/component-info.xml
Please make sure that declare your dependencies appropriately. Otherwise we end up with a
sittuation that AS and JBWS are released but BPEL does not work.
--
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
9:09 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4151) Install BPEL in all config
[ http://jira.jboss.com/jira/browse/JBAS-4151?page=comments#action_12354429 ]
Alejandro Guizar commented on JBAS-4151:
----------------------------------------
When testing against 4.2, default configuration, started with "run" my WS4EE
clients get the following exception when retrieving the MBeanServerConnection.
javax.naming.CommunicationException [Root exception is java.rmi.ConnectException:
Connection refused to host: 68.90.188.248;
nested exception is: java.net.ConnectException: Connection refused: connect]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:722)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.test.ws.JBossTestDeployer.getServer(JBossTestDeployer.java:56)
at org.jboss.test.ws.JBossTestDeployer.undeploy(JBossTestDeployer.java:49)
at org.jboss.test.ws.JBossWSTestHelper.undeploy(JBossWSTestHelper.java:55)
at org.jboss.test.ws.JBossWSTestSetup.setUp(JBossWSTestSetup.java:77)
where 68.90.188.248 is my current IP.
When starting with "run -b localhost" the above exception dissappears. I believe
this is linked to Dimitris' switching the default ip address binding from 0.0.0.0 to
127.0.0.1, but I have not confirmed yet. Just letting you know in case you encounter the
above exception.
Install BPEL in all config
--------------------------
Key: JBAS-4151
URL: http://jira.jboss.com/jira/browse/JBAS-4151
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Alejandro Guizar
Fix For: JBossAS-4.2.0.GA
BPEL should be installed in the all config.
In the jbossws userguide we claim that we support bpel. Recent changes in AS thirdparty
(jaxen) however broke bpel support.
These changes would stay unnoticed after jbossws-2.0.0.GA is released.
Therefore jbossws now includes a bpel dependency in its component-info.xml and BPEL
should do likewise for all its dependencies.
Alejandro, I aded http://repository.jboss.com/jbpm/bpel/1.1.Beta3/component-info.xml
Please make sure that declare your dependencies appropriately. Otherwise we end up with a
sittuation that AS and JBWS are released but BPEL does not work.
--
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
11:48 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4151) Install BPEL in all config
[ http://jira.jboss.com/jira/browse/JBAS-4151?page=all ]
Dimitris Andreadis updated JBAS-4151:
-------------------------------------
Component/s: Other
Install BPEL in all config
--------------------------
Key: JBAS-4151
URL: http://jira.jboss.com/jira/browse/JBAS-4151
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Reporter: Thomas Diesler
Assigned To: Alejandro Guizar
Fix For: JBossAS-4.2.0.GA
BPEL should be installed in the all config.
In the jbossws userguide we claim that we support bpel. Recent changes in AS thirdparty
(jaxen) however broke bpel support.
These changes would stay unnoticed after jbossws-2.0.0.GA is released.
Therefore jbossws now includes a bpel dependency in its component-info.xml and BPEL
should do likewise for all its dependencies.
Alejandro, I aded http://repository.jboss.com/jbpm/bpel/1.1.Beta3/component-info.xml
Please make sure that declare your dependencies appropriately. Otherwise we end up with a
sittuation that AS and JBWS are released but BPEL does not work.
--
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
2:55 p.m.
New subject: [JBoss JIRA] Resolved: (JBAS-4151) Install BPEL in all config
[ http://jira.jboss.com/jira/browse/JBAS-4151?page=all ]
Alejandro Guizar resolved JBAS-4151.
------------------------------------
Resolution: Done
Install BPEL in all config
--------------------------
Key: JBAS-4151
URL: http://jira.jboss.com/jira/browse/JBAS-4151
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Reporter: Thomas Diesler
Assigned To: Alejandro Guizar
Fix For: JBossAS-4.2.0.GA
BPEL should be installed in the all config.
In the jbossws userguide we claim that we support bpel. Recent changes in AS thirdparty
(jaxen) however broke bpel support.
These changes would stay unnoticed after jbossws-2.0.0.GA is released.
Therefore jbossws now includes a bpel dependency in its component-info.xml and BPEL
should do likewise for all its dependencies.
Alejandro, I aded http://repository.jboss.com/jbpm/bpel/1.1.Beta3/component-info.xml
Please make sure that declare your dependencies appropriately. Otherwise we end up with a
sittuation that AS and JBWS are released but BPEL does not work.
--
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
2:55 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4151) Install BPEL in all config
[ http://jira.jboss.com/jira/browse/JBAS-4151?page=comments#action_12357071 ]
Alejandro Guizar commented on JBAS-4151:
----------------------------------------
As discussed in an email thread, BPEL is part of the ESB platform as opposed to the AS
platform. We will not include BPEL in JBoss AS 4.2 but we will verify compatibility with
it as part of the JBossWS test suite.
We have verified compatibility between JBoss AS 4.2.0.GA and jBPM BPEL 1.1.Beta4, so I am
resolving this issue.
Install BPEL in all config
--------------------------
Key: JBAS-4151
URL: http://jira.jboss.com/jira/browse/JBAS-4151
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Reporter: Thomas Diesler
Assigned To: Alejandro Guizar
Fix For: JBossAS-4.2.0.GA
BPEL should be installed in the all config.
In the jbossws userguide we claim that we support bpel. Recent changes in AS thirdparty
(jaxen) however broke bpel support.
These changes would stay unnoticed after jbossws-2.0.0.GA is released.
Therefore jbossws now includes a bpel dependency in its component-info.xml and BPEL
should do likewise for all its dependencies.
Alejandro, I aded http://repository.jboss.com/jbpm/bpel/1.1.Beta3/component-info.xml
Please make sure that declare your dependencies appropriately. Otherwise we end up with a
sittuation that AS and JBWS are released but BPEL does not work.
--
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
7052
days inactive
7079
days old
9 comments
3 participants
participants (3)
-
Alejandro Guizar (JIRA) -
Dimitris Andreadis (JIRA)
-
Thomas Diesler (JIRA)