Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Message-ID: <30417997.21551291110192312.JavaMail.jira@thor>
Date: Tue, 30 Nov 2010 04:43:12 -0500 (EST)
From: =?utf-8?Q?Zsolt_M=C3=BCller_=28JIRA=29?= <jira@apache.org>
To: java-dev@axis.apache.org
Subject: [jira] Created: (AXIS2-4903) ScriptModule logs the error
 "AxisConfiguration getRepository returns null, cannot deploy scripts"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

ScriptModule logs the error "AxisConfiguration getRepository returns null, =
cannot deploy scripts"
---------------------------------------------------------------------------=
----------------------

                 Key: AXIS2-4903
                 URL: https://issues.apache.org/jira/browse/AXIS2-4903
             Project: Axis2
          Issue Type: Bug
          Components: deployment
    Affects Versions: 1.4.1, 1.5, 1.5.1, 1.5.2, 1.5.3, 1.6, 1.5.4, nightly
         Environment: Debian 5.0.7, Tomcat 5.5.26
            Reporter: Zsolt M=C3=BCller


Conditions for the error to occur:
- use of the scripting module (ie. add "axis2-scripting-*.mar" to your modu=
les/modules.list)
- use of the "axis2.xml.url" web.xml parameter or packaging of the webapp i=
nto a WAR/EAR

The problem is that during the initialization of the scripting module (ie. =
the call to org.apache.axis2.scripting.ScriptModule.init()) it checks for t=
he repository in the axisconfiguration to be not null.
The relevant code is:
  AxisConfiguration axisConfig =3D configContext.getAxisConfiguration();
  if (axisConfig.getRepository() =3D=3D null) {
    log.error("AxisConfiguration getRepository returns null, cannot deploy =
scripts");
  } else {
    ... // scripting module initialization
  }

If ConfigurationContext.getAxisConfiguration().getRepository() returns null=
, then the scripting module logs an error and the module is not initialized=
.

Now the problem causing this to happen is in org.apache.axis2.deployment.De=
ploymentEngine.loadRepositoryFromURL().
The exact callstack will look like this (without line numbers, because I do=
n't want to get version-specific):
  - DeploymentEngine.loadRepositoryFromURL(URL repoURL)
  - WarBasedAxisConfigurator.getAxisConfiguration()
  - ConfigurationContextFactory.createConfigurationContext(AxisConfigurator=
 axisConfigurator)
  - AxisServlet.initConfigContext(ServletConfig config)
  - AxisServlet.init(ServletConfig config)

If you take a look at WarBasedAxisConfigurator.getAxisConfiguration(), you'=
ll see that depeding on the configuration it executes one of the following =
to load the repository:
  - DeploymentEngine.loadRepository(String repoDir)
  - DeploymentEngine.loadRepositoryFromURL(URL repoURL)
  - DeploymentEngine.loadFromClassPath()

In case of loadRepository(String repoDir) there's a call to "axisConfig.set=
Repository(axisRepo.toURL())" which sets the repository reference in the ax=
is configuration.
In case of loadRepositoryFromURL(URL repoURL) there's no such call, which r=
esults in ScriptModule.init() in the error message I described earlier.

The fix is easy: in org.apache.axis2.deployment.DeploymentEngine.loadReposi=
toryFromURL(URL repoURL) put a axisConfig.setRepository(repoURL) call befor=
e the axisConfig.validateSystemPredefinedPhases() call.

As for DeploymentEngine.loadFromClassPath(), I don't know how to set the re=
pository URL.
Any idea? Or any other way to use the scripting module without an axis2.xml=
?
My guess is that ScriptModule should be modified to handle the case, when r=
epository is loaded from CLASSPATH. Ie. it should try to pick up the script=
ServicesDirectory from the CLASSPATH as well.
Currently it's hard-coded to look for the scriptServicesDirectory within a =
filesystem entry pointed to by a File object.

P.S.: this bug is present in v1.4.1, v1.5.3 and in SVN trunk (at the moment=
 of writing). I guess this has been around from the beginning.

--=20
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org