Failure is caused by a reference to
http://www.mobicents.org/slee/dtd/deploy-config_1_1.dtd
in
du/src/main/resources/META-INF/deploy-config.xml
resulting in HTTP GET to www.mobicents.org on deployment, which fails with
confusing errors ("java.net.ConnectException: Connection refused" - quite
strange if the RA is not supposed to connect anywhere, even more strange if the
RA would connect to a local resource that is actually available;
"java.util.zip.ZipException: error in opening zip file" - also confusingly
meaningless here as the archive is intact) in case internet access is not
available.
What steps will reproduce the problem?
1. Create a RA with all the necessary modules so that it deploys successfully
(on a machine with internet access).
2. Deploy the RA to a machine without internet access (or make
www.mobicents.org inaccessible using hosts file, updating kernel routing table,
bringing down network interface, unplugging the cable, etc.)
What is the expected output? What do you see instead?
Expected successful deployment, actual - failure to deploy the RA with errors
in the attached log excerpt.
What version of the product are you using? On what operating system?
EclipSLEE 2.0.0.v20121003-1449
m2e 1.2.0.20120903-1050 (embedded maven 3.0.4)
Eclipse 4.2.1
Debian GNU/Linux 6.0.6
Please provide any additional information below.
Trivial workaround - remove the DTD reference from deploy-config.xml. However,
I think this should be considered a serious issue as the target environments of
SLEE applications are typically isolated from the outside world, so the
developers would be getting the unpleasant surprise of their RAs working
everywhere except the target environment.
Original issue reported on code.google.com by vil...@users.sourceforge.net on 6 Feb 2013 at 11:44
Original issue reported on code.google.com by
vil...@users.sourceforge.neton 6 Feb 2013 at 11:44Attachments: