October 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-456) CXF version mismatch causing WebServiceTest to fail

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-456?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-456. ----------------------------- Resolution: Out of Date Out-of-date. The SwitchYard multiapp demo has been replaced by a generic servlet multiapp demo. > CXF version mismatch causing WebServiceTest to fail > --------------------------------------------------- > > Key: SRAMP-456 > URL: https://issues.jboss.org/browse/SRAMP-456 > Project: S-RAMP > Issue Type: Bug > Reporter: Gary Brown > Assignee: Brett Meyer > > Switchyard is currently using an older version of the IP BOM (CR6), which has version 2.6.8, while current version for alpha is supposed to be CR9, which has cxf 2.7.11. > This is causing a CNFE for org.apache.cxf.io.CopyingOutputStream. > Currently ignoring the test until versions are aligned. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-199) Wsdl and Xsd Derivers are not setting up import/include relationships

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-199?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-199. ----------------------------- Resolution: Duplicate Issue > Wsdl and Xsd Derivers are not setting up import/include relationships > --------------------------------------------------------------------- > > Key: SRAMP-199 > URL: https://issues.jboss.org/browse/SRAMP-199 > Project: S-RAMP > Issue Type: Bug > Affects Versions: 0.2.0 - Security & S-RAMP-1.0 > Reporter: Eric Wittmann > Assignee: Brett Meyer > > The XSD deriver and WSDL derivers need to set up relationships to other xsd/wsdl documents when they are imported or included. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-199) Wsdl and Xsd Derivers are not setting up import/include relationships

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-199?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-199: ----------------------------------- Superseded by SRAMP-547 > Wsdl and Xsd Derivers are not setting up import/include relationships > --------------------------------------------------------------------- > > Key: SRAMP-199 > URL: https://issues.jboss.org/browse/SRAMP-199 > Project: S-RAMP > Issue Type: Bug > Affects Versions: 0.2.0 - Security & S-RAMP-1.0 > Reporter: Eric Wittmann > Assignee: Brett Meyer > > The XSD deriver and WSDL derivers need to set up relationships to other xsd/wsdl documents when they are imported or included. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-591) Default EAP 6.3 Installation throws ERROR:Naming context is read-only

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-591?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-591. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Default EAP 6.3 Installation throws ERROR:Naming context is read-only > --------------------------------------------------------------------- > > Key: SRAMP-591 > URL: https://issues.jboss.org/browse/SRAMP-591 > Project: S-RAMP > Issue Type: Bug > Environment: CentOs 7 (3.10.0-123.el7.x86_64), > JAVA: java version "1.7.0_65"; OpenJDK Runtime Environment (rhel-2.5.1.2.el7_0-x86_64 u65-b17); OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) > Apache Ant 1.9.2 > The whole system runs inside of a virtual box with 4GB RAM, 2 CPUs and 50GB Harddrive. > Reporter: Sebastian Goschin > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > After installing DTgov and S-RAMP at EAP 6.3 and before installing workflows and ontologies of DTgov 1.4 by "ant seed", the EAP 6.3 throws errors during startup. > 18:18:49,657 WARN [org.overlord.sramp.events.jms.JMSEventProducer] (ServerService Thread Pool -- 58) Could not discover "ConnectionFactory" and/or the configured topics/queues over JNDI. Assuming a non-EE environment or that JMS/JNDI isnt configured. Falling back on an embedded ActiveMQ broker, available on {0} > 18:18:50,196 INFO [org.apache.activemq.store.kahadb.plist.PListStoreImpl] (ServerService Thread Pool -- 58) PListStore:[/home/admin/activemq-data/localhost/tmp_storage] started > 18:18:50,201 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Using Persistence Adapter: KahaDBPersistenceAdapter[/home/admin/activemq-data/localhost/KahaDB] > 18:18:50,234 INFO [org.jboss.solder.exception.control.extension] (MSC service thread 1-4) Adding handler Qualifiers: [@javax.enterprise.inject.Any()] TraversalMode: BREADTH_FIRST Handles Type: class java.lang.Throwable Precedence: -100 [method] public org.jboss.seam.transaction.SimpleTransactionExceptionHandler.markTransactionRollback(CaughtException<Throwable>) to known handlers > 18:18:50,248 ERROR [stderr] (JMX connector) Exception in thread "JMX connector" java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only > 18:18:50,279 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:155) > 18:18:50,279 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:63) > 18:18:50,280 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:248) > 18:18:50,280 ERROR [stderr] (JMX connector) at org.jboss.as.naming.InitialContext$DefaultInitialContext.bind(InitialContext.java:268) > 18:18:50,280 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:257) > 18:18:50,281 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419) > 18:18:50,281 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419) > 18:18:50,281 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:643) > 18:18:50,281 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426) > 18:18:50,282 ERROR [stderr] (JMX connector) at org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementContext.java:131) > 18:18:50,556 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @ApplicationScoped @Inject private org.overlord.sramp.governance.workflow.jbpm.ProcessService.processBean > 18:18:50,560 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @ApplicationScoped @Inject private org.overlord.dtgov.jbpm.ProcessBean.processEngineService > 18:18:50,581 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @ApplicationScoped @Inject private org.overlord.dtgov.taskapi.TaskApi.processEngineService > 18:18:50,799 INFO [org.jboss.web] (ServerService Thread Pool -- 68) JBAS018210: Register web context: /dtgov > 18:18:51,107 INFO [solder-servlet] (ServerService Thread Pool -- 68) Catch Integration for Servlets enabled > 18:18:57,085 INFO [org.apache.activemq.store.kahadb.MessageDatabase] (ServerService Thread Pool -- 58) KahaDB is version 4 > 18:18:57,110 INFO [org.apache.activemq.store.kahadb.MessageDatabase] (ServerService Thread Pool -- 58) Recovering from the journal ... > 18:18:57,111 INFO [org.apache.activemq.store.kahadb.MessageDatabase] (ServerService Thread Pool -- 58) Recovery replayed 2 operations from the journal in 0.008 seconds. > 18:18:57,162 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Apache ActiveMQ 5.8.0 (localhost, ID:overlordtestserver-38457-1412871529503-2:1) is starting > 18:18:57,176 INFO [org.apache.activemq.transport.TransportServerThreadSupport] (ServerService Thread Pool -- 58) Listening for connections at: tcp://localhost:61616 > 18:18:57,177 INFO [org.apache.activemq.broker.TransportConnector] (ServerService Thread Pool -- 58) Connector tcp://localhost:61616 Started > 18:18:57,178 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Apache ActiveMQ 5.8.0 (localhost, ID:overlordtestserver-38457-1412871529503-2:1) started > 18:18:57,178 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) For help or more information please see: http://activemq.apache.org > 18:18:57,178 WARN [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Store limit is 102400 mb, whilst the data directory: /home/admin/activemq-data/localhost/KahaDB only has 44079 mb of usable space > 18:18:57,179 ERROR [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Temporary Store limit is 51200 mb, whilst the temporary data directory: /home/admin/activemq-data/localhost/tmp_storage only has 44079 mb of usable space > 18:18:57,211 ERROR [stderr] (JMX connector) Exception in thread "JMX connector" java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only > 18:18:57,211 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:155) > 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:63) > 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:248) > 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.InitialContext$DefaultInitialContext.bind(InitialContext.java:268) > 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:257) > 18:18:57,213 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419) > 18:18:57,213 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419) > 18:18:57,214 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:643) > 18:18:57,214 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426) > 18:18:57,214 ERROR [stderr] (JMX connector) at org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementContext.java:131) > 18:18:57,218 INFO [org.apache.activemq.broker.TransportConnector] (ServerService Thread Pool -- 58) Connector vm://localhost Started -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-594) s-ramp:getMetaData command returns npe

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-594?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-594. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > s-ramp:getMetaData command returns npe > -------------------------------------- > > Key: SRAMP-594 > URL: https://issues.jboss.org/browse/SRAMP-594 > Project: S-RAMP > Issue Type: Bug > Affects Versions: 0.6.0.Final > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > After working through section 7 in the user guide, I had set the description property on an artifact and then exited the cli. > When I went back into the console and connected, I then issued the command: > s-ramp:getMetaData feed:15 > and got: > {noformat} > java.lang.NullPointerException > at org.overlord.sramp.shell.commands.core.GetMetaDataCommand.execute(GetMetaDataCommand.java:71) > at org.overlord.sramp.shell.SrampShell.run(SrampShell.java:103) > at org.overlord.sramp.shell.SrampShell.main(SrampShell.java:67) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at com.simontuffs.onejar.Boot.run(Boot.java:340) > at com.simontuffs.onejar.Boot.main(Boot.java:166) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-606) Unable to use update custom metadata using REST call

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-606?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-606. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Unable to use update custom metadata using REST call > ---------------------------------------------------- > > Key: SRAMP-606 > URL: https://issues.jboss.org/browse/SRAMP-606 > Project: S-RAMP > Issue Type: Bug > Components: Atom Binding, S-RAMP API > Affects Versions: 0.6.0.Final > Reporter: Giorgi Modebadze > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. > E.g. PUT call to Rest Service: > http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... > As a result, artifact with the given UUID will have property with name key and value Testvalue. > Here is the simple code that accepts REST calls: > https://gist.github.com/anonymous/469be08cc2610e727517 > Here's the pom.xml > https://gist.github.com/anonymous/08a3c91163c682cc6cd0 > The error from EAP: > https://gist.github.com/anonymous/b6422e498a3a90f4c28c > Predefined URLs for updating metadata work alright on EAP. E.g. > http://localhost:8080/dtgov/rest/update/name/value/uuid > Problem is produced on custom Rest calls only. > Everything works fine on Jetty, error is produced on EAP. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-606) Unable to use update custom metadata using REST call

by Giorgi Modebadze (JIRA)

[ https://issues.jboss.org/browse/SRAMP-606?page=com.atlassian.jira.plugin.... ] Giorgi Modebadze commented on SRAMP-606: ---------------------------------------- Thanks a lot for the fix. The workaround I came up with was to manually replace the UpdateMetaDataResource.class in dtgov.war with my UpdateMetaDataResource class and redeploy dtgov.war. But in future, good to know I can use additional REST calls without redeploying whole dtgov.war. > Unable to use update custom metadata using REST call > ---------------------------------------------------- > > Key: SRAMP-606 > URL: https://issues.jboss.org/browse/SRAMP-606 > Project: S-RAMP > Issue Type: Bug > Components: Atom Binding, S-RAMP API > Affects Versions: 0.6.0.Final > Reporter: Giorgi Modebadze > Assignee: Brett Meyer > > I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. > E.g. PUT call to Rest Service: > http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... > As a result, artifact with the given UUID will have property with name key and value Testvalue. > Here is the simple code that accepts REST calls: > https://gist.github.com/anonymous/469be08cc2610e727517 > Here's the pom.xml > https://gist.github.com/anonymous/08a3c91163c682cc6cd0 > The error from EAP: > https://gist.github.com/anonymous/b6422e498a3a90f4c28c > Predefined URLs for updating metadata work alright on EAP. E.g. > http://localhost:8080/dtgov/rest/update/name/value/uuid > Problem is produced on custom Rest calls only. > Everything works fine on Jetty, error is produced on EAP. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-606) Unable to use update custom metadata using REST call

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-606?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-606: ----------------------------------- [~giorgimode], here's the issue. RESTEasy was pulling in NamespacePrefixMapper from 2 different ClassLoaders: 1.) the com.sun.xml.bind EAP module and 2.) your app. #2 is transitive, included by the s-ramp-client dependency. The quick fix: {code} <dependency> <groupId>org.overlord.sramp</groupId> <artifactId>s-ramp-client</artifactId> <version>0.7.0-SNAPSHOT</version> <exclusions> <exclusion> <groupId>com.sun.xml.bind</groupId> <artifactId>jaxb-impl</artifactId> </exclusion> </exclusions> </dependency> ... <manifestEntries> <Dependencies>com.sun.xml.bind,org.jboss.resteasy.resteasy-jaxrs,org.apache.httpcomponents</Dependencies> </manifestEntries> {code} Note the addition of the com.sun.xml.bind module in the manifestEntries. After I did that, it worked perfectly. For now, I think the "fix" is going to be mentioning this caveat in our docs. Having to do platform-specific builds of s-ramp-client isn't really something I think we should spend time on, nor is it worth the maintenance. Hopefully that helps! > Unable to use update custom metadata using REST call > ---------------------------------------------------- > > Key: SRAMP-606 > URL: https://issues.jboss.org/browse/SRAMP-606 > Project: S-RAMP > Issue Type: Bug > Components: Atom Binding, S-RAMP API > Affects Versions: 0.6.0.Final > Reporter: Giorgi Modebadze > Assignee: Brett Meyer > > I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. > E.g. PUT call to Rest Service: > http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... > As a result, artifact with the given UUID will have property with name key and value Testvalue. > Here is the simple code that accepts REST calls: > https://gist.github.com/anonymous/469be08cc2610e727517 > Here's the pom.xml > https://gist.github.com/anonymous/08a3c91163c682cc6cd0 > The error from EAP: > https://gist.github.com/anonymous/b6422e498a3a90f4c28c > Predefined URLs for updating metadata work alright on EAP. E.g. > http://localhost:8080/dtgov/rest/update/name/value/uuid > Problem is produced on custom Rest calls only. > Everything works fine on Jetty, error is produced on EAP. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-606) Unable to use update custom metadata using REST call

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-606?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-606: ----------------------------------- [~giorgimode], thanks for the great write-up -- I'll see what I can do to reproduce it. > Unable to use update custom metadata using REST call > ---------------------------------------------------- > > Key: SRAMP-606 > URL: https://issues.jboss.org/browse/SRAMP-606 > Project: S-RAMP > Issue Type: Bug > Components: Atom Binding, S-RAMP API > Affects Versions: 0.6.0.Final > Reporter: Giorgi Modebadze > Assignee: Brett Meyer > > I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. > E.g. PUT call to Rest Service: > http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... > As a result, artifact with the given UUID will have property with name key and value Testvalue. > Here is the simple code that accepts REST calls: > https://gist.github.com/anonymous/469be08cc2610e727517 > Here's the pom.xml > https://gist.github.com/anonymous/08a3c91163c682cc6cd0 > The error from EAP: > https://gist.github.com/anonymous/b6422e498a3a90f4c28c > Predefined URLs for updating metadata work alright on EAP. E.g. > http://localhost:8080/dtgov/rest/update/name/value/uuid > Problem is produced on custom Rest calls only. > Everything works fine on Jetty, error is produced on EAP. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-606) Unable to use update custom metadata using REST call

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-606?page=com.atlassian.jira.plugin.... ] Work on SRAMP-606 started by Brett Meyer. ----------------------------------------- > Unable to use update custom metadata using REST call > ---------------------------------------------------- > > Key: SRAMP-606 > URL: https://issues.jboss.org/browse/SRAMP-606 > Project: S-RAMP > Issue Type: Bug > Components: Atom Binding, S-RAMP API > Affects Versions: 0.6.0.Final > Reporter: Giorgi Modebadze > Assignee: Brett Meyer > > I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. > E.g. PUT call to Rest Service: > http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... > As a result, artifact with the given UUID will have property with name key and value Testvalue. > Here is the simple code that accepts REST calls: > https://gist.github.com/anonymous/469be08cc2610e727517 > Here's the pom.xml > https://gist.github.com/anonymous/08a3c91163c682cc6cd0 > The error from EAP: > https://gist.github.com/anonymous/b6422e498a3a90f4c28c > Predefined URLs for updating metadata work alright on EAP. E.g. > http://localhost:8080/dtgov/rest/update/name/value/uuid > Problem is produced on custom Rest calls only. > Everything works fine on Jetty, error is produced on EAP. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues October 2014