[JBoss Seam] - Re: Issue with Seam and Tomcat 6 during tomcat startup
by lle
Hi Rich,
I am very sure it is not an issue with port conflicts. I installed both versions of tomcat as standalone installation, not window services.
For the behavior, as soon as I started Tomcat, after Seam has finished successfully initializing my application, then it dropped the application context as shown in my previous log snippet. As a result, I couldn't even get to the log in page. I think the little difference of the time when the context is dropped between yours and mine might be due to my app has an app-scope component. Hence, the context was dropped as soon as it finished initialization. Does your app have any app-scope component? If not, then I think my theory is correct (i.e. your app drops the context after you get to the login page since it's after the context has been initialized, maybe???).
I did deploy a non-Seam webapp and it worked fine with Tomcat 6. I used the Tomahawk examples webapp, so it is also a JSF app.
It is definitely something to do with Seam and Tomcat 6. This line in the log file marked the begining of the context dropping:
2007.03.12 10:51:45,504 DEBUG [Lifecycle] Undeploying, destroying application context
Do you have something similar in your log file?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027288#4027288
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4027288
19Â years, 1Â month
[Security & JAAS/JBoss] - Form Based Login Question: Redirect to different page after
by rkapil
We are using form based J2EE security in combination with a custom UsernamePasswordLoginModule. The entire web site is protected.
<login-config>
| <auth-method>FORM</auth-method>
| <realm-name>ASM AD Authentication</realm-name>
| <form-login-config>
| <form-login-page>/login/login.jsp</form-login-page>
| <form-error-page>
| /login/authenticationFailed.jsp
| </form-error-page>
| </form-login-config>
| </login-config>
Here's what is happening now: If a user tries to access a URL for a web app, they are redirected to the login.jsp above which submits to the JBoss j_security_check action. After they are authenticated, they are then redirected to the URL they requested.
The above works fine...if the user is requesting the "start" page for a web app and is authenticating for the first time. However, if they have bookmarked a "non-start page" in the application, or have clicked on a link after their session times out, after they are redirected to the login.jsp, authenticated by JBoss, and then sent to the URL requested, it causes problems because many URL's they are hitting expect objects in session, request, etc, and it's causing null pointer exceptions in our logs.
Here's what we want to do: If an unauthenticated user tries to access a URL that is NOT the "start" page for an application, they are redirected to specific page AFTER they are authenticated, and not the original URL requested which might cause problems.
I hope the above makes sense.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027281#4027281
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4027281
19Â years, 1Â month
[JBossWS] - Re: How do I use MIME types other than text/xml
by lbrackman
ok. I got past that issue. now I am getting an exception of the following on the client side:
[java] org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://fileXfer.ws.synoran.com}SendPartRequest
This is the SEI:
@WebService(targetNamespace = "http://fileXfer.ws.synoran.com/")
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, parameterStyle = SOAPBinding.ParameterStyle.BARE)
@BindingType(value = "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true")
public interface FileXferEndpoint
{
public SendPartResponse sendPart(SendPartRequest request);
}
I have the XmlType annotation on the SendPartRequest message class with the @XmlMimeType("application/octet-stream") declared for the DataHandler get bean. I used the wsprovide tool to generate the wsdl and deployed the app server.
@XmlType(name="SendPartRequest", namespace = "http://fileXfer.ws.synoran.com")
public class SendPartRequest {
public SendPartRequest() {
}
public SendPartRequest(long txId, int partNum, long size, DataHandler dataHandler) {
this.txId = txId;
this.dataHandler = dataHandler;
}
...
@XmlMimeType("application/octet-stream")
public DataHandler getDataHandler() {
return dataHandler;
}
public void setDataHandler(DataHandler dataHandler) {
this.dataHandler = dataHandler;
}
Using the wsconsume tool I generated the source code for the client. The generated source code does not appear to use the wrapper classes however and requires me to supply the all the parameters that are wrapped in the SendPartRequest class to the web service method call. I can't seem to find any reference to the SendPartRequest class in any of the generated code.
Is there something that I am missing here?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027279#4027279
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4027279
19Â years, 1Â month
Problem with my Roles
by Aurynn Shaw
I still need help with this.
The roles I have assigned to my users aren't getting picked up by the
authentication system, either with Tomcat's LDAP auth module via
JNDI, as well as trying it in JBoss via the JbossSecurityMgrRealm.
My roles ARE assuredly correct, as well as properly defined in my
web.xml - I can see them as being able to be checked against when the
authentication system tries to walk over the user roles that aren't
there.
As it happens with all three - both the Tomcat JNDI connector, as
well as the Jboss connectors, it leads me to believe that it's a
problem in the Tomcat side of the authentication/role checking. Am I
right in this?
I don't know where to look, however, to check WHY my user's roles are
being loaded.
Please help?
-A
19Â years, 1Â month