[JBoss JIRA] Created: (JBESB-1881) DataFiler errors on trunk
by Tom Cunningham (JIRA)
DataFiler errors on trunk
-------------------------
Key: JBESB-1881
URL: https://jira.jboss.org/jira/browse/JBESB-1881
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Management
Affects Versions: 4.4
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Burr sees the following on trunk:
17:00:03,296 ERROR [DataFiler] ERROR - found type of java.lang.Integer for actio
n bytes failed
17:00:03,298 ERROR [DataFiler] ERROR - found type of java.lang.Integer for actio
n bytes processed
17:00:03,304 ERROR [DataFiler] ERROR - found type of java.lang.Integer for overa
ll bytes processed
17:00:03,307 ERROR [DataFiler] ERROR - found type of java.lang.Integer for overa
ll bytes failed
17:00:03,373 ERROR [DataFiler] ERROR - found type of java.lang.Integer for testS
tore bytes failed
17:00:03,375 ERROR [DataFiler] ERROR - found type of java.lang.Integer for setup
Key bytes failed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months
[JBoss JIRA] Created: (JBESB-1813) Add support for property injection in jboss-esb.xml
by Naveen Malik (JIRA)
Add support for property injection in jboss-esb.xml
---------------------------------------------------
Key: JBESB-1813
URL: http://jira.jboss.com/jira/browse/JBESB-1813
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Deployment
Affects Versions: 4.2.1
Reporter: Naveen Malik
This came about from a discussion on the port defined for a HTTP listener. As it is today, the value must be hard coded in the jboss-esb.xml file, which is part of the esb archive. This makes it hard to configure when moving between environments without changing that file and rebuilding the archive. We would like to move this type of configuration into external properties. I propose using system properties and the ModulePropertyManager provided by JBoss ESB, adding a new module named "action".
I will provide a patch for this feature today or tomorrow.
--
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
17 years, 2 months
[JBoss JIRA] Created: (JBESB-2321) ESB Getting Started Guide Needs Reviewing
by Stelios Koussouris (JIRA)
ESB Getting Started Guide Needs Reviewing
-----------------------------------------
Key: JBESB-2321
URL: https://jira.jboss.org/jira/browse/JBESB-2321
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.3
Reporter: Stelios Koussouris
Priority: Trivial
The following problems were identified in the Getting Started Guide and were checked/verified by SEG
Section 3.3 "SOA_GetStarted_Guide"
Issue1.
It says that before any messages are sent the "FirstService:SimpleJMSService" s registered with the Registry Service. Where does it get the "FirstService:SimpleJMSService" the service is defined with attributes category="FirstServiceESB" and name="SimpleListener" is this a typo? Also, when it says it is registered with the Registry Service where/how does that happen & get configured?
Answer 1. Typo, it should have been FirstServiceESB:SimpleListener --> category:name
Issue2.
In the example the JMS client is sending the message "queue/quickstart_helloworld_Request_gw" and not "queue/quickstart_helloworld_Request". Is this a typo or something I am missing? Similarly, where is the JMS Gateway Listener listening to as the above is confusing matters.
Answer 2. Typo: the build.xml in helloworld says "sends a JMS message to --> queue/quickstart_helloworld_Request_gw"
Issue3.
The "JMS Gateway Listener uses the registry to lookup the Endpoint Reference (EPR) or "FirstService:SimpleJMSService" Service" could
you please explain how this is done again? And then it finds that "his works out to be JMS Queue "queue/quickstart_helloworld_Request_gw""... more confusion how it has worked that out and why now it is this queue.
Answer 3. Typo again. the document-er has confused between gateways and non-gateways. A gateway is suffixed with _gw for convenience.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months
[JBoss JIRA] Created: (JBESB-2322) ESB Administrator Guide refers to jbossesb-listener.xml and jbossesb-gateway.xml
by Stelios Koussouris (JIRA)
ESB Administrator Guide refers to jbossesb-listener.xml and jbossesb-gateway.xml
--------------------------------------------------------------------------------
Key: JBESB-2322
URL: https://jira.jboss.org/jira/browse/JBESB-2322
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.3
Reporter: Stelios Koussouris
Priority: Trivial
Administration Guide" pg. 1
"How can I configure them?
You can configure JMSListeners and JMSGateways to listen to a Queue or
Topic by specifying the following parameters in their configuration
(jbossesb-listener.xml and jbossesb-gateway.xml):
• jndi-URL
• jndi-context-factory
• jndi-pkg-prefix
• connection-factory
• destination-type
• destination-name"
Do jbossesb-listener.xml and jbossesb-gateway.xml still exist or are they part of the jboss-esb.xml? ie. obsolete now?
I believe they might be internally used but not needed to be configured by the users
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months