You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Hema Menon <me...@gmail.com> on 2005/01/19 07:16:14 UTC
Can you apply a patch on xml files? ( was Re: Invalid Column Name error - JS 2 build - SecurityAccessImpl
I don't mind answering my own queries, since I hope someone will later
benefit from the reply if they encounter a similar situation:)
Anyway, I find that security_repository.xml and sso_repository.xml
contains the column names in lower-case, whereas the table column
names themselves are defined in upper case. In my case, Sybase throws
exception, other databases(say Oracle) may not. Will it be possible to
update these files to reflect the column names in the upper case?
Thanks,
Hema
On Fri, 14 Jan 2005 14:38:53 -0600, Hema Menon <me...@gmail.com> wrote:
> Hello,
>
> I was successful in building Jetspeed 2 from the source checked out
> from CVS today. My database for deployment is Sybase. After deploying
> jetspeed when I try to login I get the SQLException due to invalid
> column name. The error stack trace is provided below.
>
> I am not why the code is looking for a Column name: creation_date,
> when the column name is indeed CREATION_DATE. It appears that
> getInternalUserPrincipal() method of SecurityAccessImpl is creating
> the query using QueryFactory where this is failing. From what I
> understand it is using SECURITY_PRINCIPAL table where CREATION_DATE
> coulmn is defined. I am not sure failure of the query due to
> case-sensitiveness is specific to Sybase. Can anyone let me know why
> this is happening?
>
> Stack trace follows:
> org.springframework.jdbc.UncategorizedSQLException: (OJB operation):
> encountered SQLException [Invalid column name 'creation_date'.
> ]; nested exception is com.sybase.jdbc2.jdbc.SybSQLException: Invalid
> column name 'creation_date'.
>
> org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.translate(SQLStateSQLExceptionTranslator.java:94)
> org.springframework.orm.ojb.OjbAccessor.convertJdbcAccessException(OjbAccessor.java:107)
> org.springframework.orm.ojb.OjbAccessor.convertOjbAccessException(OjbAccessor.java:89)
> org.springframework.orm.ojb.PersistenceBrokerTemplate.execute(PersistenceBrokerTemplate.java:155)
> org.springframework.orm.ojb.PersistenceBrokerTemplate.getObjectByQuery(PersistenceBrokerTemplate.java:178)
> org.apache.jetspeed.security.spi.impl.SecurityAccessImpl..........
> ..................................)
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:152)
> $Proxy2.getInternalUserPrincipal(Unknown Source)
> org.apache.jetspeed.security.spi.impl.DefaultUserSecurityHandler.getUserPrincipal(DefaultUserSecurityHandler.java:61)
>
> Thanks,
> Hema
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Hema Menon
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hema Menon
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: Can you apply a patch on xml files? ( was Re: Invalid Column Name error - JS 2 build - SecurityAccessImpl
Posted by Jeff Sheets <je...@gmail.com>.
As for oracle, you're right. Everything in oracle is case insensitive.
On Tue, 18 Jan 2005 21:16:14 -0900, Hema Menon <me...@gmail.com> wrote:
> I don't mind answering my own queries, since I hope someone will later
> benefit from the reply if they encounter a similar situation:)
>
> Anyway, I find that security_repository.xml and sso_repository.xml
> contains the column names in lower-case, whereas the table column
> names themselves are defined in upper case. In my case, Sybase throws
> exception, other databases(say Oracle) may not. Will it be possible to
> update these files to reflect the column names in the upper case?
>
> Thanks,
> Hema
>
> On Fri, 14 Jan 2005 14:38:53 -0600, Hema Menon <me...@gmail.com> wrote:
> > Hello,
> >
> > I was successful in building Jetspeed 2 from the source checked out
> > from CVS today. My database for deployment is Sybase. After deploying
> > jetspeed when I try to login I get the SQLException due to invalid
> > column name. The error stack trace is provided below.
> >
> > I am not why the code is looking for a Column name: creation_date,
> > when the column name is indeed CREATION_DATE. It appears that
> > getInternalUserPrincipal() method of SecurityAccessImpl is creating
> > the query using QueryFactory where this is failing. From what I
> > understand it is using SECURITY_PRINCIPAL table where CREATION_DATE
> > coulmn is defined. I am not sure failure of the query due to
> > case-sensitiveness is specific to Sybase. Can anyone let me know why
> > this is happening?
> >
> > Stack trace follows:
> > org.springframework.jdbc.UncategorizedSQLException: (OJB operation):
> > encountered SQLException [Invalid column name 'creation_date'.
> > ]; nested exception is com.sybase.jdbc2.jdbc.SybSQLException: Invalid
> > column name 'creation_date'.
> >
> > org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.translate(SQLStateSQLExceptionTranslator.java:94)
> > org.springframework.orm.ojb.OjbAccessor.convertJdbcAccessException(OjbAccessor.java:107)
> > org.springframework.orm.ojb.OjbAccessor.convertOjbAccessException(OjbAccessor.java:89)
> > org.springframework.orm.ojb.PersistenceBrokerTemplate.execute(PersistenceBrokerTemplate.java:155)
> > org.springframework.orm.ojb.PersistenceBrokerTemplate.getObjectByQuery(PersistenceBrokerTemplate.java:178)
> > org.apache.jetspeed.security.spi.impl.SecurityAccessImpl..........
> > ..................................)
> > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:152)
> > $Proxy2.getInternalUserPrincipal(Unknown Source)
> > org.apache.jetspeed.security.spi.impl.DefaultUserSecurityHandler.getUserPrincipal(DefaultUserSecurityHandler.java:61)
> >
> > Thanks,
> > Hema
> >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > Hema Menon
> >
>
> --
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Hema Menon
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org