Hi,

Please refer to [1]. Same applies for Apache Stratos.
You don't need to build the whole product, only related jar need to be
patched.

[1]
http://stackoverflow.com/questions/11306929/how-to-apply-patch-files-in-wso2-carbon



Touched, not typed. Erroneous words are a feature, not a typo.
On Jun 20, 2014 4:46 AM, "Martin Eppel (meppel)" <mep...@cisco.com> wrote:

>
> I used to be able to patch my stratos server by simply replacing jar files
> (every instance, - up to rc3) , however, since moving to code based on RC4
> this procedure started to fail.
>
> For example, to patch a change in the autoscaler I
> - stopped stratos, replace the jars and restarted stratos again.
>
> e.g replaced the following 2 jars :
>
> /opt/wso2/apache-stratos/repository/components/patches/patch0000/org.apache.stratos.autoscaler_4.0.0.jar;
>
> /opt/wso2/apache-stratos/repository/components/plugins/org.apache.stratos.autoscaler_4.0.0.jar;
>
> However, now, every time I replace a jar, even so the source hasn’t
> changed compared to the original binary,  the system fails to come up and
> hangs there :
>
> ID: [0] [STRATOS] [2014-06-19 22:37:26,613]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
> TID: [0] [STRATOS] [2014-06-19 22:37:26,613]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGiAxis2Service: org.apache.stratos.manager-4.0.0
> {org.wso2.carbon.core.init.CarbonServerManager}
> TID: [0] [STRATOS] [2014-06-19 22:38:26,613]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
> TID: [0] [STRATOS] [2014-06-19 22:38:26,613]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGiAxis2Service: org.apache.stratos.manager-4.0.0
> {org.wso2.carbon.core.init.CarbonServerManager}
>
>
> As of now it seems my only choice is to rebuild the whole system  to test
> some changes ? Is there a recommended patch sequence to test code changes
> by just patching single jar files ? What about the REST API (stratos.war) ?
>
> Any ideas to get my patch process back to work, otherwise, the option to
> rebuild all binaries + upload takes a long time and is very inefficient for
> development ?
>
> Thanks
>
> Martin
>
>

Reply via email to