riftsaw SVN: r880 - trunk/distribution/src/main/release and 1 other directory.
by riftsaw-commits＠lists.jboss.org
Author: objectiser
Date: 2010-07-15 12:29:12 -0400 (Thu, 15 Jul 2010)
New Revision: 880
Modified:
branches/RiftSaw-2.1.x/distribution/src/main/release/ReleaseNotes.txt
trunk/distribution/src/main/release/ReleaseNotes.txt
Log:
Minor changes.
Modified: branches/RiftSaw-2.1.x/distribution/src/main/release/ReleaseNotes.txt
===================================================================
--- branches/RiftSaw-2.1.x/distribution/src/main/release/ReleaseNotes.txt 2010-07-15 13:42:58 UTC (rev 879)
+++ branches/RiftSaw-2.1.x/distribution/src/main/release/ReleaseNotes.txt 2010-07-15 16:29:12 UTC (rev 880)
@@ -2,12 +2,11 @@
===================
This is the final release for RiftSaw version 2.1. The summary of the main changes
-from 2.0.0.Final and 2.1.0.Final are:
+between 2.0.0.Final and 2.1.0.Final are:
- Support for WS-Security when RiftSaw used in conjunction with JBossWS-CXF
-- UDDI registration and lookup enabled by default (if ESB already deployed with
-UDDI v3 support)
+- UDDI registration and lookup
- Migration of persistence layer to a pure JPA approach, enabling any JPA
compliant persistence provider to be used. RiftSaw uses Hibernate as its
Modified: trunk/distribution/src/main/release/ReleaseNotes.txt
===================================================================
--- trunk/distribution/src/main/release/ReleaseNotes.txt 2010-07-15 13:42:58 UTC (rev 879)
+++ trunk/distribution/src/main/release/ReleaseNotes.txt 2010-07-15 16:29:12 UTC (rev 880)
@@ -2,12 +2,11 @@
===================
This is the final release for RiftSaw version 2.1. The summary of the main changes
-from 2.0.0.Final and 2.1.0.Final are:
+between 2.0.0.Final and 2.1.0.Final are:
- Support for WS-Security when RiftSaw used in conjunction with JBossWS-CXF
-- UDDI registration and lookup enabled by default (if ESB already deployed with
-UDDI v3 support)
+- UDDI registration and lookup
- Migration of persistence layer to a pure JPA approach, enabling any JPA
compliant persistence provider to be used. RiftSaw uses Hibernate as its
13 years, 9 months
riftsaw SVN: r879 - branches/ODE/RiftSaw-ODE-trunk/bpel-test/src/test/java/org/apache/ode/test.
by riftsaw-commits＠lists.jboss.org
Author: jeff.yuchang
Date: 2010-07-15 09:42:58 -0400 (Thu, 15 Jul 2010)
New Revision: 879
Modified:
branches/ODE/RiftSaw-ODE-trunk/bpel-test/src/test/java/org/apache/ode/test/ExternalVariableTest.java
Log:
* RIFTSAW-248.
Modified: branches/ODE/RiftSaw-ODE-trunk/bpel-test/src/test/java/org/apache/ode/test/ExternalVariableTest.java
===================================================================
--- branches/ODE/RiftSaw-ODE-trunk/bpel-test/src/test/java/org/apache/ode/test/ExternalVariableTest.java 2010-07-15 13:18:20 UTC (rev 878)
+++ branches/ODE/RiftSaw-ODE-trunk/bpel-test/src/test/java/org/apache/ode/test/ExternalVariableTest.java 2010-07-15 13:42:58 UTC (rev 879)
@@ -86,24 +86,35 @@
}
}
+ public void tearDown() throws Exception {
+ super.tearDown();
+ _jdbcext = null;
+ _db.shutdown();
+ }
+
@Ignore("RIFTSAW-248")
@Test
public void testHelloWorld2() throws Throwable {
go("/bpel/2.0/ExtVar");
}
-
+
+ @Ignore("RIFTSAW-248, this got OOM heap size in hudson job, not reproducable in local machine")
@Test
public void testExtVar2() throws Throwable {
go("/bpel/2.0/ExtVar2");
}
-
+
+ @Ignore("RIFTSAW-248, this got OOM heap size in hudson job, not reproducable in local machine")
@Test
public void testExtVar3() throws Throwable {
go("/bpel/2.0/ExtVar3");
}
+ @Ignore("RIFTSAW-248, this got OOM heap size in hudson job, not reproducable in local machine")
@Test
public void testExtVarKeyGen() throws Throwable {
go("/bpel/2.0/ExtVar-GenKey");
}
+
+
}
13 years, 9 months
riftsaw SVN: r878 - trunk/distribution/src/main/release and 1 other directory.
by riftsaw-commits＠lists.jboss.org
Author: objectiser
Date: 2010-07-15 09:18:20 -0400 (Thu, 15 Jul 2010)
New Revision: 878
Modified:
branches/RiftSaw-2.1.x/distribution/src/main/release/ReleaseNotes.txt
trunk/distribution/src/main/release/ReleaseNotes.txt
Log:
Updated release notes.
Modified: branches/RiftSaw-2.1.x/distribution/src/main/release/ReleaseNotes.txt
===================================================================
--- branches/RiftSaw-2.1.x/distribution/src/main/release/ReleaseNotes.txt 2010-07-15 12:46:27 UTC (rev 877)
+++ branches/RiftSaw-2.1.x/distribution/src/main/release/ReleaseNotes.txt 2010-07-15 13:18:20 UTC (rev 878)
@@ -1,3 +1,46 @@
+RiftSaw 2.1.0.Final
+===================
+
+This is the final release for RiftSaw version 2.1. The summary of the main changes
+from 2.0.0.Final and 2.1.0.Final are:
+
+- Support for WS-Security when RiftSaw used in conjunction with JBossWS-CXF
+
+- UDDI registration and lookup enabled by default (if ESB already deployed with
+UDDI v3 support)
+
+- Migration of persistence layer to a pure JPA approach, enabling any JPA
+compliant persistence provider to be used. RiftSaw uses Hibernate as its
+default JPA provider
+
+- Update from ODE1.3.3 to ODE1.3.4
+
+- ODE project has now been mavenized
+
+- More examples
+
+- Many bug fixes
+
+- Now dependent upon ESB 4.8 or higher (instead of ESB 4.7)
+
+Due to the change from the hibernate native persistence support to a JPA+hibernate
+approach, it is necessary to update to the new schema. Instructions for doing
+this can be found in the Installation Instructions section of the Getting Started Guide.
+
+The detailed report for this release can be found at:
+https://jira.jboss.org/secure/ReleaseNote.jspa?projectId=12310843&version=12315122
+
+Known Issues:
+
+RIFTSAW-193 - Wrapped style parameters are currently not supported.
+
+RIFTSAW-238 - If a process definition has multiple versions, one active and the others retired,
+then undeploying the active version causes the web service associated with the process to be
+unpublished, even if active process instances still exist for the retired versions.
+
+
+
+
RiftSaw 2.1.0.CR2
=================
Modified: trunk/distribution/src/main/release/ReleaseNotes.txt
===================================================================
--- trunk/distribution/src/main/release/ReleaseNotes.txt 2010-07-15 12:46:27 UTC (rev 877)
+++ trunk/distribution/src/main/release/ReleaseNotes.txt 2010-07-15 13:18:20 UTC (rev 878)
@@ -1,3 +1,46 @@
+RiftSaw 2.1.0.Final
+===================
+
+This is the final release for RiftSaw version 2.1. The summary of the main changes
+from 2.0.0.Final and 2.1.0.Final are:
+
+- Support for WS-Security when RiftSaw used in conjunction with JBossWS-CXF
+
+- UDDI registration and lookup enabled by default (if ESB already deployed with
+UDDI v3 support)
+
+- Migration of persistence layer to a pure JPA approach, enabling any JPA
+compliant persistence provider to be used. RiftSaw uses Hibernate as its
+default JPA provider
+
+- Update from ODE1.3.3 to ODE1.3.4
+
+- ODE project has now been mavenized
+
+- More examples
+
+- Many bug fixes
+
+- Now dependent upon ESB 4.8 or higher (instead of ESB 4.7)
+
+Due to the change from the hibernate native persistence support to a JPA+hibernate
+approach, it is necessary to update to the new schema. Instructions for doing
+this can be found in the Installation Instructions section of the Getting Started Guide.
+
+The detailed report for this release can be found at:
+https://jira.jboss.org/secure/ReleaseNote.jspa?projectId=12310843&version=12315122
+
+Known Issues:
+
+RIFTSAW-193 - Wrapped style parameters are currently not supported.
+
+RIFTSAW-238 - If a process definition has multiple versions, one active and the others retired,
+then undeploying the active version causes the web service associated with the process to be
+unpublished, even if active process instances still exist for the retired versions.
+
+
+
+
RiftSaw 2.1.0.CR2
=================
13 years, 9 months
riftsaw SVN: r877 - branches/RiftSaw-ODE-2.1.x/bpel-test/src/test/java/org/apache/ode/test.
by riftsaw-commits＠lists.jboss.org
Author: jeff.yuchang
Date: 2010-07-15 08:46:27 -0400 (Thu, 15 Jul 2010)
New Revision: 877
Modified:
branches/RiftSaw-ODE-2.1.x/bpel-test/src/test/java/org/apache/ode/test/ExternalVariableTest.java
Log:
* RIFTSAW-248, @Ignore these three test cases for further investigation, as these can not be reproduced locally.
Modified: branches/RiftSaw-ODE-2.1.x/bpel-test/src/test/java/org/apache/ode/test/ExternalVariableTest.java
===================================================================
--- branches/RiftSaw-ODE-2.1.x/bpel-test/src/test/java/org/apache/ode/test/ExternalVariableTest.java 2010-07-15 11:57:53 UTC (rev 876)
+++ branches/RiftSaw-ODE-2.1.x/bpel-test/src/test/java/org/apache/ode/test/ExternalVariableTest.java 2010-07-15 12:46:27 UTC (rev 877)
@@ -97,17 +97,20 @@
public void testHelloWorld2() throws Throwable {
go("/bpel/2.0/ExtVar");
}
-
+
+ @Ignore("RIFTSAW-248, this got OOM heap size in hudson job, not reproducable in local machine")
@Test
public void testExtVar2() throws Throwable {
go("/bpel/2.0/ExtVar2");
}
-
+
+ @Ignore("RIFTSAW-248, this got OOM heap size in hudson job, not reproducable in local machine")
@Test
public void testExtVar3() throws Throwable {
go("/bpel/2.0/ExtVar3");
}
+ @Ignore("RIFTSAW-248, this got OOM heap size in hudson job, not reproducable in local machine")
@Test
public void testExtVarKeyGen() throws Throwable {
go("/bpel/2.0/ExtVar-GenKey");
13 years, 9 months
riftsaw SVN: r876 - branches/RiftSaw-ODE-2.1.x/bpel-test/src/test/java/org/apache/ode/test.
by riftsaw-commits＠lists.jboss.org
Author: jeff.yuchang
Date: 2010-07-15 07:57:53 -0400 (Thu, 15 Jul 2010)
New Revision: 876
Modified:
branches/RiftSaw-ODE-2.1.x/bpel-test/src/test/java/org/apache/ode/test/ExternalVariableTest.java
Log:
* attempt to fix OOM in hudson job.
Modified: branches/RiftSaw-ODE-2.1.x/bpel-test/src/test/java/org/apache/ode/test/ExternalVariableTest.java
===================================================================
--- branches/RiftSaw-ODE-2.1.x/bpel-test/src/test/java/org/apache/ode/test/ExternalVariableTest.java 2010-07-15 11:56:27 UTC (rev 875)
+++ branches/RiftSaw-ODE-2.1.x/bpel-test/src/test/java/org/apache/ode/test/ExternalVariableTest.java 2010-07-15 11:57:53 UTC (rev 876)
@@ -86,6 +86,12 @@
}
}
+ public void tearDown() throws Exception {
+ super.tearDown();
+ _jdbcext = null;
+ _db.shutdown();
+ }
+
@Ignore("RIFTSAW-248")
@Test
public void testHelloWorld2() throws Throwable {
@@ -106,4 +112,6 @@
public void testExtVarKeyGen() throws Throwable {
go("/bpel/2.0/ExtVar-GenKey");
}
+
+
}
13 years, 9 months
riftsaw SVN: r875 - trunk/docs/docbook/userguide/src/main/module and 1 other directory.
by riftsaw-commits＠lists.jboss.org
Author: objectiser
Date: 2010-07-15 07:56:27 -0400 (Thu, 15 Jul 2010)
New Revision: 875
Modified:
branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/uddi.xml
trunk/docs/docbook/userguide/src/main/module/uddi.xml
Log:
Remove references to ESB4.7 from UDDI documentation.
Modified: branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/uddi.xml
===================================================================
--- branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/uddi.xml 2010-07-15 04:22:37 UTC (rev 874)
+++ branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/uddi.xml 2010-07-15 11:56:27 UTC (rev 875)
@@ -27,7 +27,7 @@
<para>
By default RiftSaw uses the jUDDI client libraries of JBossESB/SOA-P, and the client
- configuration is found in the deploy/jbossesb.saw/esb.juddi.client.xml. Both the
+ configuration is found in the deploy/jbossesb.sar/esb.juddi.client.xml. Both the
name of the ClerkManager and the Clerk itself are specified in the
<emphasis>bpel.properties</emphasis> file.
</para>
@@ -68,31 +68,26 @@
<entry>bpel.uddi.client.impl</entry>
<entry>String (org.jboss.soa.bpel.uddi.UDDIRegistrationImpl)</entry>
<entry>
- Name of the a class that implements the org.jboss.soa.bpel.runtime.engine.ode.UDDIRegistration interface.
- The RiftSaw installation process set this value to org.jboss.soa.bpel.uddi300.UDDI300RegistrationImpl
- if JBossESB-4.7 is detected. JBossESB-4.7 uses
- the jUDDI-3.0.0 client libary, while SOA-P-5.0.0 and future version of JBossESB will use jUDDI-3.0.1 or higher and
- for those it is set to org.jboss.soa.bpel.uddi.UDDIRegistrationImpl.
+ Name of the class that implements the <emphasis>org.jboss.soa.bpel.runtime.engine.ode.UDDIRegistration</emphasis> interface.
</entry>
</row>
<row>
<entry>bpel.uddi.clerk.config</entry>
<entry>String (not used by default)</entry>
<entry>
- Defines the path to the bpel.uddi.client.xml config file. This can be left commented out if
- you want to use the jbossesb.sar/esb.uddi.client.xml. However in that case a bpel.uddi.clerk.manager
- needs to be defined.
+ Defines the path to the <filename>bpel.uddi.client.xml</filename> config file. This can be left commented out if
+ you want to use the <filename>jbossesb.sar/esb.uddi.client.xml</filename>. However in that case a
+ <filename>bpel.uddi.clerk.manager</filename> needs to be defined.
</entry>
</row>
<row>
<entry>bpel.uddi.clerk.manager</entry>
<entry>String (esb-registry)</entry>
<entry>
- Defines the ClerkManager name that will be used if the bpel.uddi.clerk.config is left commented out.
+ Defines the ClerkManager name that will be used if the <emphasis>bpel.uddi.clerk.config</emphasis> is left commented out.
This value should correspond to the name of the manager
- in the esb.juddi.client.xml. For JBossESB-4.7 this is 'test-manager', while for SOA-P-5.0.0
- and newer version of JBossESB it is 'esb-registry'. Note that if the bpel.uddi.clerk.config is defined, the
- setting of the bpel.uddi.clerk.manager is ignored.
+ in the <filename>esb.juddi.client.xml</filename>. Note that if the <emphasis>bpel.uddi.clerk.config</emphasis> is defined, the
+ setting of the <emphasis>bpel.uddi.clerk.manager</emphasis> is ignored.
</entry>
</row>
<row>
@@ -100,7 +95,7 @@
<entry>String (BPEL_clerk)</entry>
<entry>
Defines the Clerk name that will be used. This value should correspond to the name of the clerk
- in the esb.juddi.client.xml. By default this is set to 'BPEL_clerk'.
+ in the <filename>esb.juddi.client.xml</filename>. By default this is set to 'BPEL_clerk'.
</entry>
</row>
<row>
@@ -122,20 +117,13 @@
<section>
<title>Default configurations</title>
- <para>When RiftSaw is deployed to a JBossAS-5.1.0, jUDDI v3 is not installed, and therefore
+ <para>When RiftSaw is deployed to JBossAS-5.1.0, jUDDI v3 is not installed, and therefore
the UDDI integration is turned off (bpel.uddi.registration=false).</para>
- <para>When RiftSaw is deployed to JBossAS-5.1.0 + JBossESB-4.7, the UDDI integration is
- turned on. By default we use the jUDDI client library which ships with the JBossESB, which
- is configured in the <filename>jbossesb.sar/esb.uddi.client.xml</filename>,
- with manager name 'test-manager'. The <emphasis>bpel.uddi.client.impl</emphasis> is set
- to <emphasis>org.jboss.soa.bpel.uddi300.UDDI300RegistrationImpl</emphasis>.
- </para>
-
- <para>When RiftSaw is deployed to SOA-P-5.0.0 (or JBossESB > 4.7) UDDI integration is
+ <para>When RiftSaw is deployed to SOA-P-5.0.0 (or JBossESB 4.8 or higher) UDDI integration is
turned on and the <emphasis>bpel.uddi.client.impl</emphasis> is set to
<emphasis>org.jboss.soa.bpel.uddi.UDDIRegistrationImpl</emphasis>.
- Again the <filename>jbossesb.sar/esb.uddi.client.xml</filename> is used, with manager name 'esb.registry'.
+ The <filename>jbossesb.sar/esb.uddi.client.xml</filename> is used, with manager name 'esb.registry'.
</para>
</section>
@@ -174,12 +162,6 @@
to turn this value to "false" once you are content with the UDDI Seed Data.
</para>
-
- <warning><para>When running on JBossESB-4.7, the root seed data will only be installed if the UDDI tables are
- still empty. This means that you need to make sure that the jUDDI Root Seed Data install process
- did not run before installing RiftSaw. In other words, do not start JBossESB-4.7 before installing
- RiftSaw.</para></warning>
-
</section>
</chapter>
Modified: trunk/docs/docbook/userguide/src/main/module/uddi.xml
===================================================================
--- trunk/docs/docbook/userguide/src/main/module/uddi.xml 2010-07-15 04:22:37 UTC (rev 874)
+++ trunk/docs/docbook/userguide/src/main/module/uddi.xml 2010-07-15 11:56:27 UTC (rev 875)
@@ -27,7 +27,7 @@
<para>
By default RiftSaw uses the jUDDI client libraries of JBossESB/SOA-P, and the client
- configuration is found in the deploy/jbossesb.saw/esb.juddi.client.xml. Both the
+ configuration is found in the deploy/jbossesb.sar/esb.juddi.client.xml. Both the
name of the ClerkManager and the Clerk itself are specified in the
<emphasis>bpel.properties</emphasis> file.
</para>
@@ -68,31 +68,26 @@
<entry>bpel.uddi.client.impl</entry>
<entry>String (org.jboss.soa.bpel.uddi.UDDIRegistrationImpl)</entry>
<entry>
- Name of the a class that implements the org.jboss.soa.bpel.runtime.engine.ode.UDDIRegistration interface.
- The RiftSaw installation process set this value to org.jboss.soa.bpel.uddi300.UDDI300RegistrationImpl
- if JBossESB-4.7 is detected. JBossESB-4.7 uses
- the jUDDI-3.0.0 client libary, while SOA-P-5.0.0 and future version of JBossESB will use jUDDI-3.0.1 or higher and
- for those it is set to org.jboss.soa.bpel.uddi.UDDIRegistrationImpl.
+ Name of the class that implements the <emphasis>org.jboss.soa.bpel.runtime.engine.ode.UDDIRegistration</emphasis> interface.
</entry>
</row>
<row>
<entry>bpel.uddi.clerk.config</entry>
<entry>String (not used by default)</entry>
<entry>
- Defines the path to the bpel.uddi.client.xml config file. This can be left commented out if
- you want to use the jbossesb.sar/esb.uddi.client.xml. However in that case a bpel.uddi.clerk.manager
- needs to be defined.
+ Defines the path to the <filename>bpel.uddi.client.xml</filename> config file. This can be left commented out if
+ you want to use the <filename>jbossesb.sar/esb.uddi.client.xml</filename>. However in that case a
+ <filename>bpel.uddi.clerk.manager</filename> needs to be defined.
</entry>
</row>
<row>
<entry>bpel.uddi.clerk.manager</entry>
<entry>String (esb-registry)</entry>
<entry>
- Defines the ClerkManager name that will be used if the bpel.uddi.clerk.config is left commented out.
+ Defines the ClerkManager name that will be used if the <emphasis>bpel.uddi.clerk.config</emphasis> is left commented out.
This value should correspond to the name of the manager
- in the esb.juddi.client.xml. For JBossESB-4.7 this is 'test-manager', while for SOA-P-5.0.0
- and newer version of JBossESB it is 'esb-registry'. Note that if the bpel.uddi.clerk.config is defined, the
- setting of the bpel.uddi.clerk.manager is ignored.
+ in the <filename>esb.juddi.client.xml</filename>. Note that if the <emphasis>bpel.uddi.clerk.config</emphasis> is defined, the
+ setting of the <emphasis>bpel.uddi.clerk.manager</emphasis> is ignored.
</entry>
</row>
<row>
@@ -100,7 +95,7 @@
<entry>String (BPEL_clerk)</entry>
<entry>
Defines the Clerk name that will be used. This value should correspond to the name of the clerk
- in the esb.juddi.client.xml. By default this is set to 'BPEL_clerk'.
+ in the <filename>esb.juddi.client.xml</filename>. By default this is set to 'BPEL_clerk'.
</entry>
</row>
<row>
@@ -122,20 +117,13 @@
<section>
<title>Default configurations</title>
- <para>When RiftSaw is deployed to a JBossAS-5.1.0, jUDDI v3 is not installed, and therefore
+ <para>When RiftSaw is deployed to JBossAS-5.1.0, jUDDI v3 is not installed, and therefore
the UDDI integration is turned off (bpel.uddi.registration=false).</para>
- <para>When RiftSaw is deployed to JBossAS-5.1.0 + JBossESB-4.7, the UDDI integration is
- turned on. By default we use the jUDDI client library which ships with the JBossESB, which
- is configured in the <filename>jbossesb.sar/esb.uddi.client.xml</filename>,
- with manager name 'test-manager'. The <emphasis>bpel.uddi.client.impl</emphasis> is set
- to <emphasis>org.jboss.soa.bpel.uddi300.UDDI300RegistrationImpl</emphasis>.
- </para>
-
- <para>When RiftSaw is deployed to SOA-P-5.0.0 (or JBossESB > 4.7) UDDI integration is
+ <para>When RiftSaw is deployed to SOA-P-5.0.0 (or JBossESB 4.8 or higher) UDDI integration is
turned on and the <emphasis>bpel.uddi.client.impl</emphasis> is set to
<emphasis>org.jboss.soa.bpel.uddi.UDDIRegistrationImpl</emphasis>.
- Again the <filename>jbossesb.sar/esb.uddi.client.xml</filename> is used, with manager name 'esb.registry'.
+ The <filename>jbossesb.sar/esb.uddi.client.xml</filename> is used, with manager name 'esb.registry'.
</para>
</section>
@@ -174,12 +162,6 @@
to turn this value to "false" once you are content with the UDDI Seed Data.
</para>
-
- <warning><para>When running on JBossESB-4.7, the root seed data will only be installed if the UDDI tables are
- still empty. This means that you need to make sure that the jUDDI Root Seed Data install process
- did not run before installing RiftSaw. In other words, do not start JBossESB-4.7 before installing
- RiftSaw.</para></warning>
-
</section>
</chapter>
13 years, 9 months
