[JBoss JIRA] Created: (JBESB-951) Registry text update
by Mark Little (JIRA)
Registry text update
--------------------
Key: JBESB-951
URL: http://jira.jboss.com/jira/browse/JBESB-951
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Mark Little
Fix For: 4.2.1
"Service registries are central to most service oriented architectures (SOAs), and at runtime they act as a point of reference to correlate service requests to concrete actions. A service registry has metadata entries for all artifacts within the SOA that are used at both runtime and design time. Items inside a service registry may include service description artifacts (e.g., WSDL), Service Policy descriptions, XML Schemas used by various services, artifacts representing different versions of services, governance and security artifacts (certificates, audit trails), and many more items. During the design phase, business process designers may use the registry to link together calls to several services to create a workflow or business process."
--
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
18 years, 7 months
[JBoss JIRA] Created: (JBESB-814) esb.product.lib.ext property relies on current directory name
by Aleksandar Kostadinov (JIRA)
esb.product.lib.ext property relies on current directory name
-------------------------------------------------------------
Key: JBESB-814
URL: http://jira.jboss.com/jira/browse/JBESB-814
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Aleksandar Kostadinov
Assigned To: Mark Little
In the product directory I see:
./services/spring/build.properties:esb.product.lib.ext=../../../product/lib/ext
./services/jbrules/build.properties:esb.product.lib.ext=../../../product/lib/ext
./services/jbpm/build.properties:esb.product.lib.ext=../../../product/lib/ext
./services/jbossesb/build.properties:esb.product.lib.ext=../../../product/lib/ext
./services/smooks/build.properties:esb.product.lib.ext=../../../product/lib/ext
So if I try to build dist - ant dist I get an error that there is no directory `pwd`/../product/lib/ext if current directory is not called product.
IMHO the property value should be "../../lib/ext" instead of "../../../product/lib/ext" so that it doesn't rely on current directory name to be "product".
--
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
18 years, 7 months
[JBoss JIRA] Created: (JBESB-602) ESB Server should be able to deploy .ear files
by Tom Cunningham (JIRA)
ESB Server should be able to deploy .ear files
----------------------------------------------
Key: JBESB-602
URL: http://jira.jboss.com/jira/browse/JBESB-602
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Management
Affects Versions: 4.2
Reporter: Tom Cunningham
Assigned To: Mark Little
Tried to deploy my helloworld_hibernate_action .ear file, which contains some jars, a .war, and a .esb to the ESB Server, and I get the following error - I think .ear deployment is broken in the ESB server :
23:48:37,293 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@b5294d9 { url=file:/Users/tcunning/esb/esbserver/server/default/deploy/Quickstart_helloworld_hibernate_action.ear }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/Users/tcunning/esb/esbserver/server/default/deploy/Quickstart_helloworld_hibernate_action.ear
altDD: null
lastDeployed: 1181015313405
lastModified: 1181015313000
mbeans:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@b5294d9 { url=file:/Users/tcunning/esb/esbserver/server/default/deploy/Quickstart_helloworld_hibernate_action.ear }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/Users/tcunning/esb/esbserver/server/default/deploy/Quickstart_helloworld_hibernate_action.ear
altDD: null
lastDeployed: 1181015313405
lastModified: 1181015313000
mbeans:
--
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
18 years, 7 months
[JBoss JIRA] Created: (JBESB-891) jbpm.esb contains has incorrect jbpm-ds.xml
by Burr Sutter (JIRA)
jbpm.esb contains has incorrect jbpm-ds.xml
-------------------------------------------
Key: JBESB-891
URL: http://jira.jboss.com/jira/browse/JBESB-891
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: BPM
Affects Versions: 4.2 Milestone Release 3
Reporter: Burr Sutter
Assigned To: Mark Little
Fix For: 4.2
It should point to this DB:
<connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}jbpmDB</connection-url>
it currently says "jbpm", not "jbpmDB"
Finally, the user's "manager", "admin", "user" and "shipper" are missing from the default database.
You currently have to copy the jbpmdb.properties and jbpmdb.script from the jBPM 3.2.1 "Suite" download to make the admin console function.
--
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
18 years, 7 months
[JBoss JIRA] Created: (JBESB-877) Streaming transformation?
by Mark Little (JIRA)
Streaming transformation?
-------------------------
Key: JBESB-877
URL: http://jira.jboss.com/jira/browse/JBESB-877
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Transformation Service
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Tom Fennelly
Intern:
"Can Smooks deal with streaming of content? What I mean is that suppose I've got a lot of data that I'm streaming from a client to the transformation service. Can Smooks deal with that as it comes, or would I have to grab it all first before passing it on. I don't know if the ESB can deal with streaming anyway, so this may be a chicken-and-egg situation."
--
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
18 years, 7 months