[JBoss JIRA] (JBIDE-11417) OpenShift Express: Embedded cartridge 10gen-mms-agent-0.1
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11417?page=com.atlassian.jira.plugi... ]
Stefan Bunciak closed JBIDE-11417.
----------------------------------
Verified in JBoss Developer Studio
Version: 7.0.0.Alpha1
Build id: Alpha1-v20130225-0422-B62
Build date: 20130225-0422
> OpenShift Express: Embedded cartridge 10gen-mms-agent-0.1
> ----------------------------------------------------------
>
> Key: JBIDE-11417
> URL: https://issues.jboss.org/browse/JBIDE-11417
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Attila Nagy
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Alpha1
>
> Attachments: detailled-error-msg.png, mongodb-required-for-mms.png
>
>
> There are more problems with the embedded cartridge 10gen-mms-agent
> 1) It needs MongoDB and OpenShift application wizard in JBoss Tools doesn't resolve the dependency by default.
> It means that the user is not warned in advance. The new application wizard will fail and user will be unable to make the initial git clone.
> 2) Actually the user is unable to embed the cartridge, because in the first round the user has to commit and push the 10gen-mss configuration file.
> The main problem is: the JBoss Tools wizard only reports that there was an error during the configuration, no details are provided.
> Here is the error message from JBoss Tools:
> Could not embed cartridges to application php10genmms2012032701
> Could not configure application "php10genmms2012032701" at "https://ec2-50-16-87-180.compute-1.amazonaws.com/broker/embed_cartridge"
> And here is the error message from the command line:
> Missing settings.py file: /var/lib/stickshift/9bd1f27bba0e40f2b77fdc4b22081991/myphp2with10genmms/.openshift/mms/settings.py
> This file is part of the agent zip file: 10gen-mms-agent-<group-name>.zip
> The zip file is available to download from https://mms.10gen.com/ after you register with their service.
> It contains your 10gen MMS credentials and is required for running the agent.
> You will need to add this file and then do a git commit and push before you can embed the 10gen-mms-agent-0.1 cartridge.
--
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, 1 month
[JBoss JIRA] (JBIDE-13665) In BPEL editor design mode and source mode differs
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBIDE-13665:
-----------------------------------------
Summary: In BPEL editor design mode and source mode differs
Key: JBIDE-13665
URL: https://issues.jboss.org/browse/JBIDE-13665
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: BPEL
Affects Versions: 3.3.3.Final-SOA
Reporter: Andrej Podhradsky
Assignee: Robert (Bob) Brodt
Attachments: Salutations.zip
In 'If' activity the BPEL editor allows to add 'ElseIf' after 'Else'. So, the result is something like
If
-> Else
-> ElseIf
By doing this, the editor displays diagrams in this order (and also this order in in source). But when you close and reopen the bpel process the editor shows
If
-> ElseIf
-> Else
but the source includes the previous oder.
This can be confusing since the editor shows something which looks good but in fact it is not.
--
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, 1 month
[JBoss JIRA] (JBIDE-13665) In BPEL editor design mode and source mode differs
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13665?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky updated JBIDE-13665:
--------------------------------------
Attachment: Salutations.zip
> In BPEL editor design mode and source mode differs
> --------------------------------------------------
>
> Key: JBIDE-13665
> URL: https://issues.jboss.org/browse/JBIDE-13665
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: BPEL
> Affects Versions: 3.3.3.Final-SOA
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Attachments: Salutations.zip
>
>
> In 'If' activity the BPEL editor allows to add 'ElseIf' after 'Else'. So, the result is something like
> If
> -> Else
> -> ElseIf
> By doing this, the editor displays diagrams in this order (and also this order in in source). But when you close and reopen the bpel process the editor shows
> If
> -> ElseIf
> -> Else
> but the source includes the previous oder.
> This can be confusing since the editor shows something which looks good but in fact it is not.
--
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, 1 month
[JBoss JIRA] (JBDS-2483) In BPEL editor design mode and source mode differs
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBDS-2483:
---------------------------------------
Summary: In BPEL editor design mode and source mode differs
Key: JBDS-2483
URL: https://issues.jboss.org/browse/JBDS-2483
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: SOA Tooling / Platform
Affects Versions: 5.0.3.GA-SOA
Reporter: Andrej Podhradsky
Assignee: Robert (Bob) Brodt
Attachments: Salutations.zip
In 'If' activity the BPEL editor allows to add 'ElseIf' after 'Else'. So, the result is something like
If
-> Else
-> ElseIf
By doing this, the editor displays diagrams in this order (and also this order in in source). But when you close and reopen the bpel process the editor shows
If
-> ElseIf
-> Else
but the source includes the previous oder.
This can be confusing since the editor shows something which looks good but in fact it is not.
--
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, 1 month
[JBoss JIRA] (JBDS-2483) In BPEL editor design mode and source mode differs
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBDS-2483?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBDS-2483:
------------------------------------
Attachment: Salutations.zip
> In BPEL editor design mode and source mode differs
> --------------------------------------------------
>
> Key: JBDS-2483
> URL: https://issues.jboss.org/browse/JBDS-2483
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.3.GA-SOA
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Attachments: Salutations.zip
>
>
> In 'If' activity the BPEL editor allows to add 'ElseIf' after 'Else'. So, the result is something like
> If
> -> Else
> -> ElseIf
> By doing this, the editor displays diagrams in this order (and also this order in in source). But when you close and reopen the bpel process the editor shows
> If
> -> ElseIf
> -> Else
> but the source includes the previous oder.
> This can be confusing since the editor shows something which looks good but in fact it is not.
--
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, 1 month
[JBoss JIRA] (JBIDE-13664) tracing options for openshift client not showing up not is logging working when configured
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13664?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13664:
----------------------------------------
Description:
tracing options in .options in openshiftclient is not showing up.
And when starting with -debug .options
and .options contains:
org.jboss.tools.openshift.express.client/debug=true
org.jboss.tools.openshift.express.client/debug/client=true
You get:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Application Started: 37798
log4j:WARN No appenders could be found for logger (com.openshift.internal.client.RestService).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
So this is not working at all.
was:
tracing options in .options in openshiftclient is not showing up and if you enable it explicitly by using
-debug .options
and .options contains:
You get:
"SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Application Started: 37798
log4j:WARN No appenders could be found for logger (com.openshift.internal.client.RestService).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info."
> tracing options for openshift client not showing up not is logging working when configured
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-13664
> URL: https://issues.jboss.org/browse/JBIDE-13664
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> tracing options in .options in openshiftclient is not showing up.
> And when starting with -debug .options
> and .options contains:
> org.jboss.tools.openshift.express.client/debug=true
> org.jboss.tools.openshift.express.client/debug/client=true
> You get:
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> Application Started: 37798
> log4j:WARN No appenders could be found for logger (com.openshift.internal.client.RestService).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> So this is not working at all.
--
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, 1 month