Not able to get device information from WURFLManager

I don't get it, <device> X has no capabilities in it!!!!
Shailendra
Posts: 6
Joined: Thu Apr 11, 2013 3:04 am

Not able to get device information from WURFLManager

Postby Shailendra » Tue Jul 02, 2013 8:19 am

We are using java 1.7 and jboss-eap.6.0 web application server. we have integrated wrufl1.4 jar with the web application. We are not getting device information from wruflManager. Any clue what is the reason?

sm_support2
Posts: 294
Joined: Mon Jun 20, 2011 5:04 pm

Re: Not able to get device information from WURFLManager

Postby sm_support2 » Tue Jul 02, 2013 8:28 am

is there any error message, log or stack trace you can post?

thanks

Shailendra
Posts: 6
Joined: Thu Apr 11, 2013 3:04 am

Re: Not able to get device information from WURFLManager

Postby Shailendra » Wed Jul 03, 2013 1:02 am

WURFLHolder wurfl = (WURFLHolder) getServletContext().getAttribute(WURFLHolder.class.getName()); //line 1

WURFLManager manager = wurfl.getWURFLManager();//line 2

Device device = manager.getDeviceForRequest(request);//line 3

we are calling above code but on line 2 server does not give any response. I have put listener entry in web.xml correctly.
web xml entry as below.
<context-param>
<param-name>wurfl</param-name>
<param-value>classpath:/wurfl.zip</param-value>
</context-param>


<listener>
<listener-class>
net.sourceforge.wurfl.core.web.WURFLServletContextListener
</listener-class>
</listener>

fulvio.crivellaro
Posts: 38
Joined: Tue Jan 31, 2012 10:27 am

Re: Not able to get device information from WURFLManager

Postby fulvio.crivellaro » Wed Jul 03, 2013 8:03 am

Can you tell us where exactly is the wurfl.zip file placed?
Moreover, could you try to upgrade to the latest Java API version (1.4.4.3)?
There should be no difference in terms of initialization, while on the other hand wurfl.zip file retrieval should be more consistent.
Fulvio

Shailendra
Posts: 6
Joined: Thu Apr 11, 2013 3:04 am

Re: Not able to get device information from WURFLManager

Postby Shailendra » Thu Jul 04, 2013 2:14 am

After doing suggested changes,still getting the same problem.Please sugget.

Shailendra
Posts: 6
Joined: Thu Apr 11, 2013 3:04 am

Re: Not able to get device information from WURFLManager

Postby Shailendra » Thu Jul 04, 2013 4:32 am

I have tried with upgraded version of wurfl i.e. wurfl1.4.4.3 and my wurfl.zip is placed in WEB-INF/classes.
But still facing the same problem.Please help

fulvio.crivellaro
Posts: 38
Joined: Tue Jan 31, 2012 10:27 am

Re: Not able to get device information from WURFLManager

Postby fulvio.crivellaro » Thu Jul 04, 2013 6:28 am

I guess I have the solution, then.

Try to replicate the 1.4.4.3 helloworld configuration: place the wurfl.zip file in the WEB-INF folder, at the same level of the classes folder, instead of inside it
Then copy this in the web.xml file:

Code: Select all

<context-param>
	<param-name>wurfl</param-name>
	<param-value>WEB-INF/wurfl.zip</param-value>
</context-param>
As I wrote in my previous post, 1.4.4.3 should have enhanced wurfl.zip file loading, letting you avoid the classpath:/ constraint.
Let me know if this fix solves your problem.

Fulvio

Shailendra
Posts: 6
Joined: Thu Apr 11, 2013 3:04 am

Re: Not able to get device information from WURFLManager

Postby Shailendra » Fri Jul 05, 2013 2:06 am

We have done that also but problem is same.

Shailendra
Posts: 6
Joined: Thu Apr 11, 2013 3:04 am

Re: Not able to get device information from WURFLManager

Postby Shailendra » Thu Jul 11, 2013 1:16 am

There was some jar conflict issue in our project. We have rectified these conflicts. Now Project is working fine.

fulvio.crivellaro
Posts: 38
Joined: Tue Jan 31, 2012 10:27 am

Re: Not able to get device information from WURFLManager

Postby fulvio.crivellaro » Thu Jul 11, 2013 3:16 am

Problem fixed. It was actually a server configuration issue, causing JBoss not to recognize wurfl.zip path.
As usual, as in any Java projects, make sure that you don't have JAR files of older versions of the libraries in forgotten places where the CLASSPATH can still see them.
What we noticed is that sometimes JBoss fails to recognize paths like WEB-INF/<path_to_wurfl.zip>.
Nevertheless, paths like classpath:/<path_to_wurfl.zip>, or absolute paths like file:///<path_to_wurfl.zip> seem to always work.


Who is online

Users browsing this forum: No registered users and 2 guests