You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Dain Sundstrom <da...@iq80.com> on 2007/09/22 19:08:49 UTC
cwiki formatting help
The new Tomcat docs are not showing up correctly on our website. For
example,
cwiki: http://cwiki.apache.org/confluence/display/OPENEJB/Tomcat
site: http://openejb.apache.org/tomcat.html
The card decks don't seem to be rendering correctly. If you view-
source of the site, all of the text is there, so I'm guessing this
may be a css or javascript problem.
Can anyone help me get this working?
Thanks,
-dain
Re: Java 6 and OpenJPA
Posted by Dain Sundstrom <da...@iq80.com>.
On Sep 27, 2007, at 12:24 AM, David Blevins wrote:
>
> On Sep 27, 2007, at 12:00 AM, Dario Laverde wrote:
>
>> Ok, so with Java 5, OpenJPA requires the agent and OpenEJB
>> currently only supports
>> OpenJPA as the JPA provider correct?
>
> True for the first part. For the second part, any compliant JPA
> provider should work. The only thing we'd still require OpenJPA
> for is to support CMP, but if you don't use them you're fine; just
> make sure you delete the cmp container declaration from the conf/
> openejb.xml file so that container won't load.
>
> Our CMP implementation is 95% JPA generic and about 5% OpenJPA
> specific. Even then we could support other JPA impls provided we
> could get the right hooks.
The limiting factory is my attention span. Currently, Tomcat is the
shiny ball :)
>> I also noticed you added security servlets in the latest ejb-
>> examples, so EJB
>> security in Tomcat now works?
>
> Neat! Interested in that answer as well :)
Yep. In trunk OpenEJB uses the Tomcat realm for authentication and
authorization. Basically, we inherit the login from the web
application. If you invoke an EJB directly using a remote client,
then we use the realm in the first Tomcat engine.
This is the first big beta-2 feature on the books :)
-dain
Re: Java 6 and OpenJPA
Posted by David Blevins <da...@visi.com>.
On Sep 27, 2007, at 12:00 AM, Dario Laverde wrote:
> Ok, so with Java 5, OpenJPA requires the agent and OpenEJB
> currently only supports
> OpenJPA as the JPA provider correct?
True for the first part. For the second part, any compliant JPA
provider should work. The only thing we'd still require OpenJPA for
is to support CMP, but if you don't use them you're fine; just make
sure you delete the cmp container declaration from the conf/
openejb.xml file so that container won't load.
Our CMP implementation is 95% JPA generic and about 5% OpenJPA
specific. Even then we could support other JPA impls provided we
could get the right hooks.
> I also noticed you added security servlets in the latest ejb-
> examples, so EJB
> security in Tomcat now works?
Neat! Interested in that answer as well :)
-David
Re: Java 6 and OpenJPA
Posted by Dario Laverde <da...@nycjava.net>.
Ok, so with Java 5, OpenJPA requires the agent and OpenEJB currently only supports
OpenJPA as the JPA provider correct?
I also noticed you added security servlets in the latest ejb-examples, so EJB
security in Tomcat now works?
thanks,
Dario
> On Sep 26, 2007, at 4:57 PM, Dario Laverde wrote:
>
>> According to the OpenJPA docs:
>>
>> http://openjpa.apache.org/docs/latest/manual/
>> ref_guide_pc_enhance.html#ref_guide_pc_enhance_unenhanced_types
>>
>> with Java 6 OpenJPA doesn't require the java agent "enhancer".
>
> Interesting, the Java6 vm supports runtime binding of agent classes.
> The best info on this I found by googling for "sun Agent-Class" was
> this blog post http://blogs.sun.com/sundararajan/entry/
> using_mustang_s_attach_api
>
> We should definitely support this when we support Java6.
>
>> Would there be any
>> issues with running OpenEJB with Java 6, and has anyone else here
>> tested other JPA
>> providers with OpenEJB?
>
> The server doesn't run on Java6 due to changes in the JDBC apis. I
> think the biggest task is to update commons-dbcp to support Java6.
>
> -dain
>
Re: Java 6 and OpenJPA
Posted by Dain Sundstrom <da...@iq80.com>.
On Sep 26, 2007, at 4:57 PM, Dario Laverde wrote:
> According to the OpenJPA docs:
>
> http://openjpa.apache.org/docs/latest/manual/
> ref_guide_pc_enhance.html#ref_guide_pc_enhance_unenhanced_types
>
> with Java 6 OpenJPA doesn't require the java agent "enhancer".
Interesting, the Java6 vm supports runtime binding of agent classes.
The best info on this I found by googling for "sun Agent-Class" was
this blog post http://blogs.sun.com/sundararajan/entry/
using_mustang_s_attach_api
We should definitely support this when we support Java6.
> Would there be any
> issues with running OpenEJB with Java 6, and has anyone else here
> tested other JPA
> providers with OpenEJB?
The server doesn't run on Java6 due to changes in the JDBC apis. I
think the biggest task is to update commons-dbcp to support Java6.
-dain
Java 6 and OpenJPA
Posted by Dario Laverde <da...@nycjava.net>.
According to the OpenJPA docs:
http://openjpa.apache.org/docs/latest/manual/ref_guide_pc_enhance.html#ref_guide_pc_enhance_unenhanced_types
with Java 6 OpenJPA doesn't require the java agent "enhancer". Would there be any
issues with running OpenEJB with Java 6, and has anyone else here tested other JPA
providers with OpenEJB?
thanks,
Dario
Re: cwiki formatting help
Posted by David Blevins <db...@visi.com>.
On Sep 22, 2007, at 12:34 PM, Dario Laverde wrote:
> Actually it works out ok for this page as directory listings or
> initial Tomcat
> output aren't that necessary IMO (I'd remove the notes referring to
> them and keep
> the page as is). These probably fit better on the separate Tomcat
> installation page
> anyway.
I think the "Installation for the Impatient" section is aimed at
showing how to do the integration in a brief way.
I suppose at some point we may want the main Tomcat page to be sort
of a "portal" of links to other docs.
-David
Re: cwiki formatting help
Posted by Dario Laverde <da...@nycjava.net>.
Actually it works out ok for this page as directory listings or initial Tomcat
output aren't that necessary IMO (I'd remove the notes referring to them and keep
the page as is). These probably fit better on the separate Tomcat installation page
anyway.
Also, under Detailed Installation Instructions, you indicate "These instructions
assume you have a standard Tomcat installation running on port 8080." But I tested
your installer on port 80 and had no problems. The implication here seemed that it
should be run only on port 8080 when that's not the case.
-Dario
> On Sep 22, 2007, at 10:08 AM, Dain Sundstrom wrote:
>
>> The new Tomcat docs are not showing up correctly on our website.
>> For example,
>>
>> cwiki: http://cwiki.apache.org/confluence/display/OPENEJB/Tomcat
>> site: http://openejb.apache.org/tomcat.html
>>
>> The card decks don't seem to be rendering correctly. If you view-
>> source of the site, all of the text is there, so I'm guessing this
>> may be a css or javascript problem.
>>
>> Can anyone help me get this working?
>
> I have no idea. Maybe there's simply some css stuff we need out of
> the confluence css.
>
> FYI, we have to change the name of "Manual Installation" page. The
> name went from something that was confusing in one situation to
> confusing in all situations. Might be long, but OpenEJB Tomcat
> Manual Installation is better. Or Tomcat Plugin Manual
> Installation ....
>
> -David
>
>
>
>
Re: cwiki formatting help
Posted by David Blevins <db...@visi.com>.
On Sep 23, 2007, at 10:28 PM, Dain Sundstrom wrote:
> It took me _hours_ to find, but we needed a script added to the
> footer of our cwiki template. When the site refreshes in an hour,
> you will be able to see the CLI examples.
Awesome! Thanks for this! I know it was a major PITA :) The doc
looks great on the site.
-David
Re: How to confiigure an container managed EntityManger in an embeded server?
Posted by Dain Sundstrom <da...@iq80.com>.
There was a bug with resolving persistence context/unit references in
the plugin. It's fixed and I updated the jars in my home directory
http://people.apache.org/~dain/openejb-temp/ I also added a JPA
example the ejb-examples.war (http://localhost:8080/ejb-examples/jpa).
-dain
On Sep 24, 2007, at 11:01 AM, Dain Sundstrom wrote:
> I haven't tried JPA in the Tomcat plugin yet. I'll try to add an
> example today.
>
> -dain
>
> On Sep 24, 2007, at 7:44 AM, Dario Laverde wrote:
>
>> Was this guy's issue resolved? I'm also having the problem getting
>> JPA to work
>> (@PersistanceContext) under Tomcat including basing code on the test:
>>
>> openejb-itests-beans/.../AnnotatedFieldInjectionStatelessBean.java
>>
>> Speaking of which, do these tests need to be adopted to run from
>> servlets to test
>> the latest annotations support under Tomcat?
>>
>> -Dario
>>
>>
>>>> David,
>>>>
>>>> I am using Maven 2. If the example could include a Maven 2 based
>>>> pom without inheriting a parent pom, that would be great.
>>>>
>>>
>>> Definitely. Looks like another user has some examples with JPA we
>>> can use here.
>>>
>>> Doing some experimenting with an intentionally bad reference to a
>>> non-
>>> existent persistence unit and am not seeing the output a user would
>>> need to correct things. Something fishy is definitely going on.
>>> Going to dig into this more first thing tomorrow. Likely won't take
>>> too much longer to steam things out.
>>>
>>> -David
>>>
>>>> Paul Spencer
>>>>
>>>>
>>>>> David Blevins wrote:
>>>>> That looks exactly right. Let me see if I can whip up a quick
>>>>> example with similar settings and see if we can't figure out what
>>>>> might be going. We need the example anyway.
>>>>> -David
>>>>> On Aug 27, 2007, at 9:00 PM, Paul Spencer wrote:
>>>>>> David,
>>>>>> See below.
>>>>>>
>>>>>> David Blevins wrote:
>>>>>>
>>>>>>> On Aug 26, 2007, at 6:44 PM, Paul Spencer wrote:
>>>>>>> If you're persistence unit was not found when we attempted to
>>>>>>> resolve the reference (created via the annotation) during the
>>>>>>> time the bean as loading, we'd throw one of these which should
>>>>>>> be logged and would fail your app:
>>>>>>> throw new IllegalArgumentException("Persistence unit " +
>>>>>>> contextInfo.persistenceUnitName + " for persistence-context-
>>>>>>> ref " +
>>>>>>> contextInfo.referenceName + " not
>>>>>>> found");
>>>>>>>
>>>>>> I am getting this error, but I believe the datasource is defined.
>>>>>>
>>>>>> Below is my configuration. Is their something missing?
>>>>>>
>>>>>> ***
>>>>>> * conf/openejb.xml
>>>>>> ***
>>>>>> ...
>>>>>> <Connector id="Default JDBC Database" >
>>>>>> JdbcDriver org.apache.derby.jdbc.EmbeddedDriver
>>>>>> JdbcUrl jdbc:derby:openjpa-database;create=true;
>>>>>> UserName
>>>>>> Password
>>>>>> </Connector>
>>>>>> ...
>>>>>>
>>>>>> ***
>>>>>> * ArtifactManagerImpl.java
>>>>>> ***
>>>>>> ...
>>>>>> @Stateless
>>>>>> public class ArtifactManagerImpl implements ArtifactManager {
>>>>>> @PersistenceContext(unitName = "myDataSource")
>>>>>> private EntityManager entityManager;
>>>>>>
>>>>>> public ArtifactManagerImpl() {
>>>>>> }
>>>>>> ...
>>>>>>
>>>>>> ***
>>>>>> * META-INF/persistence.xml
>>>>>> ***
>>>>>> <persistence>
>>>>>> <persistence-unit name="myDataSource" transaction-type="JTA">
>>>>>> <provider>
>>>>>> org.apache.openjpa.persistence.PersistenceProviderImpl
>>>>>> </provider>
>>>>>> <jta-data-source>
>>>>>> java:openejb/Connector/Default JDBC Database
>>>>>> </jta-data-source>
>>>>>> </persistence-unit>
>>>>>> </persistence>
>>>>>>
>>>>>> -David
>>>>>>
>>>>>>
>>>>>> Paul Spencer
>>>>>>
>>
>>
>
Re: How to confiigure an container managed EntityManger in an embeded server?
Posted by Dain Sundstrom <da...@iq80.com>.
I haven't tried JPA in the Tomcat plugin yet. I'll try to add an
example today.
-dain
On Sep 24, 2007, at 7:44 AM, Dario Laverde wrote:
> Was this guy's issue resolved? I'm also having the problem getting
> JPA to work
> (@PersistanceContext) under Tomcat including basing code on the test:
>
> openejb-itests-beans/.../AnnotatedFieldInjectionStatelessBean.java
>
> Speaking of which, do these tests need to be adopted to run from
> servlets to test
> the latest annotations support under Tomcat?
>
> -Dario
>
>
>>> David,
>>>
>>> I am using Maven 2. If the example could include a Maven 2 based
>>> pom without inheriting a parent pom, that would be great.
>>>
>>
>> Definitely. Looks like another user has some examples with JPA we
>> can use here.
>>
>> Doing some experimenting with an intentionally bad reference to a
>> non-
>> existent persistence unit and am not seeing the output a user would
>> need to correct things. Something fishy is definitely going on.
>> Going to dig into this more first thing tomorrow. Likely won't take
>> too much longer to steam things out.
>>
>> -David
>>
>>> Paul Spencer
>>>
>>>
>>>> David Blevins wrote:
>>>> That looks exactly right. Let me see if I can whip up a quick
>>>> example with similar settings and see if we can't figure out what
>>>> might be going. We need the example anyway.
>>>> -David
>>>> On Aug 27, 2007, at 9:00 PM, Paul Spencer wrote:
>>>>> David,
>>>>> See below.
>>>>>
>>>>> David Blevins wrote:
>>>>>
>>>>>> On Aug 26, 2007, at 6:44 PM, Paul Spencer wrote:
>>>>>> If you're persistence unit was not found when we attempted to
>>>>>> resolve the reference (created via the annotation) during the
>>>>>> time the bean as loading, we'd throw one of these which should
>>>>>> be logged and would fail your app:
>>>>>> throw new IllegalArgumentException("Persistence unit " +
>>>>>> contextInfo.persistenceUnitName + " for persistence-context-
>>>>>> ref " +
>>>>>> contextInfo.referenceName + " not
>>>>>> found");
>>>>>>
>>>>> I am getting this error, but I believe the datasource is defined.
>>>>>
>>>>> Below is my configuration. Is their something missing?
>>>>>
>>>>> ***
>>>>> * conf/openejb.xml
>>>>> ***
>>>>> ...
>>>>> <Connector id="Default JDBC Database" >
>>>>> JdbcDriver org.apache.derby.jdbc.EmbeddedDriver
>>>>> JdbcUrl jdbc:derby:openjpa-database;create=true;
>>>>> UserName
>>>>> Password
>>>>> </Connector>
>>>>> ...
>>>>>
>>>>> ***
>>>>> * ArtifactManagerImpl.java
>>>>> ***
>>>>> ...
>>>>> @Stateless
>>>>> public class ArtifactManagerImpl implements ArtifactManager {
>>>>> @PersistenceContext(unitName = "myDataSource")
>>>>> private EntityManager entityManager;
>>>>>
>>>>> public ArtifactManagerImpl() {
>>>>> }
>>>>> ...
>>>>>
>>>>> ***
>>>>> * META-INF/persistence.xml
>>>>> ***
>>>>> <persistence>
>>>>> <persistence-unit name="myDataSource" transaction-type="JTA">
>>>>> <provider>
>>>>> org.apache.openjpa.persistence.PersistenceProviderImpl
>>>>> </provider>
>>>>> <jta-data-source>
>>>>> java:openejb/Connector/Default JDBC Database
>>>>> </jta-data-source>
>>>>> </persistence-unit>
>>>>> </persistence>
>>>>>
>>>>> -David
>>>>>
>>>>>
>>>>> Paul Spencer
>>>>>
>
>
Re: How to confiigure an container managed EntityManger in an
embeded server?
Posted by Dario Laverde <da...@nycjava.net>.
Was this guy's issue resolved? I'm also having the problem getting JPA to work
(@PersistanceContext) under Tomcat including basing code on the test:
openejb-itests-beans/.../AnnotatedFieldInjectionStatelessBean.java
Speaking of which, do these tests need to be adopted to run from servlets to test
the latest annotations support under Tomcat?
-Dario
>> David,
>>
>> I am using Maven 2. If the example could include a Maven 2 based
>> pom without inheriting a parent pom, that would be great.
>>
>
>Definitely. Looks like another user has some examples with JPA we
>can use here.
>
>Doing some experimenting with an intentionally bad reference to a non-
>existent persistence unit and am not seeing the output a user would
>need to correct things. Something fishy is definitely going on.
>Going to dig into this more first thing tomorrow. Likely won't take
>too much longer to steam things out.
>
>-David
>
>> Paul Spencer
>>
>>
>>> David Blevins wrote:
>>> That looks exactly right. Let me see if I can whip up a quick
>>> example with similar settings and see if we can't figure out what
>>> might be going. We need the example anyway.
>>> -David
>>> On Aug 27, 2007, at 9:00 PM, Paul Spencer wrote:
>>>> David,
>>>> See below.
>>>>
>>>> David Blevins wrote:
>>>>
>>>>> On Aug 26, 2007, at 6:44 PM, Paul Spencer wrote:
>>>>> If you're persistence unit was not found when we attempted to
>>>>> resolve the reference (created via the annotation) during the
>>>>> time the bean as loading, we'd throw one of these which should
>>>>> be logged and would fail your app:
>>>>> throw new IllegalArgumentException("Persistence unit " +
>>>>> contextInfo.persistenceUnitName + " for persistence-context-ref " +
>>>>> contextInfo.referenceName + " not found");
>>>>>
>>>> I am getting this error, but I believe the datasource is defined.
>>>>
>>>> Below is my configuration. Is their something missing?
>>>>
>>>> ***
>>>> * conf/openejb.xml
>>>> ***
>>>> ...
>>>> <Connector id="Default JDBC Database" >
>>>> JdbcDriver org.apache.derby.jdbc.EmbeddedDriver
>>>> JdbcUrl jdbc:derby:openjpa-database;create=true;
>>>> UserName
>>>> Password
>>>> </Connector>
>>>> ...
>>>>
>>>> ***
>>>> * ArtifactManagerImpl.java
>>>> ***
>>>> ...
>>>> @Stateless
>>>> public class ArtifactManagerImpl implements ArtifactManager {
>>>> @PersistenceContext(unitName = "myDataSource")
>>>> private EntityManager entityManager;
>>>>
>>>> public ArtifactManagerImpl() {
>>>> }
>>>> ...
>>>>
>>>> ***
>>>> * META-INF/persistence.xml
>>>> ***
>>>> <persistence>
>>>> <persistence-unit name="myDataSource" transaction-type="JTA">
>>>> <provider>
>>>> org.apache.openjpa.persistence.PersistenceProviderImpl
>>>> </provider>
>>>> <jta-data-source>
>>>> java:openejb/Connector/Default JDBC Database
>>>> </jta-data-source>
>>>> </persistence-unit>
>>>> </persistence>
>>>>
>>>> -David
>>>>
>>>>
>>>> Paul Spencer
>>>>
Re: cwiki formatting help
Posted by Dain Sundstrom <da...@iq80.com>.
On Sep 24, 2007, at 12:08 PM, Dario Laverde wrote:
>> On Sep 23, 2007, at 11:29 PM, Dario Laverde wrote:
>>
>>> Dain,
>>>
>>> It's not clear how to invoke/test beans from the web admin the way
>>> I recall doing so
>>> in 0.9.2 unless I'm missing something obvious - otherwise, great
>>> job in bringing
>>> back that feature!
>>
>> I never used it in 0.9.2, so I have no basis for comparison. Can you
>> describe what you find strange?
>
> Well I'm getting NULL when I click on the beans listed in the JNDI
> browser (e.g. for
> the beans from the servlet-samples.war) and from the invoke menu
> you can only go
> back to the JNDI browser, and from EJB viewer there's not a way to
> specify one.
> Unless I'm wrong to assume that the web admin works with the Tomcat
> plugin...
The jndi browser needs to be updated for business interfaces. Also,
you should be able to invoke anything bound into JNDI instead of just
EJBs. If someone has some time to look at this, that would be great.
>>> So what's left, besides a how to on avoiding the OpenEJBListener
>>> for per-webapp
>>> embedding? ;-)
>>
>> The basics are all working good and I think it is ready for 3.0-
>> beta-1. As for 3.0 final Tomcat integration, I'd like to:
>>
>> o integrate security
>> o replace OpenEJB jndi impl with Tomcat impl
>> o change naming code to not replace the Tomcat enc builder but to
>> supplement it
>> o add ear support
>>
>> The first two are easy, but the last two will be challenging.
>
> I'd recommend adding to the top of the list the ability to bundle
> Open-EJB with your
> webapp (similar to Gernonimo's embeddable container). Is it just a
> classloader/path
> issue to move the listener to the web app's WEB-INF/web.xml as well
> as the loader
> and all the dependencies to the web app's WEB-INF/lib folder or is
> it much more than
> that?
It is a bit more complex. The reason I put this as a low priority is
the user will still have to install the JavaAgent and update the
annotations-api.jar for our code to run. If they are willing to go
that far, then they might as well install the listener globally.
Now when, OpenJPA fixes the non-enhancement mode and Tomcat updates
the annotation classes, I think we should look at the private web app
mode.
> thanks Dain for your hard work, let me know where I can help,
The jndi browser and invoker above is a good place.
-dain
Re: cwiki formatting help
Posted by Dario Laverde <da...@nycjava.net>.
> On Sep 23, 2007, at 11:29 PM, Dario Laverde wrote:
>
>> Dain,
>>
>> It's not clear how to invoke/test beans from the web admin the way
>> I recall doing so
>> in 0.9.2 unless I'm missing something obvious - otherwise, great
>> job in bringing
>> back that feature!
>
> I never used it in 0.9.2, so I have no basis for comparison. Can you
> describe what you find strange?
Well I'm getting NULL when I click on the beans listed in the JNDI browser (e.g. for
the beans from the servlet-samples.war) and from the invoke menu you can only go
back to the JNDI browser, and from EJB viewer there's not a way to specify one.
Unless I'm wrong to assume that the web admin works with the Tomcat plugin...
>> So what's left, besides a how to on avoiding the OpenEJBListener
>> for per-webapp
>> embedding? ;-)
>
> The basics are all working good and I think it is ready for 3.0-
> beta-1. As for 3.0 final Tomcat integration, I'd like to:
>
> o integrate security
> o replace OpenEJB jndi impl with Tomcat impl
> o change naming code to not replace the Tomcat enc builder but to
> supplement it
> o add ear support
>
> The first two are easy, but the last two will be challenging.
I'd recommend adding to the top of the list the ability to bundle Open-EJB with your
webapp (similar to Gernonimo's embeddable container). Is it just a classloader/path
issue to move the listener to the web app's WEB-INF/web.xml as well as the loader
and all the dependencies to the web app's WEB-INF/lib folder or is it much more than
that?
thanks Dain for your hard work, let me know where I can help,
-Dario
> -dain
>
>
Re: cwiki formatting help
Posted by Dain Sundstrom <da...@iq80.com>.
On Sep 23, 2007, at 11:29 PM, Dario Laverde wrote:
> Dain,
>
> It's not clear how to invoke/test beans from the web admin the way
> I recall doing so
> in 0.9.2 unless I'm missing something obvious - otherwise, great
> job in bringing
> back that feature!
I never used it in 0.9.2, so I have no basis for comparison. Can you
describe what you find strange?
> So what's left, besides a how to on avoiding the OpenEJBListener
> for per-webapp
> embedding? ;-)
The basics are all working good and I think it is ready for 3.0-
beta-1. As for 3.0 final Tomcat integration, I'd like to:
o integrate security
o replace OpenEJB jndi impl with Tomcat impl
o change naming code to not replace the Tomcat enc builder but to
supplement it
o add ear support
The first two are easy, but the last two will be challenging.
-dain
Re: cwiki formatting help
Posted by Dario Laverde <da...@nycjava.net>.
Dain,
It's not clear how to invoke/test beans from the web admin the way I recall doing so
in 0.9.2 unless I'm missing something obvious - otherwise, great job in bringing
back that feature!
So what's left, besides a how to on avoiding the OpenEJBListener for per-webapp
embedding? ;-)
-Dario
> On Sep 22, 2007, at 12:21 PM, David Blevins wrote:
>
>> On Sep 22, 2007, at 12:12 PM, David Blevins wrote:
>>
>>> On Sep 22, 2007, at 10:08 AM, Dain Sundstrom wrote:
>>>
>>>> The new Tomcat docs are not showing up correctly on our website.
>>>> For example,
>>>>
>>>> cwiki: http://cwiki.apache.org/confluence/display/OPENEJB/Tomcat
>>>> site: http://openejb.apache.org/tomcat.html
>>>>
>>>> The card decks don't seem to be rendering correctly. If you view-
>>>> source of the site, all of the text is there, so I'm guessing
>>>> this may be a css or javascript problem.
>>>>
>>>> Can anyone help me get this working?
>>>
>>> I have no idea. Maybe there's simply some css stuff we need out
>>> of the confluence css.
>>
>> This might be it. Just fishing stuff out of the confluence
>> rendered page that looks good:
>>
>> http://cwiki.apache.org//confluence/styles/main-action.css?
>> pluginCompleteKey=org.randombits.confluence.composition:composition-
>> setup&stylesheetName=deck&spaceKey=OPENEJB
>
> It took me _hours_ to find, but we needed a script added to the
> footer of our cwiki template. When the site refreshes in an hour,
> you will be able to see the CLI examples.
>
> -dain
>
Re: cwiki formatting help
Posted by Dain Sundstrom <da...@iq80.com>.
On Sep 22, 2007, at 12:21 PM, David Blevins wrote:
> On Sep 22, 2007, at 12:12 PM, David Blevins wrote:
>
>> On Sep 22, 2007, at 10:08 AM, Dain Sundstrom wrote:
>>
>>> The new Tomcat docs are not showing up correctly on our website.
>>> For example,
>>>
>>> cwiki: http://cwiki.apache.org/confluence/display/OPENEJB/Tomcat
>>> site: http://openejb.apache.org/tomcat.html
>>>
>>> The card decks don't seem to be rendering correctly. If you view-
>>> source of the site, all of the text is there, so I'm guessing
>>> this may be a css or javascript problem.
>>>
>>> Can anyone help me get this working?
>>
>> I have no idea. Maybe there's simply some css stuff we need out
>> of the confluence css.
>
> This might be it. Just fishing stuff out of the confluence
> rendered page that looks good:
>
> http://cwiki.apache.org//confluence/styles/main-action.css?
> pluginCompleteKey=org.randombits.confluence.composition:composition-
> setup&stylesheetName=deck&spaceKey=OPENEJB
It took me _hours_ to find, but we needed a script added to the
footer of our cwiki template. When the site refreshes in an hour,
you will be able to see the CLI examples.
-dain
Re: cwiki formatting help
Posted by David Blevins <db...@visi.com>.
On Sep 22, 2007, at 12:12 PM, David Blevins wrote:
>
> On Sep 22, 2007, at 10:08 AM, Dain Sundstrom wrote:
>
>> The new Tomcat docs are not showing up correctly on our website.
>> For example,
>>
>> cwiki: http://cwiki.apache.org/confluence/display/OPENEJB/Tomcat
>> site: http://openejb.apache.org/tomcat.html
>>
>> The card decks don't seem to be rendering correctly. If you view-
>> source of the site, all of the text is there, so I'm guessing this
>> may be a css or javascript problem.
>>
>> Can anyone help me get this working?
>
> I have no idea. Maybe there's simply some css stuff we need out of
> the confluence css.
This might be it. Just fishing stuff out of the confluence rendered
page that looks good:
http://cwiki.apache.org//confluence/styles/main-action.css?
pluginCompleteKey=org.randombits.confluence.composition:composition-
setup&stylesheetName=deck&spaceKey=OPENEJB
-David
Re: cwiki formatting help
Posted by David Blevins <db...@visi.com>.
On Sep 22, 2007, at 10:08 AM, Dain Sundstrom wrote:
> The new Tomcat docs are not showing up correctly on our website.
> For example,
>
> cwiki: http://cwiki.apache.org/confluence/display/OPENEJB/Tomcat
> site: http://openejb.apache.org/tomcat.html
>
> The card decks don't seem to be rendering correctly. If you view-
> source of the site, all of the text is there, so I'm guessing this
> may be a css or javascript problem.
>
> Can anyone help me get this working?
I have no idea. Maybe there's simply some css stuff we need out of
the confluence css.
FYI, we have to change the name of "Manual Installation" page. The
name went from something that was confusing in one situation to
confusing in all situations. Might be long, but OpenEJB Tomcat
Manual Installation is better. Or Tomcat Plugin Manual
Installation ....
-David