[JBoss JIRA] (JBESB-3778) XMLHelper fails to load XSD referenced in jboss-esb.xml and fails with a misleading error message.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBESB-3778?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on JBESB-3778:
------------------------------------------------
David Le Sage <dlesage(a)redhat.com> changed the Status of [bug 812330|https://bugzilla.redhat.com/show_bug.cgi?id=812330] from NEW to ASSIGNED
> XMLHelper fails to load XSD referenced in jboss-esb.xml and fails with a misleading error message.
> --------------------------------------------------------------------------------------------------
>
> Key: JBESB-3778
> URL: https://issues.jboss.org/browse/JBESB-3778
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.10, 4.11
> Reporter: Marek Baluch
> Attachments: server.log, ServicioValidacionDatos.esb
>
>
> In case we have the following ESB definition (please note that the xsd path is not prefixed by '/')
> {code}
> <actions faultXsd="ValidacionDatosFault.xsd" ...>
> {code}
> deployment will fail with
> Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
> ...
> The message is misleading because the XSD file will not be found. The problem lies in the fact that the ValidacionDatosFault.xsd is not prefixed by "/". The URI for that resource will look like "classpath://ValidacionDatosRequest.xsd" and the getPath() method will return an empty string which will be passed as argument to ClassUtil.getResource(String, Class).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBESB-3740) Clarify usage of acknowledge-mode on jms-message-filter
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBESB-3740?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on JBESB-3740:
------------------------------------------------
David Le Sage <dlesage(a)redhat.com> changed the Status of [bug 781988|https://bugzilla.redhat.com/show_bug.cgi?id=781988] from NEW to ASSIGNED
> Clarify usage of acknowledge-mode on jms-message-filter
> -------------------------------------------------------
>
> Key: JBESB-3740
> URL: https://issues.jboss.org/browse/JBESB-3740
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Documentation
> Affects Versions: 4.11
> Reporter: Tom Cunningham
> Fix For: 4.13
>
>
> Description of problem:
> The ESB Programmers Guide [1] only states that CLIENT_ACKNOWLEDGE mode can be
> set on the jms-message-filter configuration, but does not talk about the
> resulting
> behavior, or about any restrictions.
> The docs should be more clear about
> - the resulting behavior if different ack modes are used
> - any restrictions that apply, such as not using CLIENT_ACKNOWLEDGE mode on
> non-gateway queues using jms-provider
> - which providers these settings apply to (jms-provider, jms-jca-provider)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBESB-3909) Document : Configure the authentication method and security domain
by William Siqueira (JIRA)
[ https://issues.jboss.org/browse/JBESB-3909?page=com.atlassian.jira.plugin... ]
William Siqueira updated JBESB-3909:
------------------------------------
> Document : Configure the authentication method and security domain
> ------------------------------------------------------------------
>
> Key: JBESB-3909
> URL: https://issues.jboss.org/browse/JBESB-3909
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Documentation
> Affects Versions: 4.11
> Reporter: Suzumura Keishi
> Priority: Minor
>
> In Programmers Guide 10.20 section[1], it mentions Configure the authentication method and security domain. But following mentions are not correct.
> incorrect
> -----------
> <http-provider name="http">
> <http-bus busid="secureFriends">
> <allowed-roles>
> <role name="friend" />
> </allowed-roles>
> <protected-methods>
> <method name="DELETE" />
> </protected-methods>
> </http-bus>
> <auth method="BASIC" domain="java:/jaas/JBossWS" />
> </http-provider>
> -----------
> correct
> -----------
> <globals>
> <!-- Security setting for all http-providers and all EBWSs in this jboss-esb.xml file.-->
> <war-security method="BASIC" domain="JBossWS" /> <!-- uname: "kermit" pw: "thefrog" -->
> </globals>
> -----------
> [1] JBoss Enterprise SOA Platform 5 ESB Programmers Guide
> 10.20. Further HTTP Gateway Security
> https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_SOA_Platf...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBESB-3965) build FuseIDE from source complains for Tycho 0.16.0.CR2
by Ronny Aerts (JIRA)
Ronny Aerts created JBESB-3965:
----------------------------------
Summary: build FuseIDE from source complains for Tycho 0.16.0.CR2
Key: JBESB-3965
URL: https://issues.jboss.org/browse/JBESB-3965
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Ronny Aerts
The main pom.xml has a variable tycho-version with contain "0.18.1" and another jboss-tycho-version with content "0.16.0.CR2". The maven "mvn clean install -Dmaven.test.skip=true" produces a "The POM for org.jboss.tools.tycho-plugins:repository-utils:jar:0.16.0.CR2 is missing" error on this.
The version Tycho version 0.16.0 does not seem to be online available anymore.
Can someone please update the main pom so I can execute a build FuseIDE from source?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 12 months
[JBoss JIRA] (JBESB-3964) FuseIDE in combination with routeContext elements from external files
by Ronny Aerts (JIRA)
Ronny Aerts created JBESB-3964:
----------------------------------
Summary: FuseIDE in combination with routeContext elements from external files
Key: JBESB-3964
URL: https://issues.jboss.org/browse/JBESB-3964
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Ronny Aerts
Hello,
I started about a half year ago using Camel in combination ActiveMQ and I feel good with this esb solution. I created all xml files and related files using an xml or text editor. I would like to switch to a more visual editor and I came across the FuseIDE. Everthing seems to work fine except for my sub-routes. I use the routeContext functionality as sub-routes in the main route file. A sub-routes are predefined reusable routes which, dependable on the customer, are included or not (in the main file). I already have a collection of sub-routes which is extending every week.
I found the same issue in eclipse-344 (http://fusesource.com/forums/thread.jspa?messageID=17641) but it should have solved quite some time ago. I am very confused about the version information for the FuseIDE product. Eclipse-344 indicates that this issue is solved in version 2.1.0 but I can't find this version number anywhere. I download the FuseIDE as part of the jboss fuse page and this gives me a download file FuseIDE-6.0.0.129-win32.win32.x86_64.zip. A see here a version 6.0.0.129 and zip contains a folder FuseIDE-6.0.0.
The "About FuseIDE" window (in eclipse) shows a version 7.6.2 (but I think this is the eclipse.exe version).
Can someone please clear out this version confusion? Can someone tell me why my sub-route design windows is blank when I open it?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 12 months
[JBoss JIRA] (JBESB-3963) FuseIDE in combination with routeContext elements from external files
by Ronny Aerts (JIRA)
Ronny Aerts created JBESB-3963:
----------------------------------
Summary: FuseIDE in combination with routeContext elements from external files
Key: JBESB-3963
URL: https://issues.jboss.org/browse/JBESB-3963
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: non-project
Reporter: Ronny Aerts
Priority: Blocker
Hello,
I started about a half year ago using Camel in combination ActiveMQ and I feel good with this esb solution. I created all xml files and related files using an xml or text editor. I would like to switch to a more visual editor and I came across the FuseIDE. Everthing seems to work fine except for my sub-routes. I use the routeContext functionality as sub-routes in the main route file. A sub-routes are predefined reusable routes which, dependable on the customer, are included or not (in the main file). I already have a collection of sub-routes which is extending every week.
I found the same issue in eclipse-344 (http://fusesource.com/forums/thread.jspa?messageID=17641) but it should have solved quite some time ago. I am very confused about the version information for the FuseIDE product. Eclipse-344 indicates that this issue is solved in version 2.1.0 but I can't find this version number anywhere. I download the FuseIDE as part of the jboss fuse page and this gives me a download file FuseIDE-6.0.0.129-win32.win32.x86_64.zip. A see here a version 6.0.0.129 and zip contains a folder FuseIDE-6.0.0.
The "About FuseIDE" window (in eclipse) shows a version 7.6.2 (but I think this is the eclipse.exe version).
Can someone please clear out this version confusion? Can someone tell me why my sub-route design windows is blank when I open it?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 12 months