On Wed, Jan 12, 2011 at 10:15 AM, Afkham Azeez <[email protected]> wrote:

>
>
> On Tue, Jan 11, 2011 at 4:12 PM, Cappa Roberto <
> [email protected]> wrote:
>
>>  Hi,
>>
>> now our SOA platform is based on WSAS 3.1.3, GREG 3.0.1 and ESB 2.1.3. We
>> would like to migrate all products to the latest versions, but we are
>> blocked since months because of different problems. In current situation
>> these are the problems.
>>
>>
>>    1. Network connection problems when adding WSDL in GREG 3.6.0
>>    https://wso2.org/jira/browse/REGISTRY-570. The suggested solution
>>    (enable access from the GREG machine to internet) is not suitable in a 
>> real
>>    scenario with network security policies.
>>    2. Unavailability of an ESB release compatibile with H2 database
>>    of GREG 3.6.0 (where we have already migrated our data).
>>    3. Non-compatibility of AS 4.0.0 with our Axis2 webservices. Our .aar
>>    works perfectly on WSAS 3.x but we have problems on AS 4.0.0. We have
>>    noticed that AS 4.0.0 is based on Axis2 *1.6 *release. So, our
>>    webservices don't compile and don't work with this version, and we should
>>    change Axis2 dependencies in our projects, but on Axis2 site it seems that
>>    the 1.6 version doesn't exist yet. We don't want to use non stable 
>> realeses
>>    of Axis2 but there is no possibility to deploy an axis 1.5 based service 
>> on
>>    AS 4.
>>
>>
> You can use the Axis2 JARs which we ship wit Carbon servers or AS 4.0.
> These are stable & well tested releases, which were created & stabilized by
> us from the Apache Axis2 trunk. The fixes and improvements we've done have
> been merged back to the Apache trunk.
>
>>
>>    1. Webapps on AS 4.0.0 works differently from a stand-alone Tomcat (
>>    http://wso2.org/forum/thread/11233). Our webapps contain a
>>    third-part library that use the "getRealPath" on ServletContext that
>>    returns a different result in Tomcat and AS 4.0.0.
>>
>>
> See
> http://download.oracle.com/javaee/1.3/api/javax/servlet/ServletContext.html#getRealPath(java.lang.String)
>
> <quote>
> The real path returned will be in a form appropriate to the computer and
> operating system on which the servlet container is running, including the
> proper path separators. This method returns null if the servlet container
> cannot translate the virtual path to a real path for any reason (such as
> when the content is being made available from a .war archive).
> </quote>
>
> In AS, we deploy the WAR without exploding it. You need to write your
> webapp in a way that it works on multiple appservers. The* getRealPath API
> does not guarantee that you will always get a path in all deployment
> environments*, so it is always best not to rely on that.
>


Just to make life a bit more easier for some users, I have added a
configuration property, carbon.unpack.wars. You can set this to true, if you
want to enable WAR unpacking at container level. This change has been
committed to the trunk.

-- 
*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
*
*
*Member; Apache Software Foundation;
**http://www.apache.org/*<http://www.apache.org/>
*
email: **[email protected]* <[email protected]>* cell: +94 77 3320919
blog: **http://blog.afkham.org* <http://blog.afkham.org>*
twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
_______________________________________________
Carbon-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to