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 "Thomas Nymand (JIRA)" <ji...@apache.org> on 2007/10/05 10:48:50 UTC
[jira] Created: (AXIS2-3246) Deployment of embedded service causes
IllegalArgumentException: Filename must not be null
Deployment of embedded service causes IllegalArgumentException: Filename must not be null
-----------------------------------------------------------------------------------------
Key: AXIS2-3246
URL: https://issues.apache.org/jira/browse/AXIS2-3246
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.3
Environment: BEA Weblogic 10, Axis2 1.3.
Reporter: Thomas Nymand
Priority: Blocker
When deploying an embedded type service (war containing services.xml in WEB-INF), the deployment fails with the following stacktrace:
java.lang.IllegalArgumentException: Filename must not be null
at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:43)
at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:48)
at org.apache.axis2.deployment.DeploymentEngine.buildServiceGroup(DeploymentEngine.java:1015)
at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServicesFromWebInf(WarBasedAxisConfigurator.java:309)
at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:270)
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:78)
at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:500)
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
The bug seems to stem directly from line 1015 in DeploymentEngine:
DeploymentFileData currentDeploymentFile = new DeploymentFileData(null, null);
- directly passing the null file argument to the constructor of DeploymentFileData.
DeploymentFileData seems to have changed a lot since v. 1.2, under which this type of deployment worked. The bug was experienced after upgrade to 1.3.
--
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
[jira] Resolved: (AXIS2-3246) Deployment of embedded service causes
IllegalArgumentException: Filename must not be null
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe resolved AXIS2-3246.
--------------------------------------
Resolution: Fixed
Fixed the issues in the trunk
> Deployment of embedded service causes IllegalArgumentException: Filename must not be null
> -----------------------------------------------------------------------------------------
>
> Key: AXIS2-3246
> URL: https://issues.apache.org/jira/browse/AXIS2-3246
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: BEA Weblogic 10
> Reporter: Thomas Nymand
> Assignee: Deepal Jayasinghe
> Priority: Critical
>
> When deploying an embedded type service (war containing services.xml in WEB-INF, services.xml containing service group), the deployment fails with the following stacktrace:
> java.lang.IllegalArgumentException: Filename must not be null
> at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:43)
> at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:48)
> at org.apache.axis2.deployment.DeploymentEngine.buildServiceGroup(DeploymentEngine.java:1015)
> at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServicesFromWebInf(WarBasedAxisConfigurator.java:309)
> at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:270)
> at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:78)
> at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:500)
> at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420)
> at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
> at weblogic.security.service.SecurityManager.runAs(Unknown Source)
> at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
> The bug seems to stem directly from line 1015 in DeploymentEngine:
> DeploymentFileData currentDeploymentFile = new DeploymentFileData(null, null);
> - directly passing the null file argument to the constructor of DeploymentFileData.
> DeploymentFileData seems to have changed a lot since v. 1.2, under which this type of deployment worked. The bug was experienced after upgrade to 1.3.
--
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
[jira] Updated: (AXIS2-3246) Deployment of embedded service causes
IllegalArgumentException: Filename must not be null
Posted by "Thomas Nymand (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Nymand updated AXIS2-3246:
---------------------------------
Environment: BEA Weblogic 10 (was: BEA Weblogic 10, Axis2 1.3.)
> Deployment of embedded service causes IllegalArgumentException: Filename must not be null
> -----------------------------------------------------------------------------------------
>
> Key: AXIS2-3246
> URL: https://issues.apache.org/jira/browse/AXIS2-3246
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: BEA Weblogic 10
> Reporter: Thomas Nymand
> Priority: Critical
>
> When deploying an embedded type service (war containing services.xml in WEB-INF, services.xml containing service group), the deployment fails with the following stacktrace:
> java.lang.IllegalArgumentException: Filename must not be null
> at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:43)
> at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:48)
> at org.apache.axis2.deployment.DeploymentEngine.buildServiceGroup(DeploymentEngine.java:1015)
> at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServicesFromWebInf(WarBasedAxisConfigurator.java:309)
> at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:270)
> at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:78)
> at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:500)
> at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420)
> at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
> at weblogic.security.service.SecurityManager.runAs(Unknown Source)
> at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
> The bug seems to stem directly from line 1015 in DeploymentEngine:
> DeploymentFileData currentDeploymentFile = new DeploymentFileData(null, null);
> - directly passing the null file argument to the constructor of DeploymentFileData.
> DeploymentFileData seems to have changed a lot since v. 1.2, under which this type of deployment worked. The bug was experienced after upgrade to 1.3.
--
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
[jira] Assigned: (AXIS2-3246) Deployment of embedded service causes
IllegalArgumentException: Filename must not be null
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe reassigned AXIS2-3246:
----------------------------------------
Assignee: Deepal Jayasinghe
> Deployment of embedded service causes IllegalArgumentException: Filename must not be null
> -----------------------------------------------------------------------------------------
>
> Key: AXIS2-3246
> URL: https://issues.apache.org/jira/browse/AXIS2-3246
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: BEA Weblogic 10
> Reporter: Thomas Nymand
> Assignee: Deepal Jayasinghe
> Priority: Critical
>
> When deploying an embedded type service (war containing services.xml in WEB-INF, services.xml containing service group), the deployment fails with the following stacktrace:
> java.lang.IllegalArgumentException: Filename must not be null
> at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:43)
> at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:48)
> at org.apache.axis2.deployment.DeploymentEngine.buildServiceGroup(DeploymentEngine.java:1015)
> at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServicesFromWebInf(WarBasedAxisConfigurator.java:309)
> at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:270)
> at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:78)
> at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:500)
> at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420)
> at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
> at weblogic.security.service.SecurityManager.runAs(Unknown Source)
> at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
> The bug seems to stem directly from line 1015 in DeploymentEngine:
> DeploymentFileData currentDeploymentFile = new DeploymentFileData(null, null);
> - directly passing the null file argument to the constructor of DeploymentFileData.
> DeploymentFileData seems to have changed a lot since v. 1.2, under which this type of deployment worked. The bug was experienced after upgrade to 1.3.
--
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
[jira] Updated: (AXIS2-3246) Deployment of embedded service causes
IllegalArgumentException: Filename must not be null
Posted by "Thomas Nymand (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Nymand updated AXIS2-3246:
---------------------------------
Priority: Critical (was: Blocker)
Description:
When deploying an embedded type service (war containing services.xml in WEB-INF, services.xml containing service group), the deployment fails with the following stacktrace:
java.lang.IllegalArgumentException: Filename must not be null
at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:43)
at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:48)
at org.apache.axis2.deployment.DeploymentEngine.buildServiceGroup(DeploymentEngine.java:1015)
at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServicesFromWebInf(WarBasedAxisConfigurator.java:309)
at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:270)
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:78)
at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:500)
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
The bug seems to stem directly from line 1015 in DeploymentEngine:
DeploymentFileData currentDeploymentFile = new DeploymentFileData(null, null);
- directly passing the null file argument to the constructor of DeploymentFileData.
DeploymentFileData seems to have changed a lot since v. 1.2, under which this type of deployment worked. The bug was experienced after upgrade to 1.3.
was:
When deploying an embedded type service (war containing services.xml in WEB-INF), the deployment fails with the following stacktrace:
java.lang.IllegalArgumentException: Filename must not be null
at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:43)
at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:48)
at org.apache.axis2.deployment.DeploymentEngine.buildServiceGroup(DeploymentEngine.java:1015)
at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServicesFromWebInf(WarBasedAxisConfigurator.java:309)
at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:270)
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:78)
at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:500)
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
The bug seems to stem directly from line 1015 in DeploymentEngine:
DeploymentFileData currentDeploymentFile = new DeploymentFileData(null, null);
- directly passing the null file argument to the constructor of DeploymentFileData.
DeploymentFileData seems to have changed a lot since v. 1.2, under which this type of deployment worked. The bug was experienced after upgrade to 1.3.
> Deployment of embedded service causes IllegalArgumentException: Filename must not be null
> -----------------------------------------------------------------------------------------
>
> Key: AXIS2-3246
> URL: https://issues.apache.org/jira/browse/AXIS2-3246
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: BEA Weblogic 10, Axis2 1.3.
> Reporter: Thomas Nymand
> Priority: Critical
>
> When deploying an embedded type service (war containing services.xml in WEB-INF, services.xml containing service group), the deployment fails with the following stacktrace:
> java.lang.IllegalArgumentException: Filename must not be null
> at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:43)
> at org.apache.axis2.deployment.repository.util.DeploymentFileData.<init>(DeploymentFileData.java:48)
> at org.apache.axis2.deployment.DeploymentEngine.buildServiceGroup(DeploymentEngine.java:1015)
> at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServicesFromWebInf(WarBasedAxisConfigurator.java:309)
> at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:270)
> at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:78)
> at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:500)
> at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420)
> at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
> at weblogic.security.service.SecurityManager.runAs(Unknown Source)
> at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
> The bug seems to stem directly from line 1015 in DeploymentEngine:
> DeploymentFileData currentDeploymentFile = new DeploymentFileData(null, null);
> - directly passing the null file argument to the constructor of DeploymentFileData.
> DeploymentFileData seems to have changed a lot since v. 1.2, under which this type of deployment worked. The bug was experienced after upgrade to 1.3.
--
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