Updated documentation is on the way...
Also, for the record, I generally build a JAR, configure with EJX,
then extract XML files to classes/META-INF for use in subsequent builds.
After that I edit the XML files by hand (for minor changes) or edit them
in the JAR with EJX and then extract them again (for new beans, etc.). I
haven't had the sort of problems you were describing (and I also use
TextPad for hand edits).
If you like, you can privately e-mail me a zipped copy of the
files that were causing you problems and the JAR they go with and I can
try to track down and fix the problem.
Aaron
On Tue, 19 Sep 2000, James Brannan wrote:
> Okay, I was a jerk,.....
>
> I recompiled and built the ejb-xml.jar from scratch via the ejx.jar
> and I think it works..... <sheepish grin>
>
> I will have to test its method to know for certain.
>
> But, the source of my frustration remains. The "getting started"
> information is extremely misleading. Following it doesn't work. I
> reinstalled and uninstalled, upgraded, recompiled, searched the FAQ's,
> looked for documentation, and tried many different things......
>
> It appears like a person MUST use the ejx.jar to create their
> ejb-jar.xml file. The frustration was not from my code not working but
> from JBoss.org's code (or at least Jboss.org's instructions) not
> working. I noticed that a lot of past posts all dealt with the same
> issue. Perhaps an addition to the FAQ about the "sensitivity" of
> ejb-jar.xml is needed.
>
> For the record: creating an ejb-jar.xml file in textpad (....being
> *really* carefull) and then jaring my files (with correct paths etc.)
> doesnt seem to work. After surfing around JBoss.org more I stumbled
> on the instructions to ejx.jar
>
> I jarred my files.
> I launched ejx.jar
> I chose ejb-jar.xml from the pulldown menu for file type. I navigated to my jar
>file and opened it.
> I clicked on the Enterprise Beans tab, clicked on actions, and started building my
>bean. I entered all the paramaters for the xml file through ejx.jar
>
> **Only this appeared to work.
> ****p.s. when I installed my xml.jar was not placed in the same folder as ejx.jar -
>I had to copy xml.jar to the bin directory for it to work.
> ****p.s.s. Editing a pre-existing ejb-jar.xml file with ejx.jar doesn't cut it. I
>tried that yesterday, only from scratch seems to work.
>
> As I get better with JBoss - provided it now works as I think it does - I promise to
>help any new users I see with similar problems as my penance :-)
>
>
> James A. Brannan
>
>
>
> >>> [EMAIL PROTECTED] 09/19/00 01:48PM >>>
> Ok ,
>
> so now that you are probably calmed down. Make sure your xml file is
> correct, the verifier says that he can't read the names of the classes!
> you seem to have big fingers please use the EJX to generate the XML files or
> doclet from Rickard and (if needed) remove the extra jboss.xml
>
> marc
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of James Brannan
> > Sent: Tuesday, September 19, 2000 10:24 AM
> > To: [EMAIL PROTECTED]
> > Subject: [jBoss-User] Does JBOSS work part II.
> >
> >
> > I do something as small as remove all hard returns from my
> > ejb-jar.xml file and I get new information with my error
> > message... Whats up with that?
> >
> > James
> >
> > ?--new info in error message ?--------
> >
> >
> > [Verifier] Verifying file:/C:/jboss/tmp/deploy/tmpejbjar60467.jar
> > [Verifier] ProductSet: The Bean Provider must specify the
> > fully-qualified name of the Java class that implements the ente
> > rprise bean's business methods.
> > [Verifier] ProductSet: The Bean Provider must specify the
> > fully-qualified name of the enterprise bean's home interface in
> > the home element.
> > [Verifier] ProductSet: The Bean Provider must specify the
> > fully-qualified name of the enterprise bean's remote interface
> > in the remote element.
> > [Container factory] Deploying ProductSet
> > [Container factory] Container Invoker Optimize='false'
> >
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Problems?: [EMAIL PROTECTED]
> >
> >
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
