Open GoogleCodeExporter opened 8 years ago
Also make it easier to adapt tests. For example add an extra outbound endpoint
to a test.
Original comment by hakan.d...@gmail.com
on 25 Oct 2013 at 1:03
Also make it possible to add customer-specific generator templates.
Reflection: does this really make soi-tk simpler? Maybe from an end-user
point-of-view?
Original comment by hakan.d...@gmail.com
on 25 Oct 2013 at 1:04
Regarding adapting tests: maybe we should move away from using named endpoints
in the generated test-setup code like (example for JMS-to-FTP):
protected void doSetUp() throws Exception {
FtpUtil.initEndpointDirectory(muleContext, "jmsToFtp-outbound-endpoint");
}
since there are these problems with the above approach:
1. Changing the outbound endpoint to be dynamic by adding an expression for
path/folder makes the above code useless, it cannot handle dynamic endpoints.
When tried it throws exception:
java.lang.UnsupportedOperationException: No connector available
at org.mule.endpoint.DynamicOutboundEndpoint.getConnector(DynamicOutboundEndpoint.java:191)
at org.soitoolkit.commons.mule.ftp.FtpUtil.getFtpClient(FtpUtil.java:141)
at org.soitoolkit.commons.mule.ftp.FtpUtil.initEndpointDirectory(FtpUtil.java:59)
2. MuleStudio (versions 3.2 -3.4) likes to change the XML flow-config when
opened in the flow-editor, especially for transports where there is an
Enterprise-version (like FTP, JDBC) but is has also been observed for
SFTP-outbound. When MuleStudio changes the flow, it typically throws away the
name-attribute of an endpoint which breaks the integration test.
Can we instead of named endpoints just use parameters for connector and path?
Original comment by hakan.d...@gmail.com
on 4 Nov 2013 at 1:12
Teststub-components: can we get rid of them as a concept?
If there is a need it can be fulfilled by other means, for example using
soapui-mockservices for http, or simply by building a dedicated full-blown
integration-component.
That would simplify the choices in the generator and remove some complexity in
understanding how teststub-components are assembled and used.
Original comment by hakan.d...@gmail.com
on 9 Nov 2013 at 8:40
Simplify mule-dependencies-pom, ref issue 361.
Original comment by hakan.d...@gmail.com
on 16 Dec 2013 at 9:13
Original issue reported on code.google.com by
hakan.d...@gmail.com
on 25 Oct 2013 at 1:01