[JBoss JIRA] Created: (JBESB-3157) Feature request - consistent requirement for URL char encoding between ftp gateway and notifier
by Len DiMaggio (JIRA)
Feature request - consistent requirement for URL char encoding between ftp gateway and notifier
-----------------------------------------------------------------------------------------------
Key: JBESB-3157
URL: https://jira.jboss.org/jira/browse/JBESB-3157
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.7
Reporter: Len DiMaggio
Priority: Minor
We're inconsistent with how we handle special characters between ftp gateway listener definitions and ftp notifier definitions - it would make it simpler for users if we handled these in the same way.
For example, to use a directory of "ftp_dir##" and a password of "password##:
FTP gateway listener:
<ftp-provider hostname="servername.com" name="FTPprovider">
<ftp-bus busid="notifyFTPChannel">
<ftp-message-filter directory="/ftp_dir##"
error-delete="false" error-suffix=".HAS_ERROR"
input-suffix=".notifiertest" passive="true"
password="password##" post-delete="false"
post-suffix=".COMPLETE" username="username"
work-suffix=".esbWorking" />
</ftp-bus>
</ftp-provider>
FTP: notifier:
<action class="org.jboss.soa.esb.actions.Notifier" name="notify">
<property name="okMethod" value="notifyOK" />
<property name="notification-details">
<NotificationList type="OK">
<target class="NotifyFTP">
<ftp
URL="ftp://username:password%23%23@servername.com/ftp_dir%23%23"
filename="{jbossesb.message.id}.notifier"
passive="true" />
</target>
</NotificationList>
</property>
</action>
--
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
11 years, 11 months
[JBoss JIRA] Created: (JBESB-3353) EBWS should support Web service generation from a WSDL
by Jeff DeLong (JIRA)
EBWS should support Web service generation from a WSDL
------------------------------------------------------
Key: JBESB-3353
URL: https://jira.jboss.org/browse/JBESB-3353
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.8
Reporter: Jeff DeLong
EBWS should be extended to allow the user to specify a WSDL (in lieu of a set of XSDs). The WSDL would be required to conform to certain limitations, in particular only a single operation would be allowed to be specified, and the soap: address in the wsdl:port would be overwritten to match the deployment environment.
This would support top-down service development. For example when using JBoss Savara project to generate WSDL documents from a Choregraphy model.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] Created: (JBESB-2460) BinarySecurityToken class hardwired to X.509 certificates
by Rune Molin (JIRA)
BinarySecurityToken class hardwired to X.509 certificates
---------------------------------------------------------
Key: JBESB-2460
URL: https://jira.jboss.org/jira/browse/JBESB-2460
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: 4.5
Reporter: Rune Molin
In order to support WS Security Kerberos Token Profile at a later time, please make the class org.jboss.soa.esb.services.security.auth.ws.BinarySecurityToken abstract. Currently it is hardwired to only support X.509 Certificate Token Profile.
By making this class abstract sooner rather than later, users could implement Kerberos Token Profile themselves, without having to duplicate too much code. This will of course mean moving the existing certificate bound implementation into a new class, CertificateSecurityToken perhaps
--
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
12 years, 1 month