Build...from source?
There's a build.bat/build.sh in the root of the JBossAS/build project, and those scripts will execute to create and populate another project called "thirdparty", which in turn obtains all JARs needed to build JBoss.
Sounds complicated, but it's automated. Can be as easy as checking out JBossAS from the desired TRUNK/Branch/Tag and running the batch/shell script.
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970267#3970267
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970267
I suppose you could persist it as a byte[], jBPM will persist them, but there will likely be issues with a blob that big (talking on pure assumption here).
The alternative is to store some reference to your document in the process, and reference it when you need to with a link or some such assuming you have some PK to the external system (or your system) where the document is actually stored.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970265#3970265
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970265
JBossWS 1.0.0.GA. It's going to get upgraded soon when AS 4.0.5.GA is released along with updated installer.
There is no patch for the JBoss.4.0.4.GA. Patch1 refers to the installer patch which we needed to created in order to correct a critical EJB3 issue.
So the latest JEMS Installer (1.2.0.BETA2) includes the following:
jboss.version=4.0.4.GA
ejb3.version=1.0.0.CR8
jbossws.version=1.0.0.GA
portal.version=2.4.0.GA
hope this helps
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970259#3970259
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970259