[JBoss Seam] - Re: Seam Security
by shane.bryzakï¼ jboss.com
"lightbulb432" wrote :
| I spoke too soon when I said the above problem sorted itself out. The following does not work:
|
| <exception class="org.jboss.seam.NotLoggedInException">
| | <redirect view-id="/login.xhtml">
| | <message>Not logged in</message>
| | </redirect>
| | </exception>
|
| This does not appear in any case. Only for authorization exceptions (when the user doesn't have appropriate permissions) does the message appear. Keep in mind the redirect is working, however, and the login.xhtml does have an h:messages. Is this a bug in Seam?
This is definitely working in the seamspace example in cvs. Navigating to the url http://localhost:8080/seam-space/comment.seam?name=Mr_Smiley&blogId=2 while not logged in will cause a redirect to the registration page, with the error message being displayed. You might like to compare the config files with your own to see if there's anything majorly different, otherwise if you post a working example to jira I'd be happy to look at it for you.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012678#4012678
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012678
19Â years, 2Â months
[JBoss Seam] - Re: Issues moving from Seam 1.1.0 to Seam 1.1.5
by norman.richardsï¼ jboss.com
Ok, let's take a step back. You are making a big deal out of a misunderstanding of what seam is doing combined with a bug in seam.
Seam log messages are structured messages. You can:
1 - log contextual state using expressions, without needing to inject values and invoke methods.
2 - log formatted data easily
3 - eliminate overhead from message creation (string buffer builders, etc...) when the message is not logged - without needing to uglify your code with isLogged() tests.
For that you only have pay one small price - your log messages need to be a format string, like a printf. You wouldn't printf("this is the message " + someOtherData), would you? You would printf("this is the message %s", someOtherData) because if someOtherData had format codes, it would get messed up.
That's all that is happening here. You are using a raw text string as a message string. If you want to log a raw string, call log("#0", yourRawTextString). There's no magic here. There's nothing scandalous or shocking here. It's simply a format string.
You happened to not run into this before because of a bug in Seam 1.1 that didn't interpolate correctly when no parameters were passed in. This happened to be magnified by a recent change I made that caused an exception to be thrown when called with a bad format string. I fixed that issue so that it won't complain loudly when the user has an error in his format string.
I really don't know what to say. If you'd like a logging method that doesn't use a format string, open a JIRA issue. I don't think I see a need to explode the API further, but its worth consideration.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012675#4012675
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012675
19Â years, 2Â months
[Tomcat, HTTPD, Servlets & JSP] - Re: Explicit document source root using context/docbase
by azariah
Thanks for your reply. Adding the WAR file location under URLs in server/default/conf/jboss-service.xml works fine. However, I need to use the directory which contains the expanded WAR file.
I have tried "file:/c:/MyApp", "file:/c:/MyApp/", "file:/c:/MyApp/WEB-INF" and "file:/c:/MyApp/WEB-INF/web.xml". Each attempt fails with different errors.
With "file:/c:/MyApp/" the errors were:
2007-02-07 13:39:13,821 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@75567bae { url=file:/C:/mg32/MailGate/Java/webapps/adminPortal/src/WEB-INF/classes/com/tumbleweed/tda/mg/admin/ApplicationEventHandler.class }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/mg32/MailGate/Java/webapps/adminPortal/src/WEB-INF/classes/com/tumbleweed/tda/mg/admin/ApplicationEventHandler.class
altDD: null
lastDeployed: 1170884348258
lastModified: 1170884348258
mbeans:
org.jboss.deployment.DeploymentInfo@2013ee8e ...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012670#4012670
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012670
19Â years, 2Â months
[JBoss Messaging] - Problem with client on one host and server on another
by tdizzle26
I am running a JBoss AS with Messaging on one host and am attempting to run the examples included with Messaging on another host. The examples I am running are the queue and topic examples. Both examples are able to send or publish messages to the destination on the other host. The problem I am having is that neither example is able to consume the message back from the destination.
Here is the part of the AS console log:
anonymous wrote : 2007-02-07 16:38:14,687 ERROR [org.jboss.remoting.callback.ServerInvokerCallbackHandler] Error handling callback.
| org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for locator - InvokerLocator [socket://127.0.0.1:3478/null?callbackServerHost=127.0.0.1&callbackServerPort=3478&callbackServerProtocol=socket&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&datatype=jms&serializationtype=jms&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper]
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:323)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:125)
| at org.jboss.remoting.Client.invoke(Client.java:607)
| at org.jboss.remoting.Client.invoke(Client.java:599)
| at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:637)
| at org.jboss.jms.server.endpoint.ServerConsumerEndpoint$Deliverer.run(ServerConsumerEndpoint.java:637)
| at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.net.ConnectException: Connection refused: connect
| at java.net.PlainSocketImpl.socketConnect(Native Method)
| at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
| at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
| at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
| at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
| at java.net.Socket.connect(Socket.java:516)
| at java.net.Socket.connect(Socket.java:466)
| at java.net.Socket.(Socket.java:366)
| at java.net.Socket.(Socket.java:179)
| at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:183)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:701)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:319)
| ... 7 more
| 2007-02-07 16:38:14,687 WARN [org.jboss.jms.server.endpoint.ServerConsumerEndpoint] Failed to deliver the message to the client. See the server log for more details.
| 2007-02-07 16:38:14,687 DEBUG [org.jboss.jms.server.endpoint.ServerConsumerEndpoint] ConsumerEndpoint[11] failed to deliver the message to the client.
| org.jboss.remoting.callback.HandleCallbackException: Error handling callback.
| at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:658)
| at org.jboss.jms.server.endpoint.ServerConsumerEndpoint$Deliverer.run(ServerConsumerEndpoint.java:637)
| at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for locator - InvokerLocator [socket://127.0.0.1:3478/null?callbackServerHost=127.0.0.1&callbackServerPort=3478&callbackServerProtocol=socket&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&datatype=jms&serializationtype=jms&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper]
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:323)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:125)
| at org.jboss.remoting.Client.invoke(Client.java:607)
| at org.jboss.remoting.Client.invoke(Client.java:599)
| at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:637)
| ... 3 more
| Caused by: java.net.ConnectException: Connection refused: connect
| at java.net.PlainSocketImpl.socketConnect(Native Method)
| at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
| at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
| at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
| at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
| at java.net.Socket.connect(Socket.java:516)
| at java.net.Socket.connect(Socket.java:466)
| at java.net.Socket.(Socket.java:366)
| at java.net.Socket.(Socket.java:179)
| at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:183)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:701)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:319)
| ... 7 more
| 2007-02-07 16:38:14,687 WARN [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] A problem has been detected with the connection to remote client 3j001-lvr3hq-exw9w9vv-1-exw9waxj-a. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed.
I am also getting an org.jboss.aop.NotFoundInDispatcherException on the client side after the examples fail to consume the message. Anyone have any insight on how I can get this working?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012669#4012669
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012669
19Â years, 2Â months