Hi Conor,
I think creating a content node for your results data would be a bit
of a nasty hack - as you say it's not CMS content so Magnolia should
only provide a presentation layer. I think you'll just create more
problems for yourself if you try doing things this way.
Looking at your original post it looks like the way you were trying to
do it was fine. If you're not displaying Magnolia content then there's
no reason to use the Magnolia taglibs, JSTL in the template pages
should be fine. My guess is that you have some small bug in the JSTL
which doesn't throw an exception, but is enough to ignore the display
code. I notice that you're using Magnolia 3, but both the examples
you're using from the wiki are for older versions, so that may be
where the problem lies.
If you're using eclipse, or some other IDE with JSP debugging
capability, then stepping through the code should help. If not then
the old-fashioned method of lots of System.out.println calls to track
progress through the code should narrow down where the problem lies.
Sorry I can't help more with the specifics - I don't know much about
JSTL as I tend to just use JSP directly when things get hard :-)
Hope that's of some help,
Simon
On 05/03/07, Conor <[email protected]> wrote:
Hi Simon(again!),
Have noted your post to Sean about creating a page on
the fly. Should I guess from your servlet code that a workaround for my
issue is that I get an arraylist of hotels, then create a new content node
with that information. Once in magnolia specific objects, I would then use
the typical magnolia cms taglibs to show the data?
Is that correct? Any workaround, like avoiding having
to deal with magnolia specific java objects and just by-pass it and use
normal jstl?
Any advice appreciated,
Conor
Conor wrote:
>
> Hi Simon,
> Any chance you show me the link to where you posted some
> sample code? I am in a similiar situation to Dieter, in that I need to
> request some information in my backend, and want to use magnolia as a pure
> cms frontend solution. Here's my previous post on the issues I'm having:
>
>
http://www.nabble.com/Cannot-view-session-information-using-JSTL--tf3290921.html
>
> Have a sample solution from magnolia, but it isn't working for me, and it
> isn't producing any exception to prompt me where I'm going wrong!? Stuck
> between a rock and a hard place. Seeing I'm not the only person who wants
> to interact with a different backend to Jackrabbit/JCR, would appreciate
> it if you could point me in the right way, if you can?
> Thanks Simon,
> Conor
>
> p.s. Dieter, if you have solved the issue on showing your mysql data using
> magnolia, can you please explain how you did it? Am sure you're solution
> would work for me too...thanks in advance.
>
> Best,
> Conor
>
>
> Magnolia - User mailing list wrote:
>>
>> Hi Dieter,
>>
>> I've just posted some code in response to a similar request which may
>> help. My recommendation would be to use the Magnolia APIs for all
>> content creation and manipulation, rather than messing with the
>> underlying data layer. This way your code should be more insulated for
>> changes to Magnolia, Jackrabbit, JCR, etc.
>>
>> However, Magnolia doesn't currently have a very clean API for external
>> integration, so it may be tricky to get everything working. I know
>> there has been talk of a proper CMS API layer, and also a WebServices
>> layer that would be even better for what you want to do. I don't know
>> what the status is on either of these though. It would be good to hear
>> from anyone that's involved in that work actually, as I have need of
>> these features myself and would happily contribute to the development.
>>
>> Simon
>>
>> On 02/03/07, dieter <[email protected]> wrote:
>>>
>>> Hi,
>>>
>>> I have been browsing through the tables on my Magnolia repository and
>>> have
>>> been wondering in which tables the actual data is stored.
>>>
>>> My reason for asking is i would like to eventually be able to automate
>>> creating new content externally from Magnolia. Is this possible?
>>>
>>> Dieter
>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Viewing-MySql-tables-tf3334323.html#a9271918
>>> Sent from the Magnolia - User mailing list archive at Nabble.com.
>>>
>>>
>>> ----------------------------------------------------------------
>>> for list details see
>>> http://www.magnolia.info/en/developer.html
>>> ----------------------------------------------------------------
>>>
>>
>> ----------------------------------------------------------------
>> for list details see
>> http://www.magnolia.info/en/developer.html
>> ----------------------------------------------------------------
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Viewing-MySql-tables-tf3334323.html#a9304523
Sent from the Magnolia - User mailing list archive at Nabble.com.
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
