Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

normalize REST dsl usage #48

Closed
wants to merge 1 commit into from
Closed

normalize REST dsl usage #48

wants to merge 1 commit into from

Conversation

acoburn
Copy link
Contributor

@acoburn acoburn commented Aug 16, 2015

This normalizes the REST dsl usage in the camel routes. @daniel-dgi will definitely need to look closely at this commit to make sure I didn't mess this up (esp. the PUT facade). n.b. I changed this from using the jetty component to using the servlet component because that's what the collections-service uses.

@ruebot
Copy link
Member

ruebot commented Oct 5, 2015

@acoburn firing up vagrant and testing now 😄

@ruebot
Copy link
Member

ruebot commented Oct 5, 2015

fcrepo doesn't come up with this one on first pass with vagrant.

ERROR 14:06:18.939 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:23.924 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:23.931 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:23.940 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:28.926 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:28.933 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:28.942 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:33.929 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:33.934 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:33.945 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:38.931 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:38.935 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:38.961 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:43.934 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:43.937 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:43.965 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:48.936 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:48.944 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
ERROR 14:06:48.971 (DefaultJmsMessageListenerContainer) Could not refresh JMS Connection for destination 'fedora' - retrying in 5000 ms. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused

whole bunch of that.

...and karaf

2015-10-05 14:02:57,133 | INFO  | de startup timer | MavenIndexerFacade               | 102 - io.hawt.hawtio-maven-indexer - 1.4.52 | Updated successfully 1/1 maven indexes.
2015-10-05 14:02:59,906 | WARN  | ActiveMQ Task-1  | FailoverTransport                | 142 - org.apache.activemq.activemq-osgi - 5.11.1 | Failed to connect to [tcp://localhost:61616] after: 10 attempt(s) continuing to retry.
2015-10-05 14:03:30,863 | INFO  | 7]-nio2-thread-1 | ServerSession                    | 28 - org.apache.sshd.core - 0.14.0 | Server session created from /0:0:0:0:0:0:0:1:46359
2015-10-05 14:03:31,438 | INFO  | 7]-nio2-thread-1 | ServerUserAuthService            | 28 - org.apache.sshd.core - 0.14.0 | Session karaf@/0:0:0:0:0:0:0:1:46359 authenticated
2015-10-05 14:03:32,551 | INFO  | h for user karaf | LogoutAction                     | 25 - org.apache.karaf.shell.console - 3.0.4 | Disconnecting from current session...
2015-10-05 14:05:38,081 | INFO  | 7]-nio2-thread-2 | ServerSession                    | 28 - org.apache.sshd.core - 0.14.0 | Server session created from /0:0:0:0:0:0:0:1:46442
2015-10-05 14:05:38,419 | INFO  | 7]-nio2-thread-2 | ServerUserAuthService            | 28 - org.apache.sshd.core - 0.14.0 | Session karaf@/0:0:0:0:0:0:0:1:46442 authenticated
2015-10-05 14:07:05,775 | WARN  | ActiveMQ Task-1  | FailoverTransport                | 142 - org.apache.activemq.activemq-osgi - 5.11.1 | Failed to connect to [tcp://localhost:61616] after: 20 attempt(s) continuing to retry.

@acoburn
Copy link
Contributor Author

acoburn commented Nov 6, 2015

closing this for now -- I may reopen it later, but I'd like to see a testing framework in place first, similar to #65

@acoburn acoburn closed this Nov 6, 2015
@ruebot
Copy link
Member

ruebot commented Nov 6, 2015

@acoburn agreed! We're so close.

@daniel-dgi
Copy link
Contributor

So I finally figured out how to register web services in Karaf using JAXRS annotated beans and publishing them to the OSGi service registry.

We should consider normalizing services with that approach. I've spent a huge amount of time time trying to get seperate camel contexts to integrate with the servlet that Karaf provides. Jetty, shared netty, servlet, spark-restlet.... none of them do 100% of what we need through the rest DSL facade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants