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 "Ruwan Linton (JIRA)" <ji...@apache.org> on 2011/01/04 07:16:45 UTC
[jira] Resolved: (AXIS2-3466) Unable to create a custom
configuration context when the module/service repository is included into
the aar file
[ https://issues.apache.org/jira/browse/AXIS2-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton resolved AXIS2-3466.
---------------------------------
Resolution: Won't Fix
This is not a bug, Axis2 doesn't support loading a repository inside an aar file. Why do you need to have a repository inside the aar file. If your intention is to invoke another service, refer to a repository in your local file system. Actually you do not need to have a repository to create a configuration context if you do not need to engage modules and so forth at global level. You could alsp get the running configuration context by calling MessageContext.getCurrentMessageContext().getConfigurationContext() method.
> Unable to create a custom configuration context when the module/service repository is included into the aar file
> ----------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-3466
> URL: https://issues.apache.org/jira/browse/AXIS2-3466
> Project: Axis2
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.3
> Environment: axis1.3
> Reporter: Michele Mazzucco
> Priority: Critical
>
> http://www.mail-archive.com/axis-user@ws.apache.org/msg37312.html
--
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