You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2007/08/22 21:30:31 UTC
[jira] Commented: (AXIS2-3143) WSDL Port Address generation
algorithim has major limitations
[ https://issues.apache.org/jira/browse/AXIS2-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521902 ]
Davanum Srinivas commented on AXIS2-3143:
-----------------------------------------
that's what we do (in Axis2 1.3) - http://marc.info/?l=axis-cvs&m=118499936203494&w=2
> WSDL Port Address generation algorithim has major limitations
> -------------------------------------------------------------
>
> Key: AXIS2-3143
> URL: https://issues.apache.org/jira/browse/AXIS2-3143
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Reporter: Haneef Ali
>
> PortAddress generation from the wsdl has serious limitations
> 1) If you have multiple network address, then we can't predict the address
> 2) Using the hostname parameter in axis.xml is not a solution for the following reason
> 1) If you hardcode hostname, then you need to create different build for deploying in different machine
> 2) In production normally you have clusters of servers. Each server in the cluster will be running in the different machine. In this case hardcoding hostname is not a solution
> 3) Normally application servers will be in their own DMZ and are fronted by a webserver. In this case , you need the address of the webserver and not that of the application server.
> Proposed solution
> 1) Get the hostname from the request and use that to generate wsdl portAddress. As far as I know this is what weblogic does.
> Thanks,
> Haneef
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[AXIS2] exploded POJO not being deployed in 1.5 or 1.6
Posted by Nadir Amra <am...@us.ibm.com>.
It use to be a could drop down and exploded directory in the services
directory and it would get deployed. This was in Axis 1.3.
In Axis 1.5.x and 1.6 I keep getting
Error: java.lang.ClassCastException:
org.apache.axis2.classloader.JarFileClassLoader incompatible with
org.apache.axis2.deployment.DeploymentClassLoader at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:131)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:101)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:178)
at
org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:82)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:661)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:337)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:241)
at
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:331)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:64)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:71)
at
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:90)
at java.util.Timer$TimerImpl.run(Timer.java:291)
as if the directory is being treated as a jar file? What happened to this
ability? I have followed the mailing list and I do not recall changes to
this capability. Any hints?
Nadir Amra
Integrated Web Services for IBM i Operating System
IBM Rochester, MN, (Tel. 507-253-0645, t/l 553-0645)
Internet: amra@us.ibm.com
[AXIS2] WSDL Port Address generation between 1.3 and 1.5
Posted by Nadir Amra <am...@us.ibm.com>.
In Axis 1.3, the Axis2 engine generated the port from the incoming
request, as far as I know. For example, assume the following:
Axis2 running in server listening on port 10051
HTTP server front-ending the Axis2 server running and listening on port
10061
services.xml file has:
<parameter name="useOriginalwsdl">false</parameter>
<parameter name="modifyUserWSDLPortAddress">true</parameter>
When I run this on Axis 1.3 I get a wsdl that has endpoint port of 10061
if I go through the HTTP server to get the WSDL file. And if I go
straight to the Axis2 server I would get 10051.
Now running in Axis 1.5, the endpoint port is 10051 (i.e. the port of the
Axis2 server).
I know about the proxy port, my question is whether change in behavior
intentional? No other resolution to get behavior in Axis 1.3?
Nadir Amra
Integrated Web Services for IBM i Operating System
Internet: amra@us.ibm.com