guice maven artifacts
by Heiko Braun
It seems that the migration to the new repository has broken the archetype and samples build.
I've uploaded the missing guice artifacts to the jboss repository.
Sorry, for the inconvenience.
/Heiko
13 years, 11 months
Missing guice-serlver 2.0 from maven repository
by Krystian Kichewko
Hello!
I tried to test errai framework today and first thing I noticed is
that guice-servlet 2.0 is missing from maven repository:
Missing:
----------
1) com.google.code.guice:guice-servlet:jar:2.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.google.code.guice
-DartifactId=guice-servlet -Dversion=2.0 -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=com.google.code.guice
-DartifactId=guice-servlet -Dversion=2.0 -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.errai:errai-bus-demos-clientservice:jar:1.1-M1
2) org.jboss.errai:errai-bus:jar:1.1-M1
3) com.google.code.guice:guice-servlet:jar:2.0
I've also manually checked this link:
https://repository.jboss.org/nexus/content/groups/public/com/google/code/...
and it's really missing :)
This renders both examples and sandbox archetype unusable.
Unfortunatelly there is almost no chance for google to upload their
jars to public maven repository so I would like to ask someone with
proper permissions to deploy guice-servlet to jboss repo. guice 2.0 is
already there.
Krystian Kichewko
13 years, 11 months
@Multi
by John DeStefano
Hi,
What is the @Multi annotation used for?
Thx
13 years, 12 months
Use of RequestDispatcher
by Mike Brock
This has been a long time coming (since before 1.0). The use of RequestDispatcher's when sending messages instead of directly referencing the MessageBus is now strongly-encouraged. In fact, new API extensions (such as the async API) will no longer introduce APIs that use the MessageBus directly in terms of sending messages.
The current APIs remain backwards compatible. But use of request dispatchers will make your application more scaleable, by allowing messaging to be sent truly asynchronously from your code. As opposed to directly performing operations against the bus in the same thread from whence you send your messages. You can simply inject a RequestDispatcher just like you're used to injecting a MessageBus.
public class MyClass {
private RequestDispatcher dispatcher;
@Inject
public MyClass(RequestDispatcher dispatcher) {
this.dispatcher = dispatcher;
}
public void sendAMessage() {
MessageBuilder.createMessage()
.toSubject("Foo").signalling().noErrorHandling()
.sendNowWith(dispatcher);
}
}
... and in the client, you can obtain an instance to the RequestDispatcher with: ErraiBus.getDispatcher();
Best,
Mike.
13 years, 12 months
