However, JPDA is only available with the professional (non-free) version of
JBuilder
-----Original Message-----
From: Russ White <[EMAIL PROTECTED]>
To: Orion-Interest <[EMAIL PROTECTED]>
Date: Mittwoch, 18. Oktober 2000 22:18
Subject: RE: JBuilder + Orion
>Probably because together is stepping on your system properties.
>JPDA debugging is much easier.
>When I develop with TogetherJ I use JBuilder to do my debugging(But you
could
>use many other tools). I have a JBuilder project that includes the Together
>project. Then I can debug using the JPDA. Very slick.
>BTW Together rocks, but I have never tried using JPDA directly with it. I
will
>have to investigate that. If I find a way I will post it.
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED]]On Behalf Of Peter
>> Pontbriand
>> Sent: Wednesday, October 18, 2000 10:45 AM
>> To: Orion-Interest
>> Subject: Re: JBuilder + Orion
>>
>>
>> > ----- Original Message -----
>> >
>> > And for what it's worth, setting up JProbe to run Orion is about as
>> > simple...
>> >
>> > Arved Sandstrom
>> >
>> >> -----Original Message-----
>> >>
>> >> - Adding orion.jar and ejb.jar to the required libraries of the
project
>> >> properties 'paths' tab.
>> >> - Setting the main class to 'com.evermind.server.ApplicationServer'
and
>> >> the VM parameters to '-Duser.dir=c:\orion' on the 'run' tab.
>> >>
>> >> Sven E. van 't Veer
>>
>> Unfortunately, when set up pretty much exactly as mentioned but in
Together
>> 4.1 (www.togethersoft.com), Orion chokes thusly:
>>
>> com.canlink.components.services.ProducerServicesException: catalog
creation
>> failed: Database error: File input/output error:
>> ./database/defaultdb.properties; nested exception is:
>> java.sql.SQLException: File input/output error:
>> ./database/defaultdb.properties;
>> ---> nested com.evermind.server.rmi.OrionRemoteException: Database
error:
>> File input/output error: ./database/defaultdb.properties; nested
exception
>> is:
>> java.sql.SQLException: File input/output error:
>> ./database/defaultdb.properties
>> at
>>
ProducerServices_StatelessSessionBeanWrapper3.createCatalog(ProducerServices
>> _StatelessSessionBeanWrapper3.java:92)
>> at
>>
com.canlink.catalog.CreateCatalogAction.perform(CreateCatalogAction.java:62)
>> at
>>
org.apache.struts.action.ActionServlet.processActionInstance(ActionServlet.j
>> ava:794)
>> at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:702)
>> at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:332)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>> at com.evermind.server.http.d3.so(JAX)
>> at com.evermind.server.http.d3.sm(JAX)
>> at com.evermind.server.http.ef.su(JAX)
>> at com.evermind.server.http.ef.dn(JAX)
>> at com.evermind.util.f.run(JAX)
>>
>> The '-Duser.dir=c:\orion' JVM argument is set correctly and the
>> defaultdb.properties file is in the right place and perfectly usable to
>> Orion when it is run outside of Together.
>>
>> Any ideas as to why this happens only when Orion is run within Together?
>>
>> P.Pontbriand
>> Canlink Interactive Technologies
>>
>>
>>
>>
>
>
