July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-1429) Reauthentication Support

by Andrew Oliver (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1429?page=comments#action_12368195 ] Andrew Oliver commented on JBAS-1429: ------------------------------------- I 1/2 implemented this for a customer a long while back but it got fscked up in the business details. If you have specific questions I'll tell what I remember. > Reauthentication Support > ------------------------ > > Key: JBAS-1429 > URL: http://jira.jboss.com/jira/browse/JBAS-1429 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.1 Final > Reporter: Andrew Oliver > Assigned To: Vicky Kak > > Add support for the reauthentication support (in particular MySQLChangeUser) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-1429) Reauthentication Support

by Vicky Kak (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1429?page=all ] Vicky Kak reassigned JBAS-1429: ------------------------------- Assignee: Vicky Kak > Reauthentication Support > ------------------------ > > Key: JBAS-1429 > URL: http://jira.jboss.com/jira/browse/JBAS-1429 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.1 Final > Reporter: Andrew Oliver > Assigned To: Vicky Kak > > Add support for the reauthentication support (in particular MySQLChangeUser) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1429) Reauthentication Support

by Vicky Kak (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1429?page=all ] Vicky Kak updated JBAS-1429: ---------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=50234 > Reauthentication Support > ------------------------ > > Key: JBAS-1429 > URL: http://jira.jboss.com/jira/browse/JBAS-1429 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.1 Final > Reporter: Andrew Oliver > Assigned To: Vicky Kak > > Add support for the reauthentication support (in particular MySQLChangeUser) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1014) Logging in often yields an error

by Micah Modell (JIRA)

Logging in often yields an error -------------------------------- Key: JBPM-1014 URL: http://jira.jboss.com/jira/browse/JBPM-1014 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM jPDL 3.2.1 Environment: FC6 - Sun Java 1.5.0.12 - Firefox 1.5.0.12 Reporter: Micah Modell Assigned To: Tom Baeyens I regularly get the following error when I attempt to log in. If I go back to the console and try again from the actual page (not a reload) then it seems to remedy the problem: 00:14:54,587 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception javax.faces.application.ViewExpiredException: viewId:/sa/procdef.jsf - View /sa/procdef.jsf could not be restored. at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:180) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1549) Add Package documentation for Portal API

by Andrew Oliver (JIRA)

Add Package documentation for Portal API ---------------------------------------- Key: JBPORTAL-1549 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1549 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.6 Final Reporter: Andrew Oliver http://docs.jboss.com/jbportal/v2.6/javadoc/ - there is no package documentation. Example of package documentation: http://docs.jboss.com/seam/2.0.0.B1/api/ How to do it: http://java.sun.com/j2se/1.3/docs/tooldocs/win32/javadoc.html#packagecomment In particular it would be helpful for the portal API. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1536) Jboss WSRP incompatible with BEA

by Andrew Oliver (JIRA)

Jboss WSRP incompatible with BEA -------------------------------- Key: JBPORTAL-1536 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1536 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6 Final Reporter: Andrew Oliver Assigned To: Chris Laprun do the public-bea-wsrp.xml wsrp example from the doco (http://docs.jboss.com/jbportal/v2.6/reference-guide/html_single/#wsrp). If you paste the WSDL in to the WSRP admin console you get: "Problem getting service description for producer bea Cause: setProperty must be overridden by all subclasses of SOAPMessage". If you create the descriptor you get: "Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: The processing instruction target matching "[xX][mM][lL]" is not allowed. @ *unknown*[3,6] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:156) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:169) at org.jboss.portal.wsrp.deployment.WSRPDeployer.init(WSRPDeployer.java:108) ... 21 more Caused by: org.xml.sax.SAXException: The processing instruction target matching "[xX][mM][lL]" is not allowed. @ *unknown*[3,6] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.fatalError(SaxJBossXBParser.java:332)" Over the wire (wireshark) the WSDL etc looks okay. Note this works with 2.4. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

3
20
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1091) CMS UI : order : for lists of languages, folders, files names

by Antoine Herzog (JIRA)

CMS UI : order : for lists of languages, folders, files names ------------------------------------------------------------- Key: JBPORTAL-1091 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1091 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Environment: JBoss Portal 2.4, WXP, CMS repository in filesystem, Reporter: Antoine Herzog Assigned To: Roy Russo Priority: Minor In the CMS UI, the ordering of the folders and the files names is "Date of creation". Wish : the ordering by names (more convenient to work). even better : feature to choose the ordering on name, dates, description (second priority). In the list of languages, when you use it with another user language than english, the list is in a very messy order : I guess it is the order of the languages names in english, but showed in the "other language". example : "english" is written "anglais" and can be found after "grec" (greek) and before "esperanto". solution : order the list with the i18n label of each items. even better : propose in top of list the few languages that are supported by the portal. propose a one (or a few) strategie(s) of ordering. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBXB-104) Improper marshalling for sequence of choices

by Wojciech Kudla (JIRA)

Improper marshalling for sequence of choices -------------------------------------------- Key: JBXB-104 URL: http://jira.jboss.com/jira/browse/JBXB-104 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Environment: JBoss 4.2.0 with bundled jboss-xml-binding.jar on Windows XP, SUSE with 1dk 1.5.11 Reporter: Wojciech Kudla When XML Schema includes <choice> nested in <sequence> element, MarshallerImpl serializes only the first element, ie. <xs:complexType name="testType"> <xs:sequence> <xs:choice> <element name="el1" type="xs:string" minOccurs="0" nillable="true" /> <element name="el2" type="xs:string" minOccurs="0" nillable="true" /> <element name="el3" type="xs:string" minOccurs="0" nillable="true" /> <xs:choice> </xs:sequence> </xs:complexType> For this schema definition, the serialized output for object containing all 3 elements would be only: <elementOfTypeTestType> <el1>test</el1> </elementOfTypeTestType>. In my opinion it is not proper handling of the mentioned type. The reason for this behavior lies in method responsible for marshaling elements nested in choice group. It returns after properly marshaling the first element. Instead it should first check the choice element's parent. This bug exists also in the trunk revision of JBoss XML Binding. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-985) MapBackedClassLoader doen't handle with different class name formats

by Fernando Meyer (JIRA)

MapBackedClassLoader doen't handle with different class name formats -------------------------------------------------------------------- Key: JBRULES-985 URL: http://jira.jboss.com/jira/browse/JBRULES-985 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.MR3 Reporter: Fernando Meyer Assigned To: Fernando Meyer Fix For: 4.0.0.MR4, FUTURE -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-1011) 3.2.1 Admin Console: Logout after a timeout

by Burr Sutter (JIRA)

3.2.1 Admin Console: Logout after a timeout ------------------------------------------- Key: JBPM-1011 URL: http://jira.jboss.com/jira/browse/JBPM-1011 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM jPDL 3.2.1 Reporter: Burr Sutter Assigned To: Tom Baeyens Priority: Minor Follow these steps using the 3.2.1 jPDL Suite - Bring up the jBPM Admin Console: http://localhost:8080/jbpm-console in a browser - Login: admin, admin - Wait N Minutes for web session to timeout (I didn't look to see what the default was) - Select "Log Out" from the top right-hand corner of the Admin Console - Login: admin, admin The following exception shows up. 15:17:05,421 WARN [lifecycle] phase(RESTORE_VIEW 1,com.sun.faces.context.FacesC ontextImpl@1bc5ebf) threw exception: java.lang.NullPointerException null org.jboss.gravel.common.phase.GravelPhaseListener.afterPhase(GravelPhaseListener .java:112) com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280) com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt erChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain. java:206) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:9 6) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt erChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain. java:206) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2 30) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1 75) And some more info: 15:17:05,421 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception javax.faces.application.ViewExpiredException: viewId:/sa/token.jsf - View /sa/to ken.jsf could not be restored. at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.jav a:187) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2007