[JBoss JIRA] (SEAMSOCIAL-32) twitter.updateStatus() error: Unable to resolve any beans for Types: interface org.jboss.seam.social.oauth.OAuthProvider
by Hendy Irawan (JIRA)
Hendy Irawan created SEAMSOCIAL-32:
--------------------------------------
Summary: twitter.updateStatus() error: Unable to resolve any beans for Types: interface org.jboss.seam.social.oauth.OAuthProvider
Key: SEAMSOCIAL-32
URL: https://issues.jboss.org/browse/SEAMSOCIAL-32
Project: Seam Social
Issue Type: Bug
Components: Twitter
Affects Versions: 3.1.0.Final
Reporter: Hendy Irawan
Assignee: Antoine Sabot-Durand
I configured beans.xml like :
{code}
<o:TwitterServiceJackson>
<s:modifies />
<o:OAuthApplication apiKey="****"
apiSecret="****" callback="http://ceefour.annafi:8080/satukancinta-web/callback.jsf" />
</o:TwitterServiceJackson>
{code}
But this code:
{code}
@Inject private TwitterService twitter;
public void publishTwitterStatus() {
String message = getFbStatusMessage();
log.debug("Updating Twitter status: {}", message);
twitter.updateStatus(message);
}
{code}
causes:
{code}
Caused by: javax.faces.el.EvaluationException: org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001308 Unable to resolve any beans for Types: [interface org.jboss.seam.social.oauth.OAuthProvider]; Bindings: [@javax.enterprise.inject.Any(), @org.jboss.seam.social.Twitter()]
at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
... 30 more
Caused by: org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001308 Unable to resolve any beans for Types: [interface org.jboss.seam.social.oauth.OAuthProvider]; Bindings: [@javax.enterprise.inject.Any(), @org.jboss.seam.social.Twitter()]
at org.jboss.weld.manager.BeanManagerImpl.getBean(BeanManagerImpl.java:707) [weld-core-1.1.4.Final.jar:2011-11-22 20:01]
at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:96) [weld-core-1.1.4.Final.jar:2011-11-22 20:01]
at org.jboss.seam.social.oauth.OAuthServiceBase.getProvider(OAuthServiceBase.java:88) [seam-social-3.1.0.Final.jar:]
at org.jboss.seam.social.oauth.OAuthServiceBase.sendSignedRequest(OAuthServiceBase.java:139) [seam-social-3.1.0.Final.jar:]
at org.jboss.seam.social.twitter.jackson.TwitterServiceJackson.updateStatus(TwitterServiceJackson.java:97) [seam-social-twitter-3.1.0.Final.jar:]
at org.jboss.seam.social.twitter.jackson.TwitterServiceJackson.updateStatus(TwitterServiceJackson.java:45) [seam-social-twitter-3.1.0.Final.jar:]
at com.satukancinta.ui.admin.UserShowAdmin.publishTwitterStatus(UserShowAdmin.java:262) [classes:]
at com.satukancinta.ui.admin.UserShowAdmin$Proxy$_$$_WeldClientProxy.publishTwitterStatus(UserShowAdmin$Proxy$_$$_WeldClientProxy.java) [classes:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.7.0_147-icedtea]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.7.0_147-icedtea]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.7.0_147-icedtea]
at java.lang.reflect.Method.invoke(Method.java:601) [:1.7.0_147-icedtea]
at org.apache.el.parser.AstValue.invoke(AstValue.java:262) [jbossweb-7.0.7.Final.jar:]
at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278) [jbossweb-7.0.7.Final.jar:]
at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:39) [weld-core-1.1.4.Final.jar:2011-11-22 20:01]
at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50) [weld-core-1.1.4.Final.jar:2011-11-22 20:01]
at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
... 31 more
{code}
I tried to provide my own OAuthSession but doesn't work: (because the access token is already stored, there's no need to re-authorize every time)
{code}
@Produces @RequestScoped @Twitter public OAuthSession getTwitterSession() {
OAuthSessionImpl session = new OAuthSessionImpl(Twitter.class.cast(Annotation.class));
session.setAccessToken(new OAuthToken() {
@Override
public String getToken() {
return userView.getUser().getTwitterAccessToken();
}
@Override
public String getSecret() {
return userView.getUser().getTwitterAccessTokenSecret();
}
});
return session;
}
{code}
I can get the Twitter instance but cannot do anything with it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] Created: (JBSEAM-4830) Seam version is not displayed on JBoss AS 7
by Marek Novotny (JIRA)
Seam version is not displayed on JBoss AS 7
-------------------------------------------
Key: JBSEAM-4830
URL: https://issues.jboss.org/browse/JBSEAM-4830
Project: Seam 2
Issue Type: Bug
Components: Core
Affects Versions: 2.2.2.Final
Reporter: Marek Novotny
Assignee: Marek Novotny
Fix For: 2.3.0.BETA1
While testing seam examples on JBoss AS 7, i noticed that Seam version is displayed as:
INFO [javax.servlet.ServletContextListener] (MSC service thread 1-1) Welcome to Seam null
This should give a version from jboss-seam.jar META-INF/Manifest.MF file like:
INFO [javax.servlet.ServletContextListener] (MSC service thread 1-1) Welcome to Seam 2.3.0-SNAPSHOT
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (SEAMJMS-65) Ingress JMS bridging results in endless invocations of observer method
by Thorsten Kunz (Created) (JIRA)
Ingress JMS bridging results in endless invocations of observer method
----------------------------------------------------------------------
Key: SEAMJMS-65
URL: https://issues.jboss.org/browse/SEAMJMS-65
Project: Seam JMS
Issue Type: Bug
Components: Event Bridging
Affects Versions: 3.1.0.CR1
Environment: JBAS 7.1.0.Beta1b
Reporter: Thorsten Kunz
I have defined this interface method:
@Outbound public void routeStringToQueue(@Observes String string, @JmsDestination(jndiName = "queue/pegasusMessage") Queue queue);
@Inbound public void routeStringsFromQueue(@Observes String string, @JmsDestination(jndiName = "queue/pegasusMessage") Queue queue);
Then create this observer method:
public void inboundMessageTest(@Observes @Inbound String message) { ... }
Once a String type event is fired this is being logged:
13:59:26,095 INFO [org.jboss.seam.jms.MessageManagerImpl] (http-localhost-127.0.0.1-8080-1) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT
13:59:26,108 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message
13:59:26,110 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT
13:59:26,337 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message
13:59:26,339 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT
13:59:26,386 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message
13:59:26,387 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT
13:59:26,403 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message
13:59:26,404 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT
13:59:26,403 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message
13:59:26,404 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT
[ ... and so on ... ]
It works just fine if I replace the observer method with a regular MDB for this destination.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] Created: (SEAMSOCIAL-19) WebClient example NPE in MultiServicesManagerImpl.connectCurrentService on facebook callback
by Marek Schmidt (JIRA)
WebClient example NPE in MultiServicesManagerImpl.connectCurrentService on facebook callback
--------------------------------------------------------------------------------------------
Key: SEAMSOCIAL-19
URL: https://issues.jboss.org/browse/SEAMSOCIAL-19
Project: Seam Social
Issue Type: Bug
Components: Facebook
Environment: jboss-as-7.1.0.Alpha1-SNAPSHOT, 3.0.0-SNAPSHOT revision 54570b8e1267b00b76c60b0345fe79d5d2b175ef
Reporter: Marek Schmidt
Assignee: Antoine Sabot-Durand
Sometimes (but not always, but happened more than once... ) after a redirect from Facebook login, I see the following exception instead of the webclient callback page:
I could not reproduce it by aggresive clicking after it happened, so I suspect it may occur after some session times out somewhere...
also, I am not sure it is facebook-specific or not.
{noformat}
15:52:38,299 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/social-web-client].[Faces Servlet]] (http--127.0.0.1-8080-5) Servlet.service() for servlet Faces Servlet threw exception: java.lang.NullPointerException
at org.jboss.seam.social.core.MultiServicesManagerImpl.connectCurrentService(MultiServicesManagerImpl.java:118) [seam-social-3.0.0-SNAPSHOT.jar:]
at org.jboss.seam.social.examples.webclient.SocialClient.connectCurrentService(SocialClient.java:103) [classes:]
at org.jboss.seam.social.examples.webclient.SocialClient$Proxy$_$$_WeldClientProxy.connectCurrentService(SocialClient$Proxy$_$$_WeldClientProxy.java) [classes:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24]
at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.facelets.tag.jsf.core.DeclarativeSystemEventListener.processEvent(EventHandler.java:128) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2477) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2102) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2050) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:287) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:245) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:293) [jboss-as-weld-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT]
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:108) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:313) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (SEAMINTL-72) Seam 3.1.0.Beta3 Bug - Messages NOT displayed
by Luca Cavagnoli (Created) (JIRA)
Seam 3.1.0.Beta3 Bug - Messages NOT displayed
---------------------------------------------
Key: SEAMINTL-72
URL: https://issues.jboss.org/browse/SEAMINTL-72
Project: Seam International
Issue Type: Bug
Components: Messages
Affects Versions: 3.1.0.Beta3
Environment: JBoss AS 7.0.1.Final
Seam 3.1.0.Beta3
Reporter: Luca Cavagnoli
Assignee: Ken Finnigan
I opened the security-idmconsole example included in 3.1.0.Beta3
I created a controller that has the following:
@Inject org.jboss.seam.international.status.Messages messages;
public void save() {
messages.info("Here is an info message!");
messages.warn("Here is a warning message!");
messages.error("Here is an error message!");
}
I deployed the project in JBoss AS 7.0.1.Final
The messages are NOT being displayed in the page.
If I remove the <h:messages> component from the page, I do NOT even get the "WARNING: FacesMessage(s) have been enqueued, but may not have been displayed." warning.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months