Re: [jboss-user] [jBPM] - jBPM5 Developer Guide – Request for Feedback
by Mauricio Salatino
Mauricio Salatino [http://community.jboss.org/people/salaboy21] commented on the document
"jBPM5 Developer Guide – Request for Feedback"
To view all comments on this document, visit: http://community.jboss.org/docs/DOC-17427#comment-8621
--------------------------------------------------
Yes totally, Guvnor/Designer and console are already into it. We definitely need to look at BAM.
in more detail. I mean.. the current implementation can be explained, but probably an integration with jasper reports will be great and a real life example will also help. BAM is the only topic that worries me a little bit because we need real data and a real example to show it. I can defenitely extend the emergency service live report to show some dashboard-like graphs using all the information that is available.
The form builder is something that needs to go.. I don't know if it will be ready, but we can mention it as a work in progress. The service repository is also in.
Cheers
--------------------------------------------------
12 years, 6 months
[JBoss Tools] - BIRT Integration-Cannot find the ODA dataSource extension (org.jboss.tools.birt.oda)
by Mike Baxley
Mike Baxley [http://community.jboss.org/people/mbaxley] created the discussion
"BIRT Integration-Cannot find the ODA dataSource extension (org.jboss.tools.birt.oda)"
To view the discussion, visit: http://community.jboss.org/message/610705#610705
--------------------------------------------------------------
I created a Seam 2.2 + JBoss BIRT Integeration project (BIRT2.6). I want to use the Hibernate ODA datasource for my reporting.
In my test project I used the Birt Sample Classic Models database. I generated the entity bean for the employees table and then built a report design using the Hibernate ODS datasource and dataset. I was able to preview the data and report within the eclipse IDE.
When I run the application in JBoss 5.1, I can successfully run the test and test1 sample reports added with birt integration. I can also view the data witht the seam generated web pages. So it seems my birt installation works fine along with my hibernate entity manager.
When I try to run my report that uses the Hibernate ODA datasource i get the following message:
The following items have errors:
Table (id = 9):
+ An exception occurred during processing. Please see the following message for details:
Cannot find or process the org.jboss.tools.birt.oda driver's data source extension configuration.
Cannot find the ODA dataSource extension (org.jboss.tools.birt.oda).
Check the workspace log file for any problems with loading the extension bundle and its dependencies.
The ReportEngine log shows this:
Jun 16, 2011 11:20:43 AM org.eclipse.birt.data.engine.odaconsumer.Driver doGetDriverManifest
SEVERE: Cannot find or process the ODA data source extension configuration.
java.lang.IllegalArgumentException: Cannot find the ODA dataSource extension (org.jboss.tools.birt.oda).
Check the workspace log file for any problems with loading the extension bundle and its dependencies.
at org.eclipse.datatools.connectivity.oda.util.manifest.ManifestExplorer.getExtensionManifest(ManifestExplorer.java:200)
at org.eclipse.birt.data.engine.odaconsumer.Driver.doGetDriverManifest(Driver.java:150)
at org.eclipse.birt.data.engine.odaconsumer.Driver.findDataSourceExtensionConfig(Driver.java:126)
at org.eclipse.birt.data.engine.odaconsumer.Driver.getDriverExtensionConfig(Driver.java:78)
at org.eclipse.birt.data.engine.odaconsumer.Driver.getExtensionConfig(Driver.java:60)
at org.eclipse.birt.data.engine.odaconsumer.Driver.createNewDriverHelper(Driver.java:97)
at org.eclipse.birt.data.engine.odaconsumer.DriverManager.getDriverHelper(DriverManager.java:111)
at org.eclipse.birt.data.engine.odaconsumer.DriverManager.getNewDriverHelper(DriverManager.java:100)
at org.eclipse.birt.data.engine.odaconsumer.ConnectionManager.openConnection(ConnectionManager.java:150)
at org.eclipse.birt.data.engine.executor.DataSource.newConnection(DataSource.java:224)
at org.eclipse.birt.data.engine.executor.DataSource.open(DataSource.java:212)
I grabbed the source code for ManifestExplorer and added some logging. It looks like the hibernate oda plugin is not being found. These are the plugins that are returned from the ExtensionRegistry:
org.eclipse.birt.report.data.oda.jdbc.dbprofile
org.eclipse.birt.report.data.oda.jdbc
org.eclipse.birt.report.data.oda.sampledb
org.eclipse.birt.report.data.oda.xml
org.eclipse.datatools.connectivity.oda.flatfile
org.eclipse.datatools.enablement.oda.ws
org.eclipse.datatools.enablement.oda.xml
org.jboss.tools.birt.oda is not listed. I do have the org.jboss.tools.birt.oda_1.2.0.v20110215-1225-H29-GA plugin in my plugins folder. I have tried using it both in a jar and exploded.
Any thoughts on how to make BIRT recognize the plugin? I also tried these same steps with my actual database with the identical results.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/610705#610705]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 6 months
[JBoss Web Services] - JBossWS - Supported Target Containers
by Alessio Soldano
Alessio Soldano [http://community.jboss.org/people/asoldano] modified the document:
"JBossWS - Supported Target Containers"
To view the document, visit: http://community.jboss.org/docs/DOC-13569
--------------------------------------------------------------
The following tables show the JBoss Application Server (community) versions JBossWS has been tested with before the release.
h2. Latest JBossWS versions
|| AS Version -> || 5.0.0 || 5.0.1 || 5.1.0 || 6.0.0.M1 || 6.0.0.M3 || 6.0.0.CR1 || 6.0.0.Final || 7.0.0 || 7.0.1 || 7.0.2 ||
| jbossws-native-3.1.2 | X | X | X |
|
|
|
|
|
|
|
| jbossws-native-3.2.0 | X | X | X |
|
|
|
|
|
|
|
| jbossws-native-3.2.1 | X | X | X |
|
|
|
|
|
|
|
| jbossws-native-3.2.2 | X | X | X | X |
|
|
|
|
|
|
| jbossws-native-3.3.0 |
| X | X |
| X |
|
|
|
|
|
| jbossws-native-3.3.1 |
| X | X |
| X |
|
|
|
|
|
| jbossws-native-3.4.0 |
| X | X |
|
| X |
|
|
|
|
| jbossws-native-3.4.1 |
|
|
|
|
|
| X |
|
|
|
| jbossws-native-4.0.0 |
|
|
|
|
|
|
| X | X | X |
|| AS Version -> || 5.0.0 || 5.0.1 || 5.1.0 || 6.0.0.M1 || 6.0.0.M3 || 6.0.0.CR1 || 6.0.0.Final || 7.0.0 || 7.0.1 || 7.0.2 ||
| jbossws-cxf-3.1.2 | X | X | X |
|
|
|
|
|
|
|
| jbossws-cxf-3.2.0 | X | X | X |
|
|
|
|
|
|
|
| jbossws-cxf-3.2.1 | X | X | X |
|
|
|
|
|
|
|
| jbossws-cxf-3.2.2 | X | X | X | X |
|
|
|
|
|
|
| jbossws-cxf-3.3.0 |
| X | X |
| X |
|
|
|
|
|
| jbossws-cxf-3.3.1 |
| X | X |
| X |
|
|
|
|
|
| jbossws-cxf-3.4.0 |
| X | X |
|
| X |
|
|
|
|
| jbossws-cxf-3.4.1 |
|
|
|
|
|
| X |
|
|
|
| jbossws-cxf-4.0.0 |
|
|
|
|
|
|
| X | X | X |
h2. Legacy / old JBossWS versions
|| AS Version -> || 4.0.5 || 4.2.1 || 4.2.2 || 4.2.3 || 5.0.0
Beta4 || 5.0.0
CR1 || 5.0.0
CR2 || 5.0.0 || 5.0.1 ||
| jbossws-native-2.0.1 | X | X |
|
|
|
|
|
|
|
| jbossws-native-2.0.2 | X | X | X |
|
|
|
|
|
|
| jbossws-native-2.0.3 | X | X | X |
|
|
|
|
|
|
| jbossws-native-3.0.0 |
| X | X |
| X |
|
|
|
|
| jbossws-native-3.0.1 |
| X | X |
| X |
|
|
|
|
| jbossws-native-3.0.2 |
| X | X |
| X | X |
|
|
|
| jbossws-native-3.0.3 |
|
| X | X |
| X | X |
|
|
| jbossws-native-3.0.4 |
|
| X | X |
|
| X |
|
|
| jbossws-native-3.0.5 |
|
| X | X |
|
|
| X |
|
| jbossws-native-3.1.0 |
|
|
| X |
|
|
| X | X |
| jbossws-native-3.1.1 |
|
|
| X |
|
|
| X | X |
|| AS Version -> || 4.0.5 || 4.2.1 || 4.2.2 || 4.2.3 || 5.0.0
Beta4 || 5.0.0
CR1 || 5.0.0
CR2 || 5.0.0 || 5.0.1 || 5.1.0 || 6.0.0.M1 || 6.0.0.M3 ||
| jbossws-metro-3.0.0 |
|
| X |
| X |
|
|
|
|
|
|
|
| jbossws-metro-3.0.1 |
|
| X |
| X |
|
|
|
|
|
|
|
| jbossws-metro-3.0.2 |
|
| X |
| X | X |
|
|
|
|
|
|
| jbossws-metro-3.0.3 |
|
| X | X |
| X | X |
|
|
|
|
|
| jbossws-metro-3.0.4 |
|
| X | X |
|
| X |
|
|
|
|
|
| jbossws-metro-3.0.5 |
|
| X | X |
|
|
| X |
|
|
|
|
| jbossws-metro-3.1.0 |
|
|
| X |
|
|
| X | X |
|
|
|
| jbossws-metro-3.1.1 |
|
|
| X |
|
|
| X | X |
|
|
|
| jbossws-metro-3.2.0 |
|
|
|
|
|
|
| X | X | X |
|
|
| jbossws-metro-3.2.1 |
|
|
|
|
|
|
| X | X | X |
|
|
| jbossws-metro-3.2.2 |
|
|
|
|
|
|
| X | X | X | X |
|
| jbossws-metro-3.3.0 |
|
|
|
|
|
|
|
| X | X |
| X |
| jbossws-metro-3.3.1 |
|
|
|
|
|
|
|
| X | X |
| X |
|| AS Version -> || 4.0.5 || 4.2.1 || 4.2.2 || 4.2.3 || 5.0.0
Beta4 || 5.0.0
CR1 || 5.0.0
CR2 || 5.0.0 || 5.0.1 ||
| jbossws-cxf-3.0.0 |
|
| X |
| X |
|
|
|
|
| jbossws-cxf-3.0.1 |
|
| X |
| X |
|
|
|
|
| jbossws-cxf-3.0.2 |
|
| X |
| X | X |
|
|
|
| jbossws-cxf-3.0.3 |
|
| X | X |
| X | X |
|
|
| jbossws-cxf-3.0.4 |
|
| X | X |
|
| X |
|
|
| jbossws-cxf-3.0.5 |
|
| X | X |
|
|
| X |
|
| jbossws-cxf-3.1.0 |
|
|
| X |
|
|
| X | X |
| jbossws-cxf-3.1.1 |
|
|
| X |
|
|
| X | X |
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-13569]
Create a new document in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
12 years, 6 months
[JBoss Web Services] - JBossWS - Supported Target Containers
by Alessio Soldano
Alessio Soldano [http://community.jboss.org/people/asoldano] modified the document:
"JBossWS - Supported Target Containers"
To view the document, visit: http://community.jboss.org/docs/DOC-13569
--------------------------------------------------------------
Generally, a new version of JBossWS http://labs.jboss.com/portal/jbossws/downloads comes out approximately every eight weeks and http://community.jboss.org/docs/DOC-13549 integrates with the last three JBoss Application Server releases. For details, please see the http://jira.jboss.org/jira/browse/JBWS?report=com.atlassian.jira.plugin.s... roadmap and the http://jira.jboss.org/jira/browse/JBWS?report=com.atlassian.jira.plugin.s... changelog. The following tables show the JBoss Application Server (community) versions JBossWS has been tested with before the release.
|| AS Version -> || 4.0.5 || 4.2.1 || 4.2.2 || 4.2.3 || 5.0.0
Beta4 || 5.0.0
CR1 || 5.0.0
CR2 || 5.0.0 || 5.0.1 || 5.1.0 || 6.0.0.M1 || 6.0.0.M3 || 6.0.0.CR1 || 6.0.0.Final || 7.0.0 || 7.0.1 || 7.0.2 ||
| jbossws-native-2.0.1 | X | X |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| jbossws-native-2.0.2 | X | X | X |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| jbossws-native-2.0.3 | X | X | X |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| jbossws-native-3.0.0 |
| X | X |
| X |
|
|
|
|
|
|
|
|
|
|
|
|
| jbossws-native-3.0.1 |
| X | X |
| X |
|
|
|
|
|
|
|
|
|
|
|
|
| jbossws-native-3.0.2 |
| X | X |
| X | X |
|
|
|
|
|
|
|
|
|
|
|
| jbossws-native-3.0.3 |
|
| X | X |
| X | X |
|
|
|
|
|
|
|
|
|
|
| jbossws-native-3.0.4 |
|
| X | X |
|
| X |
|
|
|
|
|
|
|
|
|
|
| jbossws-native-3.0.5 |
|
| X | X |
|
|
| X |
|
|
|
|
|
|
|
|
|
| jbossws-native-3.1.0 |
|
|
| X |
|
|
| X | X |
|
|
|
|
|
|
|
|
| jbossws-native-3.1.1 |
|
|
| X |
|
|
| X | X |
|
|
|
|
|
|
|
|
| jbossws-native-3.1.2 |
|
|
|
|
|
|
| X | X | X |
|
|
|
|
|
|
|
| jbossws-native-3.2.0 |
|
|
|
|
|
|
| X | X | X |
|
|
|
|
|
|
|
| jbossws-native-3.2.1 |
|
|
|
|
|
|
| X | X | X |
|
|
|
|
|
|
|
| jbossws-native-3.2.2 |
|
|
|
|
|
|
| X | X | X | X |
|
|
|
|
|
|
| jbossws-native-3.3.0 |
|
|
|
|
|
|
|
| X | X |
| X |
|
|
|
|
|
| jbossws-native-3.3.1 |
|
|
|
|
|
|
|
| X | X |
| X |
|
|
|
|
|
| jbossws-native-3.4.0 |
|
|
|
|
|
|
|
| X | X |
|
| X |
|
|
|
|
| jbossws-native-3.4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
| X |
|
|
|
| jbossws-native-4.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
| X | X | X |
|| AS Version -> || 4.0.5 || 4.2.1 || 4.2.2 || 4.2.3 || 5.0.0
Beta4 || 5.0.0
CR1 || 5.0.0
CR2 || 5.0.0 || 5.0.1 || 5.1.0 || 6.0.0.M1 || 6.0.0.M3 ||
| jbossws-metro-3.0.0 |
|
| X |
| X |
|
|
|
|
|
|
|
| jbossws-metro-3.0.1 |
|
| X |
| X |
|
|
|
|
|
|
|
| jbossws-metro-3.0.2 |
|
| X |
| X | X |
|
|
|
|
|
|
| jbossws-metro-3.0.3 |
|
| X | X |
| X | X |
|
|
|
|
|
| jbossws-metro-3.0.4 |
|
| X | X |
|
| X |
|
|
|
|
|
| jbossws-metro-3.0.5 |
|
| X | X |
|
|
| X |
|
|
|
|
| jbossws-metro-3.1.0 |
|
|
| X |
|
|
| X | X |
|
|
|
| jbossws-metro-3.1.1 |
|
|
| X |
|
|
| X | X |
|
|
|
| jbossws-metro-3.2.0 |
|
|
|
|
|
|
| X | X | X |
|
|
| jbossws-metro-3.2.1 |
|
|
|
|
|
|
| X | X | X |
|
|
| jbossws-metro-3.2.2 |
|
|
|
|
|
|
| X | X | X | X |
|
| jbossws-metro-3.3.0 |
|
|
|
|
|
|
|
| X | X |
| X |
| jbossws-metro-3.3.1 |
|
|
|
|
|
|
|
| X | X |
| X |
|| AS Version -> || 4.0.5 || 4.2.1 || 4.2.2 || 4.2.3 || 5.0.0
Beta4 || 5.0.0
CR1 || 5.0.0
CR2 || 5.0.0 || 5.0.1 || 5.1.0 || 6.0.0.M1 || 6.0.0.M3 || 6.0.0.CR1 || 6.0.0.Final || 7.0.0 || 7.0.1 || 7.0.2 ||
| jbossws-cxf-3.0.0 |
|
| X |
| X |
|
|
|
|
|
|
|
|
|
|
|
|
| jbossws-cxf-3.0.1 |
|
| X |
| X |
|
|
|
|
|
|
|
|
|
|
|
|
| jbossws-cxf-3.0.2 |
|
| X |
| X | X |
|
|
|
|
|
|
|
|
|
|
|
| jbossws-cxf-3.0.3 |
|
| X | X |
| X | X |
|
|
|
|
|
|
|
|
|
|
| jbossws-cxf-3.0.4 |
|
| X | X |
|
| X |
|
|
|
|
|
|
|
|
|
|
| jbossws-cxf-3.0.5 |
|
| X | X |
|
|
| X |
|
|
|
|
|
|
|
|
|
| jbossws-cxf-3.1.0 |
|
|
| X |
|
|
| X | X |
|
|
|
|
|
|
|
|
| jbossws-cxf-3.1.1 |
|
|
| X |
|
|
| X | X |
|
|
|
|
|
|
|
|
| jbossws-cxf-3.1.2 |
|
|
|
|
|
|
| X | X | X |
|
|
|
|
|
|
|
| jbossws-cxf-3.2.0 |
|
|
|
|
|
|
| X | X | X |
|
|
|
|
|
|
|
| jbossws-cxf-3.2.1 |
|
|
|
|
|
|
| X | X | X |
|
|
|
|
|
|
|
| jbossws-cxf-3.2.2 |
|
|
|
|
|
|
| X | X | X | X |
|
|
|
|
|
|
| jbossws-cxf-3.3.0 |
|
|
|
|
|
|
|
| X | X |
| X |
|
|
|
|
|
| jbossws-cxf-3.3.1 |
|
|
|
|
|
|
|
| X | X |
| X |
|
|
|
|
|
| jbossws-cxf-3.4.0 |
|
|
|
|
|
|
|
| X | X |
|
| X |
|
|
|
|
| jbossws-cxf-3.4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
| X |
|
|
|
| jbossws-cxf-4.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
| X | X | X |
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-13569]
Create a new document in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
12 years, 6 months
[jBPM] - jBPM 5.2: How to restart timer?
by Stefan Krause
Stefan Krause [http://community.jboss.org/people/krausest] created the discussion
"jBPM 5.2: How to restart timer?"
To view the discussion, visit: http://community.jboss.org/message/642548#642548
--------------------------------------------------------------
My Process looks like that: Script Task -> Intermediate Timer Event -> Script Task
To simulate an appserver restart while waiting for the timer I want to terminate the JVM process before the timer expires. In a new JVM process I want to restart the process and see the timer expire. How to do that?
My current attempt is the following:
I keep the session id from the session I created via JPAKnowledgeService.newStatefulKnowledgeSession(knowledgeBase, null, env) and restore the session with that id by calling JPAKnowledgeService.loadStatefulKnowledgeSession(sessionId, knowledgeBase, null, env). Nevertheless the timer is not fired. If I perform the test in one VM (starting the process, disposing the the KnowledgeSession and reloading with loadStatefulKnowledgeSession) the timer fires.
Who can help?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/642548#642548]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 6 months