[jBPM Development] - local history for the jbpm web editor
by Gábor Farkas
Gábor Farkas [https://community.jboss.org/people/hhcofcmds] created the discussion
"local history for the jbpm web editor"
To view the discussion, visit: https://community.jboss.org/message/762978#762978
--------------------------------------------------------------
Hello,
We've created a prototype for a local history functionality for the jbpm-designer, we needed it for multiple reasons. It stores data in the browser localStorage, so it also serves a bit like 'undo after save'. It checks the json representation of the process every minute and if it differs, it creates a new local history entry, including a thumbnailed screenshot. It's available after browser restart too, so if you accidentally close the browser, you can still restore your work.
Here's a small screenshot.
https://docs.google.com/open?id=0Bxw7L2kmpno8RkJUY3Zjd0I4Mlk https://docs.google.com/open?id=0Bxw7L2kmpno8RkJUY3Zjd0I4Mlk
Needs quite much elaboration, but it's already functional and useful for our needs.
If you find it interesting, we'd be happy to share it with the community.
regards,
Gabor Farkas
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/762978#762978]
Start a new discussion in jBPM Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 6 months
[JBoss AS 7 Development] - Error trying to Validate jboss-ejb3.xml
by vam kris
vam kris [https://community.jboss.org/people/vamsi2012] created the discussion
"Error trying to Validate jboss-ejb3.xml"
To view the discussion, visit: https://community.jboss.org/message/762035#762035
--------------------------------------------------------------
In the Jboss-ejb3.xml,its trying to reference http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd something like this.
In the above,We are referencing both Schemas http://www.jboss.com/xml/ns/javaee http://www.jboss.com/xml/ns/javaee jboss-ejb3-2_0.xsd (namespace is http://www.jboss.com/xml/ns/javaee http://www.jboss.com/xml/ns/javaee ) and http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd (namespace is http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee) under xsi:schemaLocation. jboss-ejb3-2_0.xsd inturn references jboss-ejb3-spec-2_0.xsd something like this
There is an ambiguity error or the Conflict that is Caused for the Element in both jboss-ejb3-spec-2_0.xsd and ejb-jar_3_1.xsd 1. jboss-ejb3-spec-2_0.xsd Defines the Defines the Element as below:
It references assembly-descriptor like this: 2. http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd Defines the Element something like this The assembly-descriptorType defines application-assembly information. The application-assembly information consists of the following parts: the definition of security roles, the definition of method permissions, the definition of transaction attributes for enterprise beans with container-managed transaction demarcation, the definition of interceptor bindings, a list of methods to be excluded from being invoked, and a list of exception types that should be treated as application exceptions. All the parts are optional in the sense that they are omitted if the lists represented by them are empty. Providing an assembly-descriptor in the deployment descriptor is optional for the ejb-jar or .war file producer. Because of the above Scenario when I am trying to Validate the XML ,I am getting the following error: cos-nonambig: " http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee":assembly-descriptor and " http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee":assembly-descriptor (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles. Attached are the 3 XSD Files. Could anyone help me resolve this.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/762035#762035]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 6 months
[JBoss AS 7 Development] - Creating .dodeploy marker file
by Shivani Sharma
Shivani Sharma [https://community.jboss.org/people/jboss7_newbie] created the discussion
"Creating .dodeploy marker file"
To view the discussion, visit: https://community.jboss.org/message/762747#762747
--------------------------------------------------------------
I am trying to integrate ActiveMQ-5.6 with Jboss7.activemq.rar is placed in standalone/deployments folder and I read in many posts that to enable Jboss7 to deploy exploded content you have to create a .dodeploy marker.
So I created an empty activemq.rar.dodeploy file and placed it in standalone/deployments folder.But still Jboss7 fails to deploy the rar.If I set auto-deploy-exploded="true" in standalone.xml then Jboss deploys the rar
I would like to manually deploy the rar so am wondering what I have missed since just creating the marker file seems to work for others.
I still see -
17:07:59,363 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found activemq.rar in deployment directory. To trigger deployment create a file called activemq.rar.dodeploy
even though I have already placed the marker file in standalone/deployments.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/762747#762747]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 6 months
[JBoss Transactions Development] - Narayana Release Process
by Paul Robinson
Paul Robinson [https://community.jboss.org/people/paul.robinson] modified the document:
"Narayana Release Process"
To view the document, visit: https://community.jboss.org/docs/DOC-17433
--------------------------------------------------------------
This page provides a list of instructions that must be done *in order* when doing a release of Narayana.
h2. Check JIRA
Ensure all issues are resolved. Any outstanding issues must be pushed back or resolved.
h2. Check Hudson
Ensure no test failures in the following group of hudson tests (for the branch you intend to release):
* 4.16 Branch : jbossts-branch416-*
* 4.17 Branch : jbossts-branch417-*
* 5 Branch: jbossts-narayana-*
h2. Do Release
h3. Release Quickstarts and Docs (4.17 and 5 only)
Must be done first as the build-release-packages.xml relies on the tag being available
# Similar steps apply to both Quickstarts and Docs
current='4\([._]\)17\([._]\)0\([._]\)Final-SNAPSHOT'
next='4\117\20\3Final'
find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git commit -am "Updated to $next"
git tag 4.17.0.Final
current='4\([._]\)17\([._]\)0\([._]\)Final'
next='5\10\20\3M2-SNAPSHOT'
find . -name \*.java -o -name \*.xml -o name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git push upstream master --tags
h3. svn branches
#Make sure your checkout has no local changes
svn update
svn status
POINT_VERSION=5
NEXT_POINT_VERSION=6
#Update the version in text files
find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v target | xargs grep -l "4[._]16" | xargs sed -i "s/4\([._]\)16\([._]\)${POINT_VERSION}\([._]\)Final-SNAPSHOT/4\116\2$POINT_VERSION\3Final/"
svn commit -m "Updated to version 4.16.$POINT_VERSION.Final"
#Tag the release:
svn cp https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_16 https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_${POINT_V... -m "4.16.$POINT_VERSION"
#Bump to next version using similar find to above
find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v target | xargs grep -l "4[._]16" | xargs sed -i "s/4\([._]\)16\([._]\)${POINT_VERSION}\([._]\)Final/4\116\2${NEXT_POINT_VERSION}\3Final-SNAPSHOT/"
svn commit -m "Updated to version 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT"
#Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as
git checkout 4_16_BRANCH
git pull --rebase --ff-only
#Check no local changes
git status
sed -i "s/4.16.${POINT_VERSION}.Final-SNAPSHOT/4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT/g" pom.xml
git commit -am "Updated to 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT"
git push
#Build and deploy the release to nexus staging:
mkdir ~/filemgmt.jboss.org/
sshfs jbosstm(a)filemgmt.jboss.org: ~/filemgmt.jboss.org/
ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
h5.
h3. git branches
#Make sure your checkout has no local changes
git checkout master
git status
#Pull remote changes
git fetch
git reset --hard upstream/master
#Update the version in text files and tag and push the release
CHANGE:
current='4\([._]\)17\([._]\)0\([._]\)Final-SNAPSHOT'
next='4\117\20\3Final'
find . -name \*.java -o -name \*.xml -o name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git commit -am "Updated to $next"
git tag 4.17.0.Final
git push upstream master
git push upstream --tags
#Bump to next version using similar find to above
CHANGE:
current='4\([._]\)17\([._]\)0\([._]\)Final'
next='5\10\20\3M2-SNAPSHOT'
find . -name \*.java -o -name \*.xml -o name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git push upstream master
#Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as
git clone -o jbosstm https://github.com/jbosstm/jboss-as
git checkout 5_BRANCH
sed -i "s/5.0.0.M1-SNAPSHOT/5.0.0.M2-SNAPSHOT/g" pom.xml
git commit -am "Updated to 5.0.0.M2-SNAPSHOT"
git push jbosstm 5_BRANCH
#Build and deploy the release to nexus staging:
mkdir ~/narayana/filemgmt.jboss.org/
sshfs jbosstm(a)filemgmt.jboss.org: ~/narayana/filemgmt.jboss.org/
ant -f build-release-pkgs.xml dist downloads docs magnolia
h2. Release the artifact through Nexus
1. https://repository.jboss.org/nexus/index.html#welcome https://repository.jboss.org/nexus/index.html#welcome
2. login
3. "Staging Repositories"
4. Click tickbox for your repo
5. Click "Close"
6. Don't worry about a description, just click "Close"
7. Click tickbox after it is closed
8. Click "Release"
9. Again a description doesn't matter
h2. JIRA Release
1. Check all issues resolved.
2. Create next point release version if not exists - this is so you can push issues in step 3 below.
3. Unresolved issues should be resolved or pushed.
4. Close all issues for the release
5. Mark as released (Need admin permissions)
h2. Update Website
Update the Narayana community site:
* Login to Magnolia* https://www.jboss.org/author/.magnolia/pages/adminCentral.html https://www.jboss.org/author/.magnolia/pages/adminCentral.html
* Login with credentials: Tom and Paul know these, ask them.
* Documentation* Browse to 'jbosstm/documentation'
* right click on 'downloads' and select 'import'
* browse to the location of the 'website.jbosstm.documentation.4.16.5.Final.xml' file
* Right click on the new file and click 'move'
* Drag the file to the top of the documentation list.
* Right click on the new page and select 'open page...'
* Check that the page looks right and that the download links work
* Right click on the new page and select 'activate'
* You now need to wait for the page to be moderated before it will appear.
* Downloads* Browse to 'jbosstm/downloads'
* right click on 'downloads' and select 'import'
* browse to the location of the 'website.jbosstm.downloads.4.16.5.Final.xml' file
* Right click on the new file and click 'move'
* Drag the file to the top of the downloads list.
* Right click on the new page and select 'open page...'
* Check that the page looks right and that the download links work
* Right click on the new page and select 'activate'
* You now need to wait for the page to be moderated before it will appear.
* Announcement* Right click on 'jbosstm' and select 'open page...'
* Click edit on the 'announcement' pane
* Update the announcement for this release.
* Right click on 'jbosstm' and select 'activate changes'
* You now need to wait for the page to be moderated before it will appear.
* Release notes* Right click on 'jbosstm' and select 'open page...'
* Click edit on the 'getting started' pane on the right-hand-side
* Edit the release notes url to point to the release notes for this version
* Click save
* Right click on 'jbosstm' and select 'activate changes'
* You now need to wait for the page to be moderated before it will appear.
h2. Push Upstream
If appropriate for this release, create a new 'component update' issue in AS7 JIRA. Ensure the module is set to 'transactions' and select an appropriate 'fix for'.
Assign it to yourself
Resolve the work and raise the pull request
1. https://issues.jboss.org/browse/AS7 https://issues.jboss.org/browse/AS7
2. cd AS source
3. git checkout -b AS7-<JIRANUMBER>
4. sed -i "s/4.16.3.Final/4.16.4.Final/g" pom.xml
5. git commit -am "AS7-<JIRA> Updated to 4.16.4.Final"
6. git push
7. Raise a pull request
h2. Promote
NOTE: It is worth waiting for the merge of the pull request before advertising, or at least wait for the merge build notification first ;)
Promote the release through the following channels:
1. Email jbossts-announce(a)lists.jboss.org (mailto:jbossts-announce@lists.jboss.org)
2. Forum
3. Blog - as appropriate
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-17433]
Create a new document in JBoss Transactions Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
11 years, 6 months