[JBoss JIRA] Created: (JBESB-3293) FtpImpl getFileListFromRemoteDir() bad suffix handling, listing subdir contents
by Tom Eicher (JIRA)
FtpImpl getFileListFromRemoteDir() bad suffix handling, listing subdir contents
-------------------------------------------------------------------------------
Key: JBESB-3293
URL: https://jira.jboss.org/jira/browse/JBESB-3293
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Adapters
Affects Versions: 4.8, 4.7 CP1, 4.7, 4.6
Reporter: Tom Eicher
- RemoteFileSystem.getFileListFromRemoteDir(p_sSuffix) is meant to return the listing of the files of the current directory.
- however, due to the "suffix enforcing" in FtpImpl, even calls like "getFileListFromRemoteDir(null)" and "getFileListFromRemoteDir("")" will be executed as getFileListFromRemoteDir("*"), making this a FTP "NLST *" command.
- (and "getFileListFromRemoteDir(".")" will be "getFileListFromRemoteDir("*.")"...)
- now, when your target directory contains only one entry, and that entry is a file, the NLST will glob the "*" and return the listing of the subdir(!)
- so, you will get unexpected results like "tmp/file1", "tmp/file2", when all you wanted was to receive the "tmp".
- even when giving a suffix like "*.xml", this will return "tmp/file1.xml".
- tested against Microsoft ftp server, but the behaviour is as expected, so will be identical with many ftp servers
- fix: when no suffix given, call "listNames()", not "listNames("*")".
- see also: FTPClient.listNames(String) docu, which says "The server may or may not expand glob expressions". For ftp servers not doing globbing, this means all downloads will fail.
--
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
13 years, 10 months
[JBoss JIRA] Created: (JBESB-3289) BpmProcessor documentation anarchy
by Marcel Sebek (JIRA)
BpmProcessor documentation anarchy
----------------------------------
Key: JBESB-3289
URL: https://jira.jboss.org/jira/browse/JBESB-3289
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.8
Reporter: Marcel Sebek
The documentation of BpmProcessor is misleading. In the programmers guide, there is the following:
"
The following jBPM commands have been implemented:
- NewProcessInstanceCommand
- StartProcessCommand
- CancelProcessInstanceCommand
- GetProcessInstanceVariablesCommand
"
The correct version is StartProcessInstanceCommand. A few lines bellow,
there is NewProcessInstance-Command (the dash should probably not be
there). Also SignalProcessInstanceCommand is mentioned but that command
has been removed.
Instead of "processdefinition", there should be "process-definition-name".
In ServicesGuide, there is also a note about SignalProcessInstanceCommand and
the "processdefinition" is there too.
There may be more occurrences of these inconsistencies, I've mentioned just the
most obvious.
--
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
13 years, 11 months
[JBoss JIRA] Created: (JBESB-2556) Character corruption using SOAPClient (SOAPUI)
by Theodore S (JIRA)
Character corruption using SOAPClient (SOAPUI)
----------------------------------------------
Key: JBESB-2556
URL: https://jira.jboss.org/jira/browse/JBESB-2556
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.5
Environment: any
Reporter: Theodore S
When using SOAPUI using International characters can lead to character corruption.
How to reproduce:
Send chinese characters in the WS request to a webservice endpoint using the SOAPUI integration in JBossESB.
Fix:
In class org.jboss.soa.esb.actions.soap.SOAPClient change line 462:
post.setRequestEntity(new StringRequestEntity(request));
to
StringRequestEntity requestEntity = new StringRequestEntity(request,"text/xml","UTF-8");
post.setRequestEntity(requestEntity);
--
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
13 years, 11 months
[JBoss JIRA] Created: (JBESB-1553) SOAPClient action remappes objects with null strings to empty strings
by Jiri Pechanec (JIRA)
SOAPClient action remappes objects with null strings to empty strings
---------------------------------------------------------------------
Key: JBESB-1553
URL: http://jira.jboss.com/jira/browse/JBESB-1553
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Assigned To: Kevin Conner
Fix For: 4.2.1 CP2
Use webservice_consumer2 quickstart and use the attached files - contains enhanced equals and toString defintions. Make sure that option1 is used.
The object with following contents is sent to processing to ivoke web service
id = 101 lineItems = [Line Item ID= 1 Price=10.0 Ship To=aname, Line Item ID= 2 Price=20.0 Ship To=aname2] shipTo = null
But in the web service processing method the contents is
id = 101 lineItems = [Line Item ID= 1 Price=10.0 Ship To=aname, Line Item ID= 2 Price=20.0 Ship To=aname2] shipTo =
The difference is in shipTo property which was set tu null on the input but comes to web service as empty string.
--
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
13 years, 11 months