The dependencies required to make a standalone (outside of any container) JMS client for Glassfish are too large.
According to this page:
We need gf-client and imqjmsra. Now here is another independent problem, that realistically people won't just "reference JAR files"; we need maven dependencies. There is a gf-client maven package, for imqjmsra it's less obvious, and people are arguing which maven dependencies are needed in this case:
In our case we ended up referencing glassfish-embedded, which gives us a 70Mb deployment (all just to write to a JMS queue!). On top of that, because of the huge scale of those dependencies, we had conflicts and strange behaviour at runtime, and gave up integrating weld-se in that client application:
We think writing to a JMS queue from a standalone client ought to require minimal dependencies, all tied to JMS and nothing else, and there should be clear instructions on the maven dependencies which are required.