I did a quick clean download last night and just ran the pos app clean
and it worked fine and it uses all the Null devices by default as I
wasn't plugged into anything. For testing the Null printer dumps to the
log files and I got a nice little receipt for the order I placed.

You'll find the Null devices in:
    specialpurpose/pos/src/org/ofbiz/pos/jpos/service

Are you running in a non standard container? Or from within Eclipse or
something that is missing the classpath values maybe? I'd certainly move
back towards a clean version without mods like removing pop.Drawer until
you find the real cause of the problem.

Ray


Branden Strickland wrote:
> Jacques,
>
> I pulled down the newest release, and got everything up and working, but it
> seems that all of the "null" devices can't be found. Where exactly are those
> java files located?
>
> I'm guessing my drawer doesn't pop, becuase I've removed the pop.Drawer
> funtion in PosTranaction.java file.
>
> Is there something i can manually load into the classpath through the
> .classpath file to get those devices back?
>
> Thanks!
>
> On Tue, May 20, 2008 at 2:51 AM, Jacques Le Roux <
> [EMAIL PROTECTED]> wrote:
>
>   
>> I'm not sure of the reason (maybe it's in your code, or it depends of your
>> driver ?) but I get any of these (nor with Null cashdrawer)
>>
>> Jacques
>>
>>
>> From: "Branden Strickland" <[EMAIL PROTECTED]>
>>
>>     
>>> This is what I got while trying to finish a transaction when I had nothing
>>> in the quotes of the cashdrawer.
>>>
>>> Exception in thread "Thread-214" java.lang.NullPointerException
>>>       at org.ofbiz.pos.PosTransaction.popDrawer(PosTransaction.java:152)
>>>       at org.ofbiz.pos.PosTransaction$1.construct(PosTransaction.java:797)
>>>       at net.xoetrope.xui.helper.SwingWorker$2.run(Unknown Source)
>>>       at java.lang.Thread.run(Thread.java:619)
>>>
>>> and actually, I got this when I tried using the Null cashdrawer.
>>>
>>> JPOS Exception
>>> Exception: jpos.JposException
>>> Message: Could not connect to service with logicalName = NullCashDrawer:
>>> Exception.message=org.ofbiz.pos.jpos.factory.OfbizJposServiceFactory
>>> ---- stack trace
>>> ---------------------------------------------------------------
>>> jpos.JposException: Could not connect to service with logicalName =
>>> NullCashDrawer:
>>> Exception.message=org.ofbiz.pos.jpos.factory.OfbizJposServiceFactory
>>> jpos.loader.simple.SimpleServiceConnection.connect(Unknown Source)
>>> jpos.BaseJposControl.open(Unknown Source)
>>> org.ofbiz.pos.device.GenericDevice.open(GenericDevice.java:44)
>>> org.ofbiz.pos.device.DeviceLoader.load(DeviceLoader.java:165)
>>>
>>> org.ofbiz.pos.container.JposDeviceContainer.start(JposDeviceContainer.java:50)
>>> org.ofbiz.base.container.ContainerLoader.start(ContainerLoader.java:79)
>>> org.ofbiz.base.start.Start.startStartLoaders(Start.java:261)
>>> org.ofbiz.base.start.Start.startServer(Start.java:310)
>>> org.ofbiz.base.start.Start.start(Start.java:314)
>>> org.ofbiz.base.start.Start.main(Start.java:397)
>>>
>>>
>>> On Mon, May 19, 2008 at 5:23 PM, Jacques Le Roux <
>>> [EMAIL PROTECTED]> wrote:
>>>
>>> From: "Branden Strickland" <[EMAIL PROTECTED]>
>>>       
>>>>  I finally found epsons 1.9 adk, followed directions found on a ofbiz
>>>>
>>>>         
>>>>> jira forum.  However, because I'm using a cashdrawer that soley uses a
>>>>> signal from the printer, even commenting out the cashdrawer in
>>>>> pos-containers didn't work.  I had to change PosTransaction.java and
>>>>> commented out the popDrawer function. It kept giving me a null
>>>>> exception because as far s the pos is concerned, there is no drawer.
>>>>> maybe a thought is to make that conditional for the drawers that don't
>>>>> actually rely on the pos instead getting the signal from the printer.
>>>>>
>>>>> Sorry for the grammer, this is comming from my phone.
>>>>>
>>>>>
>>>>>           
>>>> What kind of error do you get ? I have no cashdrawer and I get no errors
>>>> using a TM-T88III with ADK 1.8 (just tested)
>>>>
>>>> Jacques
>>>>
>>>>
>>>>         
>
>   

Reply via email to