[JBoss JIRA] (WFLY-117) Add and deploy does not fail if runtimeName already exists
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-117?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler reopened WFLY-117:
---------------------------------
> Add and deploy does not fail if runtimeName already exists
> ----------------------------------------------------------
>
> Key: WFLY-117
> URL: https://issues.jboss.org/browse/WFLY-117
> Project: WildFly
> Issue Type: Bug
> Components: OSGi, Server
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: 8.0.0.Alpha1
>
>
> The ServerDeploymentHelper has this code
> {code}
> public String deploy(String runtimeName, InputStream input) throws ServerDeploymentException {
> ServerDeploymentActionResult actionResult;
> try {
> DeploymentPlanBuilder builder = deploymentManager.newDeploymentPlan();
> builder = builder.add(runtimeName, input).andDeploy();
> DeploymentPlan plan = builder.build();
> DeploymentAction action = builder.getLastAction();
> Future<ServerDeploymentPlanResult> future = deploymentManager.execute(plan);
> ServerDeploymentPlanResult planResult = future.get();
> actionResult = planResult.getDeploymentActionResult(action.getId());
> } catch (Exception ex) {
> throw new ServerDeploymentException(ex);
> }
> if (actionResult.getDeploymentException() != null)
> throw new ServerDeploymentException(actionResult);
> return runtimeName;
> }
> {code}
> which does not fail if the runtimeName already exists
> There is a debug log like this
> {code}
> 11:11:25,103 DEBUG [org.jboss.as.controller.management-operation] (pool-4-thread-1) JBAS014616: Operation ("add") failed - address: ([("deployment" => "v200.jar")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"v200.jar\")]"
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (WFLY-1277) Define Camel context definition format for deployments
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-1277?page=com.atlassian.jira.plugin.... ]
Thomas Diesler updated WFLY-1277:
---------------------------------
Description:
We currently support single XML file deployments with a name pattern like this
{code}
*-context.xml
{code}
or contained in other deployment types like this
{code}
META-INF/*-context.xml
{code}
Existing user deployments of either form would be treated as spring camel context deployments, which they are probably not.
A single XML file deployment is perhaps also questionable because it can only reference camel components, processors, beans, etc. that are already registered in the system somehow.
A safer option would be to only process deployment of type
{code}
*-camel-context.xml
META-INF/jboss-camel-context.xml
{code}
was:
We currently support single XML file deployments with a name pattern like this
{code}
*-context.xml
{code}
or contained in other deployment types like this
{code}
META-INF/*-context.xml
{code}
Existing user deployments of either form would be treated as spring camel context deployments, which they are probably not.
A single XML file deployment is perhaps also questionable because it can only reference camel components, processors, beans, etc. that are already registered in the system.
A safer option would be to only process deployment of type
{code}
*-camel-context.xml
META-INF/jboss-camel-context.xml
{code}
> Define Camel context definition format for deployments
> -------------------------------------------------------
>
> Key: WFLY-1277
> URL: https://issues.jboss.org/browse/WFLY-1277
> Project: WildFly
> Issue Type: Task
> Components: OSGi
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Labels: camel
>
> We currently support single XML file deployments with a name pattern like this
> {code}
> *-context.xml
> {code}
> or contained in other deployment types like this
> {code}
> META-INF/*-context.xml
> {code}
> Existing user deployments of either form would be treated as spring camel context deployments, which they are probably not.
> A single XML file deployment is perhaps also questionable because it can only reference camel components, processors, beans, etc. that are already registered in the system somehow.
> A safer option would be to only process deployment of type
> {code}
> *-camel-context.xml
> META-INF/jboss-camel-context.xml
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (WFLY-1036) FreeBSD native support
by Alexander Yerenkow (JIRA)
[ https://issues.jboss.org/browse/WFLY-1036?page=com.atlassian.jira.plugin.... ]
Alexander Yerenkow updated WFLY-1036:
-------------------------------------
Description:
There's no native .so for FreeBSD JBoss- Web variant.
Could you provide it?
Or, could you lend me a hand to create required build scripts :)
was:
There's no native .so for FreeBSD JBoss variant.
Could you provide it?
> FreeBSD native support
> ----------------------
>
> Key: WFLY-1036
> URL: https://issues.jboss.org/browse/WFLY-1036
> Project: WildFly
> Issue Type: Enhancement
> Reporter: Alexander Yerenkow
> Assignee: Remy Maucherat
>
> There's no native .so for FreeBSD JBoss- Web variant.
> Could you provide it?
> Or, could you lend me a hand to create required build scripts :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (WFLY-1277) Define Camel context definition format for deployments
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-1277?page=com.atlassian.jira.plugin.... ]
Thomas Diesler updated WFLY-1277:
---------------------------------
Description:
We currently support single XML file deployments with a name pattern like this
{code}
*-context.xml
{code}
or contained in other deployment types like this
{code}
META-INF/*-context.xml
{code}
Existing user deployments of either form would be treated as spring camel context deployments, which they are probably not.
A single XML file deployment is perhaps also questionable because it can only reference camel components, processors, beans, etc. that are already registered in the system.
A safer option would be to only process deployment of type
{code}
*-camel-context.xml
META-INF/jboss-camel-context.xml
{code}
was:
We currently support camel system context definitions like this
{code}
<subsystem xmlns="urn:jboss:domain:camel:1.0">
<camelContext id="system-context-1">
<![CDATA[
<route>
<from uri="direct:start"/>
<transform>
<simple>Hello #{body}</simple>
</transform>
</route>
]]>
</camelContext>
</subsystem>
{code}
> Define Camel context definition format for deployments
> -------------------------------------------------------
>
> Key: WFLY-1277
> URL: https://issues.jboss.org/browse/WFLY-1277
> Project: WildFly
> Issue Type: Task
> Components: OSGi
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Labels: camel
>
> We currently support single XML file deployments with a name pattern like this
> {code}
> *-context.xml
> {code}
> or contained in other deployment types like this
> {code}
> META-INF/*-context.xml
> {code}
> Existing user deployments of either form would be treated as spring camel context deployments, which they are probably not.
> A single XML file deployment is perhaps also questionable because it can only reference camel components, processors, beans, etc. that are already registered in the system.
> A safer option would be to only process deployment of type
> {code}
> *-camel-context.xml
> META-INF/jboss-camel-context.xml
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (WFLY-1277) Define Camel context definition format for deployments
by Thomas Diesler (JIRA)
Thomas Diesler created WFLY-1277:
------------------------------------
Summary: Define Camel context definition format for deployments
Key: WFLY-1277
URL: https://issues.jboss.org/browse/WFLY-1277
Project: WildFly
Issue Type: Task
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
We currently support camel system context definitions like this
{code}
<subsystem xmlns="urn:jboss:domain:camel:1.0">
<camelContext id="system-context-1">
<![CDATA[
<route>
<from uri="direct:start"/>
<transform>
<simple>Hello #{body}</simple>
</transform>
</route>
]]>
</camelContext>
</subsystem>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (WFLY-1276) Allow Camel expressions in subsystem configuration
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-1276?page=com.atlassian.jira.plugin.... ]
Thomas Diesler updated WFLY-1276:
---------------------------------
Description:
We currently support camel system context definitions like this
{code}
<subsystem xmlns="urn:jboss:domain:camel:1.0">
<camelContext id="system-context-1">
<![CDATA[
<route>
<from uri="direct:start"/>
<transform>
<simple>Hello #{body}</simple>
</transform>
</route>
]]>
</camelContext>
</subsystem>
{code}
This uses a substitution hack for ${body}
was:
We currently support camel system context definitions like this
{code}
<subsystem xmlns="urn:jboss:domain:camel:1.0">
<camelContext id="system-context-1">
<![CDATA[
<route>
<from uri="direct:start"/>
<transform>
<simple>Hello #{body}</simple>
</transform>
</route>
]]>
</camelContext>
</subsystem>
{code}
> Allow Camel expressions in subsystem configuration
> --------------------------------------------------
>
> Key: WFLY-1276
> URL: https://issues.jboss.org/browse/WFLY-1276
> Project: WildFly
> Issue Type: Task
> Components: OSGi
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Labels: camel
>
> We currently support camel system context definitions like this
> {code}
> <subsystem xmlns="urn:jboss:domain:camel:1.0">
> <camelContext id="system-context-1">
> <![CDATA[
> <route>
> <from uri="direct:start"/>
> <transform>
> <simple>Hello #{body}</simple>
> </transform>
> </route>
> ]]>
> </camelContext>
> </subsystem>
> {code}
> This uses a substitution hack for ${body}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (WFLY-1276) Allow Camel expressions in subsystem configuration
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-1276?page=com.atlassian.jira.plugin.... ]
Thomas Diesler updated WFLY-1276:
---------------------------------
Description:
We currently support camel system context definitions like this
{code}
<subsystem xmlns="urn:jboss:domain:camel:1.0">
<camelContext id="system-context-1">
<![CDATA[
<route>
<from uri="direct:start"/>
<transform>
<simple>Hello #{body}</simple>
</transform>
</route>
]]>
</camelContext>
</subsystem>
{code}
This uses a substitution hack for $
was:
We currently support camel system context definitions like this
{code}
<subsystem xmlns="urn:jboss:domain:camel:1.0">
<camelContext id="system-context-1">
<![CDATA[
<route>
<from uri="direct:start"/>
<transform>
<simple>Hello #{body}</simple>
</transform>
</route>
]]>
</camelContext>
</subsystem>
{code}
This uses a substitution hack for ${body}
> Allow Camel expressions in subsystem configuration
> --------------------------------------------------
>
> Key: WFLY-1276
> URL: https://issues.jboss.org/browse/WFLY-1276
> Project: WildFly
> Issue Type: Task
> Components: OSGi
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Labels: camel
>
> We currently support camel system context definitions like this
> {code}
> <subsystem xmlns="urn:jboss:domain:camel:1.0">
> <camelContext id="system-context-1">
> <![CDATA[
> <route>
> <from uri="direct:start"/>
> <transform>
> <simple>Hello #{body}</simple>
> </transform>
> </route>
> ]]>
> </camelContext>
> </subsystem>
> {code}
> This uses a substitution hack for $
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (WFLY-1276) Allow Camel expressions in subsystem configuration
by Thomas Diesler (JIRA)
Thomas Diesler created WFLY-1276:
------------------------------------
Summary: Allow Camel expressions in subsystem configuration
Key: WFLY-1276
URL: https://issues.jboss.org/browse/WFLY-1276
Project: WildFly
Issue Type: Task
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
We currently support camel system context definitions like this
{code}
<subsystem xmlns="urn:jboss:domain:camel:1.0">
<camelContext id="system-context-1">
<![CDATA[
<route>
<from uri="direct:start"/>
<transform>
<simple>Hello #{body}</simple>
</transform>
</route>
]]>
</camelContext>
</subsystem>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (WFLY-1275) Define content and format of the Camel subsystem configuration
by Thomas Diesler (JIRA)
Thomas Diesler created WFLY-1275:
------------------------------------
Summary: Define content and format of the Camel subsystem configuration
Key: WFLY-1275
URL: https://issues.jboss.org/browse/WFLY-1275
Project: WildFly
Issue Type: Task
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
We currently support camel system context definitions like this
{code}
<subsystem xmlns="urn:jboss:domain:camel:1.0">
<camelContext id="system-context-1">
<![CDATA[
<route>
<from uri="direct:start"/>
<transform>
<simple>Hello #{body}</simple>
</transform>
</route>
]]>
</camelContext>
</subsystem>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months